| Oracle® Database Release Notes 10g Release 2 (10.2) for Microsoft Windows (x64) Part Number B15680-07 |
|
| View PDF |
| Oracle® Database Release Notes 10g Release 2 (10.2) for Microsoft Windows (x64) Part Number B15680-07 |
|
| View PDF |
Release Notes
10g Release 2 (10.2) for Microsoft Windows (x64)
B15680-07
August 2008
This document contains important information that was not included in the platform-specific or product-specific documentation for this release. This document supplements Oracle Database Readme and may be updated after it is released.
This document may be updated after it is released. To check for updates to this document and to view other Oracle documentation, refer to the Documentation section on the Oracle Technology Network Web site:
http://www.oracle.com/technology/documentation/
For additional information about this release, refer to the readme files located in the ORACLE_BASE\ORACLE_HOME\relnotes directory.
Note:
The Database Quick Installation Guides are no longer available in printed format. These documents are available with the media in the same location as the software and on Oracle Technology Network.This document contains the following topics:
The latest certification information for Oracle Database 10g Release 2 (10.2) is available on OracleMetaLink at:
Oracle Database 10g Release 2 Certification
Oracle Database 10g Release 2 (10.2.0.4 or later) is certified on Microsoft Windows Vista x64 and Microsoft Windows Server 2008 x64 (all editions). The specific operating system components that are not supported are Windows Server 2008 x64 Hyper-V and Server Core.
JDK Version on Windows Server 2008
JDK 1.5.0 is used in Oracle Database 10g Release 2.
Microsoft Internet Explorer Support
Microsoft Internet Explorer 7 is supported for Oracle Enterprise Manager Database Control.
Oracle Services for Microsoft Transaction Server Support on Windows Vista
Microsoft introduced Agile Recovery for distributed transactions in Windows Vista and Windows Server 2008. Starting with Oracle Database 10g Release 2 (10.2.0.4), Oracle Services for Microsoft Transaction Server supports Agile Recovery when the operating system is Windows Vista x64 with Service Pack 1 or Windows Server 2008.
Agile Recovery permits "in-doubt" Microsoft Distributed Transaction Coordinator (MSDTC) transaction outcomes on one node of a mid-tier Windows cluster to be queried through the MSDTCs on other participating cluster nodes. It only applies to Windows machines in a mid-tier clustered environment.
ODP.NET and ODE.NET Support
Starting with Oracle Database 10g Release (10.2.0.4), Oracle Data Provider for .NET and Oracle Database Extensions for .NET are supported. The supported .NET framework version is 2.0.
Grid Control Support on Windows Vista
Oracle Enterprise Manager Grid Control Agent 10g Release 4 (10.2.0.4) is supported on Windows Vista and Windows Server 2008.
See Also:
The certification matrix, Note 412431.1, on OracleMetaLink for the latest Grid Control certification informationThe following products are not supported with Oracle Database 10g release 2 (10.2):
Oracle Enterprise Manager Grid Control media
A 64-bit Windows version of Oracle Enterprise Manager Grid Control is not available in this release.
Oracle Real Application Clusters, including Cluster File System and Server Management is not supported on Windows XP and Windows Vista.
Oracle Clusterware is not supported on Windows XP and Windows Vista.
Oracle Database Lite is not supported on Windows Vista 64-bit and Windows Server 2008 64-bit.
Entrust PKI Support
Generic Connectivity
nCipher Accelerator Support
Oracle Fail Safe Server is not supported on Windows Server 2008. Oracle Fail Safe Client is not supported on Windows Vista.
You can execute Oracle Migration Workbench from a 32-bit Windows environment to migrate third-party databases, as supported by release 9.2.0.2.1 or later, to an Oracle Database 10g Release 2 (10.2) database installed on a 64-bit Windows computer.
Oracle Enterprise Integration Gateways, which include the following:
Oracle Procedural Gateway for APPC
Oracle Transparent Gateway for IBM DRDA
Oracle Open Gateways, which include the following:
Oracle Transparent Gateway for Sybase
Oracle Transparent Gateway for Teradata
Oracle Transparent Gateway for Microsoft SQL Server
Review the following before installing Oracle Database 10g Release 2:
Our goal is to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle Database 10g release 2 (10.2) supports accessibility features. To make best use of these accessibility features, Oracle recommends the following software configuration:
Windows 2003 or later
Microsoft Internet Explorer 7.0 or later
Note:
Java Access Bridge is not supported.Additional accessibility information for Oracle products can be found at
http://www.oracle.com/accessibility
For the latest configuration information and for information about addressing accessibility and assistive technology issues, see the Oracle Accessibility FAQ at
http://www.oracle.com/accessibility/faq.html
Review the following sections for information about issues that affect Oracle Database installation, configuration, and upgrade:
Installation Media for Windows Vista and Windows Server 2008
Shutdown of Cluster Ready Services Stack May Leave Processes Running
Installing Oracle Database Client into an Existing Oracle Home
Error While Deleting a Remote Instance from an Oracle RAC-Shared Oracle Home Database
Reading a Downgraded Oracle Cluster Registry with Database Management Tools
Central Configuration of Oracle Real Application Clusters Disabled on Windows
Oracle Universal Installer Help Files Incorrect for Oracle Database Companion CD
Database Control Startup Not Timed Properly after Oracle RAC Database Creation
For late-breaking updates and best practices about preupgrade, postupgrade, compatibility, and interoperability discussions, refer to Note 466181.1 on OracleMetalink (https://metalink.oracle.com/) that links to "Oracle 11g Upgrade Companion" page.
Oracle recommends installing Oracle Database on NTFS. NTFS allows for strong security of database files, trace files, incident data, and so on stored in Oracle home.
Oracle Database is supported on Windows Vista and Windows Server 2008 with the 10.2.0.4 release. Use the Oracle Database 10g Release 2 (10.2.0.4.0) for Microsoft Windows Vista x64 and Microsoft Windows Server 2008 x64 media. This software is also available on the Oracle Technology Network site.
After shutting down the Cluster Ready Services (CRS) stack on a given node using the following command:
CRSCTL.EXE stop crs
the OracleEVMService or OracleCRService may not be listed in the STOPPED state. Furthermore, you may notice the existence of CRSD.EXE or EVMD.EXE in the Task Manager list of running processes. To stop these processes, issue the following commands from the operating system command prompt:
net stop OracleCRService net stop OracleEVMService
Oracle Database Client can be installed in the same Oracle Database home if both products are at the same release level. For example, you can install Oracle Database Client 10g Release 2 (10.2) into an existing Oracle Database 10g Release 2 (10.2) home. If you apply a patch set before installing the client, then you must apply the patch set again.
When modifying the name, IP address, or netmask of an existing virtual IP address (VIP) resource, use the srvctl modify nodeapps command and include the existing interfaces for the VIP in the -A argument. For example:
srvctl modify nodeapps -n mynode1 -A 100.200.300.40/255.255.255.0/eth0
This issue is tracked with Oracle bug 4500688.
During a delete instance operation on a cluster database using a shared Oracle home, you can encounter the following error message if the database has been configured for Enterprise Manager Database Control:
Error updating EM configuration for node node name
As a result, the Enterprise Manager configuration is not completely removed from the node where the deleted instance was running. However, this does not have any adverse effects. You can click OK, ignore the error, and proceed.
This issue is tracked with Oracle bug 4547265.
Oracle Database 9.2 management tools (such as srvctl) encounter errors when attempting to read an Oracle Cluster Registry (OCR) that was downgraded from 10.2 to 9.2 on Windows.
Workaround:
Dump the contents of the 10.2 OCR before downgrading by using the ocrdump tool. Identify the set of 9.2 configured databases. The database configuration resides under the DATABASE.DATABASES key.
Follow the downgrade procedure as documented.
Identify the location of the 9.2 OCR. It is either \\.\srvcfg or the file pointed to by registry value CfsOcrRoot under HKEY_LOCAL_SYSTEM\SOFTWARE\Oracle\osd9i\ocr.
Clear the contents of the 9.2 OCR.
Execute the following command from the 9.2 Oracle home:
srvconfig -init -f
Configure the 9.2 cluster databases identified in Step 1:
srvctl add database
This issue is tracked with Oracle bug 4507090.
The srvctl tool fails with the following errors when starting Oracle9i databases after Oracle 10g Release 2 Clusterware is installed and the Global Services Daemon (GSD) is started from the Oracle Clusterware home:
/ORA-01005: null password given; logon denied / /ORA-01031: insufficient privileges / /ORA-01005: null password given; logon denied" /
Workaround:
Execute the following command to get the list of nodes in the Oracle Clusterware:
CRS home/bin/olsnodes
where home is the Oracle Clusterware home.
Execute the following command on one node.
CRS home/bin/crsuser add Oracle_user*
This command creates the service on all other nodes.
Execute the following commands for each node identified in Step 1:
CRS home/bin/crs_stop ora.node_name.gsd CRS home/bin/crs_setperm ora.node_name.gsd -o Oracle_user CRS home/bin/crs_start ora.node_name.gsd
This issue is tracked with Oracle bug 4523043.
Starting Oracle Database release 9.2 with srvctl fails when the Global Services Daemon (GSD) is running from Oracle 10.2 Clusterware. A dialog window displays the following error message:
The instruction at hex_address referenced memeory at hex_address. The memory could not be read
Workaround:
Copy srvctl.bat to srvctl.orig.bat in the 9.2 Oracle_Home\bin directory.
Edit the 9.2 Oracle_Home\bin\srvctl.bat file to add the following before -classpath.
-DTRACING.ENABLED=true -DTRACING.LEVEL=2
Save the Oracle_Home\bin\srvctl.bat file and reissue the same command with srvctl that previously failed.
This issue is tracked with Oracle bug 4571520.
If the ORA.ORA_SID.DB resource is ONLINE on a node that you want to delete from Oracle Clusterware, the delete node procedure displays the following errors while running crssetup:
prompt> crssetup del -nn node_name Step 1: shutting down node apps :node_name ora.racr1.db in ONLINE state . . . please manually stop dependent CRS resource before continuing
Workaround:
For the database resource (ora.*.db) mentioned in the error as being ONLINE, perform a relocation of that resource to any other node that is a part of the cluster. Run the crs_relocate command as shown below to perform the relocation:
crs_relocate name_of_the_db_resource -c cluster_node
This issue is tracked with Oracle bug 4564000.
While Oracle Database 10g supports raw devices, tools such as Database Configuration Assistant do not support the configuration of raw devices for single instances. Instead, use Automatic Storage Management (ASM) or the file system to store database files.For Oracle Real Application Clusters (Oracle RAC) installations, configure raw device shared storage by stamping disks with Oracle Object Link Manager. You can also use your own scripts to configure raw devices.
See Also:
Oracle Database Installation Guide for Microsoft Windows (for single-instance database installations)
Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide for Microsoft Windows
This issue is tracked with Oracle bug 4554058.
Oracle Messaging Gateway is supported starting from patch set 10.2.0.3. Follow these steps to install Oracle Messaging Gateway:
Log on to OracleMetaLink at :
Download and install the patch 6688246.
Download and install the Oracle Database 10.2.0.3 patch set. Make sure you follow the instructions in the patch set readme file.
Set the MGW_PRE_PATH variable as follows:
set MGW_PRE_PATH = JRE_HOME\bin\server
See the configuration steps in Chapter 18, "Getting Started with Oracle Messaging Gateway" in Oracle Streams Advanced Queuing User's Guide and Reference. The existing document sets the MGW_PRE_PATH variable to client because it is for Windows 32-bit.
The option for configuring central management of your database by Enterprise Manager 10g Grid Control is not available during Oracle RAC installation on Windows. Also not supported on Windows is the use of standalone Enterprise Manager Configuration Assistant or Database Configuration Assistant to configure central management for Oracle RAC.
If you want central management for the installed Oracle RAC database, then you will have to discover the Oracle RAC database target manually from Grid Control after the installation.
If you select Start > Programs > Oracle - HOME_NAME > Application Development > Oracle ODBC, the online help displays in English instead of Japanese.
This issue is tracked with Oracle bug 4490895.
During installation of Oracle Database 10g Release 2 on a pre-existing Oracle RAC cluster, you may receive the following error message:
CreateServiceMarkedForDeleteException_desc Click 'Help' for more information. Click 'Retry' to try again. Click 'Continue' to use the default value and go on. Click 'Cancel' to stop this installation. [Help] [Retry] [Continue] [Cancel]
Workaround:
Click Retry to enable this operation to proceed. If the retry fails, try again until the operation completes. Afterwards, the service should be created successfully.
This issue is tracked with Oracle bug 4508168.
The Oracle Universal Installer online help files for Oracle Database Companion CD are not specific to the Oracle Database Companion CD installation.
Workaround:
Refer to Chapter 3, "Installing the Oracle Database Companion CD Software," in Oracle Database Companion CD Installation Guide for Microsoft Windows (32-Bit)for detailed information about the installation process.
This issue is tracked with Oracle bug 4604992.
When a new Oracle RAC database is created either during installation or using Database Control Configuration Assistant (DBCA), the Database Control console may start before the new database instance has been registered with the listener. When this happens, in some conditions, some metrics will not be monitored. The following error in the Database Control console will appear:
java.lang.Exception: Can't get query descriptor or execution descriptor
Workaround:
Stop and restart the Database Control console. From the Start menu, select Programs, then Oracle - HOME_NAME, then Database Control.
This issue is tracked with Oracle bug 4591002.
If you run the Cluster Verfication Utility (CVU) from the runcluvfy.bat script prior to installing Oracle Clusterware, the first line of output may contain the following error message:
The system cannot find the file specified.
This is a benign message which you can ignore. CVU should continue processing normally and provide the required output a short time later.
This issue is tracked with Oracle bug 5369224.
If different user IDs are used for installing Oracle Database 10g and Oracle Clusterware, then restarting the system will result in OCR errors. See OracleMetaLink note 551478.1 for more information.
Workaround:
Oracle recommends that you apply the patch set 10.2.0.3 or higher to your Oracle Clusterware install before you patch Oracle Database.
This issue is tracked with Oracle bug 4748946.
The file oraxml10.dll gets copied to the system directory on a computer with previously installed Oracle Access Manager. This interferes with the installation of other Oracle products even after Oracle Access Manager is uninstalled, giving the following pop-up error:
The procedure entry point xqcGetXQXDOM could not be located in the dynamic link library oraxml10.dll.
Workaround:
Remove oraxml10.dll file from the system directory after uninstalling Oracle Access Manager.
This issue is tracked with Oracle bug 6852359.
The following are the sections covering known issues on Windows Vista and Windows Server 2008:
Managing User Accounts with User Account Control on Windows Vista and Windows Server 2008
Oracle Universal Installer Issue on Windows Vista and Windows Server 2008
Automatic Storage Management Tool Displays Error Messages on Windows Vista
Support for Microsoft Active Directory for Net Naming on Windows Vista
Shared Oracle Home Shortcuts Do Not Work on Windows Server 2008
Incorrect Operating System Appears on Windows Server 2008 Hosts
Oracle ODBC Help Shortcut Does Not Work on Windows Server 2008
Oracle Enterprise Manager Reconfiguration Issues on Windows Server 2008
Cluster Ready Services Installation Issue on Windows Server 2008
Driver Security Certificate Expiration Issue on Windows Server 2008
Configuration Assistants Intermittently Hang in Oracle RAC Environment on Windows Server 2008
To ensure that only trusted applications run on your computer, Windows Vista and Windows Server 2008 provide User Account Control. If you have enabled this security feature, then, depending on how you have configured it, Oracle Universal Installer prompts you for either your consent or your credentials when installing Oracle Database. Provide either the consent or your Windows Administrator credentials as appropriate.
You must have Administrator privileges to run some Oracle tools, such as Oracle Universal Installer, Database Configuration Assistant, Net Configuration Assistant, and OPatch, or to run any tool or application that writes to any directory within the Oracle home. If User Account Control is enabled, and you are logged in as the local Administrator, then you can successfully run each of these commands in the usual way. However, if you are logged in as "a member of the Administrator group," then you must explicitly start these tasks with Windows Administrator privileges. See "Starting Database Tools on Windows Vista" in Oracle Database Platform Guide for Microsoft Windows (x64) for more information.
All executables in the Oracle Clusterware Home should be run with administrative privileges.
To run a Windows shortcut with Windows Administrator privileges:
Click the Start menu button.
Navigate to Programs, then to Oracle - HOME_NAME.
Right-click the name of the command or application you want to run, then select Run as administrator.
Note:
Many Oracle Start menu shortcuts are coded to run as administrator. When prompted, select to trust the application or grant your permission to continue.To start a command prompt window with Windows Administrator privileges:
On your Windows Vista or Windows Server 2008 Desktop, create a shortcut for the command prompt window. An icon for that shortcut appears on the Desktop.
Right-click the icon for the newly created shortcut, and specify "Run as administrator."
When you open this window, the title bar reads Administrator: Command Prompt. Commands run from within this window are run with Administrator privileges.
The stamped disks are not displayed in Oracle Database Configuration Assistant on Windows Vista and Windows Server 2008.
Workaround:
Complete the following steps to resolve this issue:
Click Stamp Disk.
Delete the labels.
Click Stamp Disk.
Stamp the disks again.
This issue is tracked with Oracle bug 5944993.
If the Oracle Universal Installer is run from the Start menu to remove Oracle Database, then the database is not completely removed as the Start menu shows Oracle home. The top level directory is shown but no contents exist.
Workaround:
Remove the Oracle home entry from the Start menu manually or run the Oracle Universal Installer from the command prompt to ensure a clean removal of Oracle Database software.
This issue is tracked with Oracle bug 6983386.
If you configure Automatic Storage Management, the Automatic Storage Management tool displays the following error messages:
Note:
These are the OS error messages. Oracle tools display the Oracle error messages triggered by these OS errors.Workaround:
Complete the following steps to resolve this issue:
Create a desktop shortcut for Windows command window.
Right-click the desktop shortcut icon.
From the shortcut menu, select Run as administrator.
Run the asmtool.exe or asmtoolg.exe command in the command window.
This issue is tracked with Oracle bug 5873952.
Workaround:
Use the diskpart.exe command to create a raw partition and raw logical drive on the basic disk. You can also use the Disk Management MMC snap-in to create a raw partition or raw logical drive. However, you need to assign a drive letter to it when using the Disk Management MMC snap-in. Remove the drive letter after the partition or the drive is created. You enable automount before you create raw devices.
This issue is tracked with Oracle bug 5873952.
Workaround:
It is caused by the raw devices in dynamic disk. Dynamic disk is not supported so this error message can be ignored.
This issue is tracked with Oracle bug 5873952.
The following compilers are not supported on Windows Vista:
GCC
Micro Focus Net Express 4.0
Pro*COBOL will be supported when Micro Focus Net Express is available on Windows Vista
Oracle Net Directory Naming and Oracle Directory Objects are not supported with Active Directory from Windows Vista clients.
This issue is tracked with Oracle bug 5943019. This issue is fixed in the 10.2.0.4 patch set.
Starting Net Configuration Assistant or Database Configuration Assistant from shared Oracle home shortcut gives the following error:
Missing shortcut: windows is searching launch.exe
The shortcuts exit following the error.
Workaround:
Start the tools from the command prompt.
This issue is tracked with Oracle bug 6791055.
Oracle Enterprise Manager Grid Control displays incorrect operating system on Windows Server 2008. The Configuration section on the Host page shows 'Microsoft Windows NT Server 6.0 Service Pack 1 (32-bit)' as the operating system instead of Windows Server 2008.
This issue is tracked with Oracle bug 7110300.
You must run Oracle ODBC Help shortcut as administrator on Windows Server 2008. The following are the steps:
Click the Start menu button.
From the Programs menu, select Oracle - HOME_NAME, Application Development, and then Oracle ODBC Help.
Right-click Oracle ODBC Help, then select Run as administrator.
This issue is tracked with Oracle bug 6656171.
Reconfiguring Oracle Enterprise Manager on a database where database control is installed or on a new node when adding an instance may fail with the following error:
SEVERE: Error starting Database Control
Workaround:
Manually start the OracleDBConsoleSID service from the Services control panel of the node where it failed.
This issue is tracked with Oracle bug 7146689.
When formatting an Oracle Cluster File System drive during a Cluster Ready Services installation on Windows Server 2008, the following message appears and should be ignored:
You need to format the disk in drive H: before you can use it. Do you want to format it? [format disk] [cancel]
Workaround:
Click Cancel.
This issue is tracked with Oracle bug 7148951.
When installing Oracle Cluster Ready Services on Windows Server 2008, the prerequisite check fails with the following message:
Security certificates for OCFS and Orafence drivers on Windows Server 2008 have expired.
Workaround:
If you encounter the certificate expiration problem, then download the new drivers from OracleMetaLink and follow the instructions on the site to proceed with the installation.
This issue is tracked with Oracle bug 7320726.
Network Configuration Assistant and Database Configuration Assistant intermittently hang on Windows Server 2008 if Oracle RAC cluster nodes have Symantec Antivirus software enabled.
Workaround:
Uncheck the Enable Scanning option in the Symantec Antivirus software. Follow the instructions on the Symantec Web site:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2006030817095748
The Symantec case number is 311-992285. This issue is also tracked with Oracle bug 7332683.
The following sections contain information about issues related to Oracle Database 10g and associated products:
Transportable Tablespaces feature in Enterprise Manager Database Console
Enterprise Manager Database Control Exception Error To Ignore
Remote Users Not Being Added to ORA_DBA Group in Cluster Installations
MAX_IDLE_BLOCKER_TIME Does Not Work in Oracle RAC Environment
Deploying a .NET Stored Procedure Using Oracle Developer Tools for .NET
Dedicated Extproc Configuration for Oracle Database Extensions for .NET
Some Readme text files contain UNIX line breaks. If you double-click these files, they open in Notepad by default, but Notepad does not recognize UNIX line breaks. Use WordPad (write.exe) or edit.com instead.
If NTS authentication is used with an Oracle client as a .NET remote object impersonating a user credential, then NTS authentication fails with the error ora-12638 Credential Retrieval Failed. This happens due to the failure of the Windows API AcquireCredentialsHandle() in the NTS adapter inside the .NET remote object. Refer to OracleMetalink for more details.
Windows 2003 Service Pack 1 and Windows XP Service Pack 2 changes the security of WebDAV configurations. The following access error message may display when computers with Windows XP Service Pack 2 attempt to access an Oracle XML DB repository using the HTTP/Web Distributed Authoring and Versioning (WebDAV) protocol from Windows Explorer or other tools:
The folder you entered does not appear to be valid. Please choose another.
Perform the following steps to access Oracle XML DB from a client computer using the WebDAV protocol:
Create the following registry key on the client machine and set it to a non-zero value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\UseBasicAuth (DWORD)
Restart the client computer or restart the WebClient service.
See Also:
http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx#XSLTsection129121120120 for more information about the WebDAV security changes in Service Pack 2
"Postinstallation Configuration Tasks on Windows" in Oracle Database Platform Guide for Microsoft Windows (32-Bit) for more information about required Microsoft Firewall configuration tasks
If you install Oracle Database 10g Products, which include Oracle Workflow server, in a language other than English, the installation adds a submenu named Configuration and Migration Tools in English to the Windows Start menu under the corresponding Oracle home. This submenu includes only one item: Workflow Configuration Assistant. Other Oracle Database tools still appear under a separate, properly translated Configuration and Migration Tools submenu.
This issue is tracked with Oracle bug 4551276.
The transportable tablespaces feature accessible from the Maintenance tab has some limitations when generating and integrating tablespaces in Automatic Storage Management (ASM). The limitations and workarounds are described below:
Limitation:
There is a limitation when generating the transportable tablespace set on databases using ASM as storage. On Page 4, Files Page, if you provide the disk group name in the dump file location, you receive the following error when you submit the job:
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on ORA_DISK_1 channel at 08/22/2005 08:23:58 ORA-19504: failed to create file "+DATA/naresh/testtablespace1.260.566954713" ORA-17502: ksfdcre:4 Failed to create file +DATA/naresh/testtablespace1.260.566954713 ORA-15046: ASM file name '+DATA/naresh/testtablespace1.260.566954713' is not in single-file creation form
Workaround:
On Page 4, Files Page, provide a file system location instead of the disk group name. Data files and dump files are generated on the file system location you provide.
Limitation:
There is a limitation when integrating the transportable tablespace set on databases using ASM as storage. On Page 2, Datafile Destination Page, if in the data files table you provide the same disk group name for all data files, you can receive the following error when you submit the job:
RMAN> 2> 3> Starting backup at 22-AUG-05 allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid=152 devtype=DISK RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup command at 08/22/2005 09:08:36 ORA-15122: ASM file name '+MAKI/+MAKI/+MAKI/+MAKI/' contains an invalid file number
Workaround:
On Page 2, Datafile Destination Page, provide a unique disk group name for each data file.
This issue is tracked with Oracle bug 4566250.
Immediately after switching the Enterprise Manager Agent from nonsecure to secure mode, or vice versa, Enterprise Manager Database Control can show the following exceptions on the home page:
java.lang.Exception: Exception in sending Request :: null java.lang.Exception: IOException in reading Response :: Connection reset
The home page is fully functional despite these exceptions, and they should go away within five minutes. Starting and stopping Enterprise Manager Database Control should also make these exceptions go away.
This issue is tracked with Oracle bug 4562655.
When you install Oracle Database on Microsoft Windows, Oracle Universal Installer creates a Windows local group called ORA_DBA, and then adds your Windows username to it. Members of ORA_DBA automatically receive the SYSDBA privilege. However, for cluster installations, Oracle Universal Installer does not add the user to ORA_DBA if they have performed the installation remotely. As a result, this user cannot log in to SQL*Plus using the SYSDBA role.
Workaround:
Manually add remote users to ORA_DBA.
See Also:
Oracle Database Platform Guide for Microsoft Windows (x64) for more information onORA_DBA and instructions on manually granting administrator and operator privileges for an Oracle databaseThis issue is tracked with Oracle bug 4553355.
Do not remove the key values for the wait class metrics. Doing so removes them permanently and currently there is no easy way to recover them.
This issue is tracked with Oracle bug 4602952.
Oracle JVM is JDK 1.4 compatible. Because the supported JDK is version JDK 1.5, when you compile Java applications, be sure to pass additional cross-compilation options to javac as described below. This is complicated and error prone, since typos on jars paths remain obscure and there is no easy way to verify exactly which version of jars javac loads when driving compilation. For this reason, the best and safest approach is to load sources into Oracle JVM with loadjava, which in turn invokes the 1.4 version of javac directly in Oracle JVM.
Another safe approach is to compile sources and build jars using any client-side, JDK 1.4-based environment which can access the jars from the Windows x64 release (using network paths to ORACLE_BASE\ORACLE_HOME\javavm\lib\aurora.zip, ORACLE_BASE\ORACLE_HOME\jdbc\lib\classes12.jar, ORACLE_BASE\ORACLE_HOME\sqlj\lib\translator.zip, and so on, or physically copy these jars). After that, you can upload the jars using loadjava as usual.
If this is not feasible, you can compile using the 1.5 version of javac as follows. Javac must be forced to cross-compile, to use 1.4 jars and emit 1.4 bytecodes. For that, you must pass it by using the following set of flags:
-bootclasspath jdk14-jars -classpath other-jars -source 1.4 -target 1.4 -extdir ""
where dk14-jars is a list of standard JDK jars such as
myjdk1.4home\jre\rt.jar;myjdk1.4home\lib\tools.jar
The list can include any other JDK 1.4 jars as needed.
The flag -extdir is empty but Sun recommends using it.
To get good results, it is essential to verify that the pathnames to rt.jar and tools.jar are valid and they are in fact JDK 1.4 jars.
SQLJ in this release on Windows x64 is supported with JDK 1.5 with source compatibility set to 1.4 only. This complicates SQLJ program compilation. If code needs be compiled from source, care must be taken to force 1.5 javac to generate 1.4-compatible bytecodes.
The best and safest approach is to compile sources and build jars using a client-side, JDK 1.4-based environment which can access the jars for the Windows x64 release (using network paths to ORACLE_BASE\ORACLE_HOME\javavm\lib\aurora.zip, ORACLE_BASE\ORACLE_HOME\jdbc\lib\classes12.jar, ORACLE_BASE\ORACLE_HOME\sqlj\lib\translator.zip, and so on, or physical copy of these jars).
If this is not feasible, you can compile SQLJ sources using the 1.5 javac forced to cross-compile in 1.4 env and as 1.4 javac. For that, you must pass it by using the following flags:
-bootclasspath jdk14-jars -classpath other-jars -source 1.4 -target 1.4 -extdir ""
where jdk14-jars is a list of standard JDK jars such as
myjdk1.4home\jre\rt.jar;myjdk1.4home\lib\tools.jar
The list can include any other JDK 1.4 jars as needed.
The flag -extdir is for directories where 1.4 classes may reside.
To pass these options sthrough SQLJ to javac, use -C as follows:
sqlj -C-bootclasspath=jdk14-jars -C-classpath=other-jars -C-source=1.4 -C-target=1.4 -C-extdir="" abc.sqlj
This passes all the cross-compilation flags to the Java compiler, which assumes that the input Java files are Java 1.4-compatible, not having any Java1.5 specific features. However, the execution of SQLJ programs is done using Java Runtime Environment 1.5 (JRE 1.5).
SVMClassificationModelDetails.getBias() is not supported in this release because it is incompatible with J2SE 5.0.
The service account for OracleServiceSID, where SID represents the Oracle system identifier of the database instance, must be Local System, you can only use the UTL_FILE function for read and write operations on files that are stored on local file systems. In other words, due to this limitation, UTL_FILE cannot access remote or shared file systems.
This issue is tracked with Oracle bug 5591946.
Setting a value for MAX_IDLE_BLOCKER_TIME feature of Resource manager does not work as expected in Oracle RAC environment.
Workaround: Set a value for MAX_IDLE_TIME instead of setting a value for MAX_IDLE_BLOCKER_TIME.
This issue is tracked with Oracle bug 6114355.
When you connect to the database using Database Control, the page does not display the listener details.
Workaround:
After installing Oracle Database 10g Release 2, you must shutdown the Database Control with the command emctl stop dbconsole. Modify the targets.xml file located in ORACLE_BASE\ORACLE_HOME\hostname_SID\sysman\emd directory so that the value of the machinename field is the same for listener and database. Restart Database Control with the command emctl start dbconsole to display the listener details.
This issue is tracked with Oracle bug 6743916.
The diskgroup does not get mounted after restarting the computer.
Workaround:
Change startup type of OracleASMService+ASMInstanceName into manual from the Services Control Panel and restart the node.
This issue is tracked with Oracle bug 6688751.
32-bit Oracle Developer Tools for Visual Studio .NET, ODT.NET, can be used to deploy a .NET stored procedure on Windows x64 database. For the .NET stored procedure, select AnyCPU from the Platform Target list.
Oracle recommends the use of multithreaded extproc for Oracle Database Extensions for .NET. However, if dedicated extproc is used, then it is recommended to add ENVS attribute to the CLRExtProc entry in SID_LIST_LISTENER list of ORACLE_BASE\ORACLE_HOME\network\admin\listener.ora as shown below:
(SID_DESC = (SID_NAME = CLRExtProc) (ORACLE_HOME = Oracle_Home_Path) (PROGRAM = extproc) (ENVS="EXTPROC_DLLS=ONLY:Oracle_Home_Path\bin\oraclr10.dll") )
If the application creates JMS Topic Connections and sets the link options to all the three exit types, namely, MQ_SENDEXIT, MQ_RECEIVEEXIT, and MQ_SECURITYEXIT, then you may receive the following error:
[Linked-exception] javax.jms.JMSException: MQJMS1007: failed to create instance of exit class oracle.mgw.test.misc.mySecurityExit at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java :614) at com.ibm.mq.jms.MQConnection.checkExitType(MQConnection.java:4386)
Workaround:
Do not set all the three exit types together. You can use any two exit types together or any of the exit types individually.
This issue is tracked with Oracle bug 7248134.
The following are the corrections to the installation guides for Microsoft Windows x64:
The following text of the section 2.6.1, "IP Address Requirements," in Chapter 2, "Pre-Installation Tasks," of Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide states that the virtual IP address (VIP) should respond to a ping command:
During installation, Oracle Universal Installer uses the ping command to ensure that the VIP is reachable.
The preceding statement is incorrect. Before installation, the VIP address should be configured in DHCP or /etc/hosts, or both, but it must not be assigned to a server that can respond to a ping command.
This issue is tracked with Oracle bug 6017001.
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, 7 days a week. For TTY support, call 800.446.2398. Outside the United States, call +1.407.458.2479.
Oracle Database Release Notes, 10g Release 2 (10.2) for Microsoft Windows (x64)
B15680-07
Copyright © 2006, 2008, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
