Oracle Data Provider for .NET (32-bit and 64-bit) and Oracle Database Extensions for .NET (32-bit and 64-bit) are supported on Windows 8.1. The supported .NET framework versions are 4.5.1.

2 Latest Upgrade Information

For late-breaking updates and best practices about preupgrade, postupgrade, compatibility, and interoperability discussions, refer to Note 785351.1 on My Oracle Support (formerly OracleMetaLink) that links to the "Oracle 11gR2 Upgrade Companion" page.

4.1.1 Accessibility Software Recommendations for Windows 32-Bit

Our goal is to make Oracle products, services, and supporting documentation accessible to the disabled community. Oracle Database 11g Release 2 (11.2) supports accessibility features. To make best use of these accessibility features, Oracle recommends the following software configuration:

4.2.1 Microsoft Visual C++ Redistributable Packages

The Microsoft Visual C++ 2005 SP1 Redistributable Package is automatically installed with the Oracle Database 11g Release 2 (11.2) software. Do not remove this package from the Add or Remove Programs interface in the Control Panel.

4.2.2 Upgrading Windows 32-Bit to Windows 64-Bit Using Oracle OLAP

There are specific instructions for migrating 32-bit Oracle Online Analytical Processing (OLAP) option databases to 64-bit. These instructions are documented in Note 352306.1 on My Oracle Support (formerly OracleMetaLink) at

Oracle Database 11.2 supports Oracle SID having an underscore but it is not compatible with the earlier client releases with a bequeath connection. The issue affects any Oracle Database Client 11.1.0.7 or earlier client, when connecting to the database over a bequeath connection. This includes all OCI clients and Oracle Enterprise Manager agents that monitor the database.

Workaround:

Use only alphanumeric characters including hyphens for Oracle SID or connect to the database using TCP connection.

For volumes in disk groups that are mounted manually, you must also manually enable the volumes in that disk group before using them.

In Oracle Restart, to load Oracle Automatic Storage Management Cluster File System drivers during system initialization as an Administrator, you must manually reload the three drivers associated with Oracle ACFS: Oracle OKS, Oracle ADVM and Oracle ACFS.

This issue is tracked with Oracle bug 7700977.

4.2.5 Automatic Storage Management Service Is Disabled After System Restart

After an installation, the Automatic Storage Management Startup Type is set to Manual. Hence, Automatic Storage Management does not start when you restart the system.

Workaround:

In Services Control Manager, change the Startup Type to Automatic.

4.2.6 OCI Instant Client Version Update Issue

A new Oracle Database release does not update OCI Instant Client version.

Solution:

Use the OCIClientVersion feature to determine the client version instead of checking the dll version number.

This issue is tracked with Oracle bug 8372062.

4.2.7 ORA-00600 Error During Database Upgrade

When you upgrade from Oracle Database Release 9.2 to release 10.2, and then upgrade to release 11.2, the database upgrade fails with an ORA-00600 error.

[INS-40406] There is no previous version of grid software detected on the system.

Workaround:

If you are performing the upgrade on a remote node, a node other than the one on which Oracle Clusterware 11g Release 1 (11.1.0.6) was installed, then the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\inst_loc may not have been set on that node.

Ensure that you manually set the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\inst_loc to the location of the Oracle Inventory directory of the node on which you are performing the upgrade installation.

This issue is tracked with Oracle bugs 9210861 and 6527941.

4.2.9 EMVLOGGER.EXE Process Does Not Restart Automatically

If the EMVLOGGER.EXE process is terminated at the operating system level, it fails to restart automatically because of an existing log file.

Workaround:

Remove the emvlogger log file at Grid_home\evm\log\*_evmlogger.log, where Grid_home is the location of your Oracle Grid Infrastructure installation. The evmlogger.exe process should automatically restart after approximately one minute.

This issue is tracked with Oracle bug 9260650.

4.2.10 Windows Service Issue for Oracle Database

Manually shutting down an Oracle Database or stopping an Oracle ASM instance using CRSCTL utility or SQL*Plus does not stop its associated Windows service.

Workaround:

Using the Services management console, manually stop the Windows service associated with the Oracle instance. You can access the Services management console through the Control Panel, or you can stop the Oracle Database service, or Oracle ASM service directly using the following commands:

When attempting to upgrade Cluster Ready Services or Oracle ASM to 11.2 release using the Automatic Storage Management Configuration Assistant, the upgrade succeeds, but the configuration changes made to the Agents on a remote host fail to reload. As a result, Oracle Enterprise Manager Grid Control and Database Control cannot monitor the Oracle ASM and Cluster Ready Services targets.

Workaround:

Manually reload the remote agents after the upgrade using the following command:

emctl reload agent

This issue is tracked with Oracle bug 9398380.

4.2.12 Oracle MTS Recovery Service Issue When Installing Oracle RAC

In an Oracle RAC database installation, Oracle MTS Recovery Service on the remote nodes does not have the correct host name registered for string variable HOST under registry key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Protid_0. This variable contains the name of the host from where the installation was performed instead of the name of the local host. This registry variable is used by COM+ applications to pass information to Oracle databases so that they can connect back to the Windows computer if the database must resolve in-doubt COM+ transactions. The incorrect host name that is registered can cause transaction recovery issues.

Workaround:

To fix this, use Registry Editor (regedit) on the remote Windows system and look under the registry key:

When running rootcrs.pl or roothas.pl to configure, upgrade, or deconfigure Oracle Grid Infrastructure, the script does not display the success or failure status in the command window.

Workaround:

None. Check the log file generated at the following location to know the status of the script:

Grid_home/cfgtoollogs/rootcrs_host_name.log

This issue is tracked with Oracle bug 9473262.

4.2.14 Issue Encountered When Special Characters Are Used in Network Interface Names

While installing or upgrading Oracle Grid Infrastructure for a cluster, you might encounter an issue if special characters, including non-ASCII characters and single quotation marks, are used in network connection names. The following message is recorded in the Oracle Universal Installer log:

ATTENTION: Bareword found where operator expected at (eval 20) line 1,
near "'"node-vip/netmask/excutabled'acc"
ATTENTION: (Missing operator before acc?)
ATTENTION: Parameter ORACLE_HOME not defined at
C:\app\11.2.0\grid\crs\install/crsconfig_lib.pm line 8722.

4.2.17 Deinstallation Issues with ODP.NET

While removing a single instance Oracle Database, Oracle Database Client, or Oracle RAC on 64-bit Windows, you might see some unnecessary characters or lines printed in winprod_cleanup.out on a non-English operating system. If the operating system is English, then you might see the following message:

This action is only valid for products that are currently installed.

Workaround:

Ignore these unnecessary characters and the message.

This issue is tracked with Oracle bug 9440539.

4.2.18 Deinstallation Tool Does Not Remove Oracle Home

When using the Deinstallation Tool to remove an Oracle home that has Oracle Enterprise Manager Database Control configured and that was installed on Oracle ACFS, the ORACLE_BASE\ORACLE_HOME\host_sid\sysman directory and its sub directories cannot be deleted, preventing the Oracle home from being removed.

Workaround:

Before performing these operations, run the following command as the Administrator user:

4.2.20 Deinstallation Tool Does Not Remove ocfs.sys File

The Deinstallation Tool fails to remove the ocfs.sys file when deinstalling Oracle RAC.

Workaround:

Manually remove the ocfs.sys file:

system_drive\Windows\System32\drivers\ocfs.sys

This issue is tracked with Oracle bug 9498036.

4.2.21 Deinstallation Tool Does Not Detect Oracle RAC Home

If you are deinstalling the 11.2.0.1.0 Oracle RAC Database software installed on Oracle ACFS mounted drive using the Deinstallation Tool, you might see the following message during the Oracle Configuration Manager (OCM) deconfiguration:

Oracle Home does not exists, but CCR is configured

Workaround:

You can ignore this message, the OCM gets deconfigured successfully.

This issue is tracked with Oracle bug 9545478.

4.2.22 Using Deinstallation Tool for Oracle RAC Returns Errors

The Deinstallation Tool cannot delete files that are still in use because one or more processes or services were not stopped successfully. The deinstall output shows error messages such as:

Failed to delete the file file_name

Workaround:

Remove the Oracle home manually after the server is restarted.

This issue is tracked with Oracle bug 9446472.

4.2.23 Time Issue with Deinstallation Tool to Remove Oracle RAC Home

When using the Deinstallation Tool to remove an Oracle RAC home that was installed on Oracle ACFS, the tool takes a longer amount of time than expected to finish.

Workaround:

None. Wait an additional 20-30 minutes for the deinstallation tool to finish.

When using the Deinstallation Tool to remove Oracle Grid Infrastructure for a cluster in silent mode, the tool fails with the following error message:

ERROR: As the privileged user, Execute \deinstall\crsdc.bat on every
node in this cluster except for this node, and then execute
\deinstall\rootdeinstall.bat on this node to remove the configuration of the
Oracle Clusterware and to completely remove the Oracle software

Workaround:

Follow these steps when the deinstallation fails:

Run crsdc.bat on all the nodes as instructed by the Deinstallation Tool.

If you install 32-bit Oracle software and 64-bit Oracle software on the same server, then you should use different Oracle Base directories for the 32-bit Oracle software and the 64-bit Oracle software.

This issue is tracked with Oracle bug 9502109.

4.2.26 User Issue with ORA_DBA Group on Remote Nodes

When installing an Oracle RAC Database on a cluster using a local user (non-domain user) account, the user account is not added to the ORA_DBA group on remote nodes. This prevents the local user from connecting to the database as SYSDBA using operating system authentication.

Workaround:

Manually add this local user to the ORA_DBA group on all the remote nodes or install as a domain user.

This issue is tracked with Oracle bug 9524516.

4.2.27 Oracle Clusterware Resource Status Issue

In an Oracle RAC cluster with 2 or more nodes, if you restart one node, and then, while the node is being restarted, use CRSCTl on another node to query the status of the Oracle Clusterware resources, then CRSCTL either displays no information, or returns the error message:

In an Oracle Clusterware environment where DHCP is configured and GNS is enabled, if the non-qualified SCAN is resolved by DNS, it can cause Enterprise Manager Configuration Assistant or Database Configuration Assistant to fail with the following error message:

SEVERE: Scan Listener is not up or database service is not registered with it.
Start the Scan Listener and register database service and run EM Configuration Assistant again

Workaround:

When using GNS, ensure that the SCAN, qualified by either the default domain on the network, or qualified by any domain in the cluster nodes' domain search order, is not resolvable through DNS for the network.

During an Oracle Grid Infrastructure for a cluster installation, upgrade of Oracle Clusterware 10.2.0.5 to Oracle Clusterware 11.2.0.1 fails. The installer displays the following message:

Grid Infrastructure Configuration failed.

Solution:

Upgrading directly from Oracle Clusterware 10.2.0.5 to Oracle Clusterware 11.2.0.1 is not supported. Either complete the upgrade by running an Oracle Grid Infrastructure for a cluster 11.2.0.2 installation, or contact support for a one-off patch for the Oracle Clusterware 11.2.0.1 software.

This issue is tracked with Oracle bug 9776578.

4.3 Other Known Issues for Release 11.2.0.1

The following sections contain information about issues related to Oracle Database 11g and associated products:

4.3.7 Installing Online Patches on Windows Systems

Opatch tool version 11.2.0.1.1 is available on My Oracle Support as Patch 6880880 for Oracle Database 11g Release 2. Download and install Opatch Tool version 11.2.0.1.1 before applying online patches on Windows systems.

To list the database instances patched by an online patch, run the opatch lsinventory -details command. Ensure that you run the opatch rollback command instead of opatch disableOnlinepatch command to disable and remove an online patch from the final database instance in a node. To remove the online patch that is in a disabled state, run the disableOnlinepatch command. To remove the online patch in a disabled state, use -no_sysmod flag with opatch rollback command, only when opatch lsinv -details does not list any instances for that patch. For example, use opatch rollback -id 1234 -no_sysmod, only when opatch lsinv -details show no instances patched for bug 1234.

When the Oracle ACFS mount registry resource or the Oracle ACFS individual file system resource mounts an Oracle ADVM volume on a drive letter, the drive is not visible in Windows Explorer. This only affects the visibility of the drive letter in Windows Explorer; the volume is mounted and fully accessible using the command line, and is visible using the acfsutil.exe utility.

Workaround:

You must log out of your Windows session and log back in to view the driver letter in Windows Explorer.

This issue is tracked with Oracle bug 9343876.

4.3.9 Download Microsoft Handle Utility When Using Oracle ACFS

The Microsoft handle utility is required for proper operation of Oracle ACFS High Availability resources managed by Oracle Clusterware. Oracle Clusterware resources may not shut down properly if this command is not included.

After downloading, place the Handle utility in the BIN directory of your Grid home.

Note:

Ensure that the Grid home is included in the PATH environment variable for your current session.

This issue is tracked with Oracle bug 9349433.

4.3.10 Oracle Grid Infrastructure Listeners Issue

After installing Oracle Grid Infrastructure, the default listener does not listen on public addresses. As a result, even though the listener is available, the listener does not service the database or Oracle ASM instances.

Workaround 1:

If you are not using GNS with DHCP, then perform the following steps:

Add the local IP address and host name information to %Systemroot%\System32\Drivers\Etc\Hosts.

For example, IP addresshost name such as 192.0.2.254dbhost.

Restart the Oracle Grid Infrastructure listener.

This issue is tracked with Oracle bug 9382523.

Workaround 2:

If you have configured GNS and use DHCP to assign the addresses for the cluster nodes, then configure DHCP so that the IP address assigned to the host name for each cluster node (the public IP address) has a smaller numeric value than the IP addresses assigned for the Virtual IP (VIP) address, GNS VIP address, or SCAN VIP address for a node.

For example, you could use IP addresses in the range of xxx.xxx.xxx.0 – xxx.xxx.xxx.099 for only host IP addresses, and all other IP address assignments must use a value of xxx.xxx.xxx.100 or higher.

This issue is tracked with Oracle bug 9441288.

4.3.11 Shared Oracle Home Shortcuts Do Not Work on Windows Server 2008

Start the tools from a Windows command prompt with Administrator privileges.

This issue is tracked with Oracle bug 7525053.

4.3.12 addNode.bat Script Shows Success Even When One or More Node Additions Fail

When running the addNode.bat script to add one or more nodes to your cluster, if there was a failure during any installation on any of the new nodes, they are removed from the list of nodes to be adding to the cluster. As a result the updatenodelist command called after the node addition process returns a status of success even if there was a failure in adding a node.

Workaround:

None. Verify that the new nodes are correctly added to the node list after the addNode procedure. If not, check the addNode logs for any error messages. Correct the problem and repeat the addNode procedure.

This issue is tracked with Oracle bug 9481472.

4.3.13 Inventory Issue with addNode.bat Script

After running the addNode.bat script, the inventory on the new nodes does not reflect the newly added home.

4.3.14 Data Pump Worker Processes Do Not Run on Different Oracle RAC Instances

When running a Data Pump job in an Oracle RAC environment, if you specify a value greater than 1, then Data Pump should use the Oracle RAC resources and start additional worker processes on other nodes in the cluster up to the value of the parallel parameter. However, for Windows systems, all the Data Pump processes run on the instance where the job is created; worker processes on other nodes are not started.

Workaround:

None.

This issue is tracked with Oracle bug 9448829.

4.3.15 ORA_DBA Group Not Created By addNode.bat Script

When you use the addNode.bat script to add a node to your cluster, the operating system group ORA_DBA is not created on the nodes being added to the cluster or the user running the addNode.bat script is not added to the ORA_DBA group on the nodes being added to the cluster. This causes the root.bat script to fail.

Workarounds:

If you have not yet run the root.bat script as prompted by addNode.bat, then you can manually create the ORA_DBA operating system group on the nodes being added to the cluster and add the user that is running the addNode.bat script to that ORA_DBA group.

When installing software in a cluster or adding a node to a cluster, the same operating system user performing the installation on the first node must exist on each node, and the user must be explicitly declared as a member of the local Administrators group and the ORA_DBA group on each node in the cluster.

Alternatively, you can run the following command from Oracle home in which Oracle Clusterware is installed as the user that runs addNode.bat:

4.3.16 ODP.NET Help Not Installed on 64-Bit Windows

If you install 32-bit Oracle software on a 64-bit Windows computer, then help for ODP.NET is not installed.

Workaround:

Use the .NET Help Setup Wizard to manually install the dynamic help. To start the wizard on an English locale, run the DataProviderHelp_en.msi file from the ORACLE_BASE\ORACLE_HOME\ODP.NET\help directory. For the Japanese locale, run the DataProviderHelp_ja.msi file from the same directory.

This issue is tracked with Oracle bug 9524039.

4.3.17 Using Oracle ACFS for the Database Home and LOB Files

If you place the Oracle Database home on Oracle ACFS, and the database uses LOB files, which are also stored on Oracle ACFS, then the Oracle ACFS home must be of the format, DRIVE_LETTER:\directory. For example:

g:\dir
g:\dir1\dir2

Otherwise, LOB related errors are shown when accessing the LOB (as in the sample schema for a basic installation). For example:

ERROR at line 1:
ORA-22288: file or LOB operation FILEOPEN failed
ORA-06512: at "SYS.DBMS_LOB", line 744
ORA-06512: at "XDB.DBMS_XDB", line 301
ORA-06512: at line 4

Under certain conditions, errors may be issued during an Oracle Grid Infrastructure shutdown relating to activity on Oracle ACFS file systems:

acfsdismount: ACFS-04007: dismount failed due to open files on the volume

Workaround:

To avoid these errors, unmount all Oracle ACFS file systems manually before Oracle Grid Infrastructure shutdown. You can use the Windows handle and wmic commands to identify processes which are active on the file systems. Ensure that these processes are no longer active, unmount all ACFS file systems, then reissue Oracle Grid Infrastructure shutdown.

Find and stop the java process for the ora.eons resource, oracle.supercluster.impl.cluster.EONSServerImpl.

To determine the process ID (PID) of the process, you can use a utility such as the Microsoft Windows Management Utility. For example:

wmic RETURN process

While logged in as an Administrator user, start the Microsoft Windows Management Utility using the following command:

C:\> wmic

When the utility prompt appears, run the process command, as shown here:

wmic:root\cli> process

A long list of processes and the command used to start those processes is displayed. For the processes named java.exe, find the one associated with the eons process. It will appear similar to the following, where Grid_home is the directory in which Oracle Grid Infrastructure is installed on the local node:

The GSD resource should stay OFFLINE in a cluster environment when there are no Oracle 9i databases configured. After you restart Oracle Clusterware, it is possible the GSD resource status could be changed to ONLINE. There is no issue with keeping the GSD resource ONLINE, but if this resource is not needed (there are no Oracle 9i databases to be managed) and you want to keep this resource OFFLINE, then use the suggested workaround.

Workaround:

Use the following command to stop GSD on all the nodes:

srvctl stop nodeapps -g

Also, ensure that the file, Grid_home\admin\gsd.pid, does not exist on any of the cluster nodes.

This issue is tracked with Oracle bug 9489026.

4.3.21 VIP Does Not Fail Back When Public Network Interface Card (NIC) Status Changes Rapidly

If the Public NIC is disabled and enabled within a short span of time, then the VIP resources do not fail back to the node where the NIC was enabled.

5.2.1 Oracle ACFS Drivers Installation Error

Oracle ASM Configuration Assistant (ASMCA) may report that the Oracle ASM Cluster File System (ACFS) drivers are not installed when in reality the drivers are installed but not loaded. This is seen in the Oracle ASM Instances tab of ASMCA user interface after Oracle ASM is configured. There is no functionality impact and you can check if the drivers are installed by running grid_home\bin\acfsdriverstate installed. This utility prints the correct information.

Oracle Database 11.2 supports Oracle SID having an underscore but it is not compatible with the earlier client releases with a bequeath connection. The issue affects any Oracle Database Client 11.1.0.7 or earlier client, when connecting to the database over a bequeath connection. This includes all OCI clients and Oracle Enterprise Manager agents that monitor the database.

Workaround:

Use only alphanumeric characters including hyphens for Oracle SID or connect to the database using TCP connection.

[INS-40406] There is no previous version of grid software detected on the system.

Workaround:

If you are performing the upgrade on a remote node, a node other than the one on which Oracle Clusterware 11g Release 1 (11.1.0.6) was installed, then the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\inst_loc may not have been set on that node.

Ensure that you manually set the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\inst_loc to the location of the Oracle Inventory directory of the node on which you are performing the upgrade installation.

When attempting to upgrade Cluster Ready Services or Oracle ASM to 11.2 release using the Automatic Storage Management Configuration Assistant, the upgrade succeeds, but the configuration changes made to the Agents on a remote host fail to reload. As a result, Oracle Enterprise Manager Grid Control and Database Control cannot monitor the Oracle ASM and Cluster Ready Services targets.

Workaround:

Manually reload the remote agents after the upgrade using the following command:

emctl reload agent

This issue is tracked with Oracle bug 9398380.

5.2.7 Deinstallation Tool Does Not Remove Oracle Home

When using the Deinstallation Tool to remove an Oracle home that has Oracle Enterprise Manager Database Control configured and that was installed on Oracle ACFS, the ORACLE_BASE\ORACLE_HOME\host_sid\sysman directory and its sub directories cannot be deleted, preventing the Oracle home from being removed.

Workaround:

Before performing these operations, run the following command as the Administrator user:

When running rootcrs.pl or roothas.pl to configure, upgrade, or deconfigure Oracle Grid Infrastructure, the script does not display the success or failure status in the command window.

Workaround:

None. Check the log file generated at the following location to know the status of the script:

Grid_home/cfgtoollogs/rootcrs_host_name.log

This issue is tracked with Oracle bug 9473262.

5.2.10 Time Issue with Deinstallation Tool to Remove Oracle RAC Home

When using the Deinstallation Tool to remove an Oracle RAC home that was installed on Oracle ACFS, the tool takes a longer amount of time than expected to finish.

Workaround:

None. Wait an additional 20-30 minutes for the deinstallation tool to finish.

This issue is tracked with Oracle bug 9478372.

5.2.11 Oracle MTS Recovery Service Issue When Installing Oracle RAC

In an Oracle RAC database installation, Oracle MTS Recovery Service on the remote nodes does not have the correct host name registered for string variable HOST under registry key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Protid_0. This variable contains the name of the host from where the installation was performed instead of the name of the local host. This registry variable is used by COM+ applications to pass information to Oracle databases so that they can connect back to the Windows computer if the database must resolve in-doubt COM+ transactions. The incorrect host name that is registered can cause transaction recovery issues.

Workaround:

To fix this, use Registry Editor (regedit) on the remote Windows system and look under the registry key:

When using the Deinstallation Tool to remove Oracle Grid Infrastructure for a cluster in silent mode, the tool fails with the following error message:

ERROR: As the privileged user, Execute \deinstall\crsdc.bat on every
node in this cluster except for this node, and then execute
\deinstall\rootdeinstall.bat on this node to remove the configuration of the
Oracle Clusterware and to completely remove the Oracle software

Workaround:

Follow these steps when the deinstallation fails:

Run crsdc.bat on all the nodes as instructed by the Deinstallation Tool.

Removing Oracle home fails with file in use errors as the services and processes running from the Oracle home are not removed completely by Microsoft's Service Control Manager before the Oracle home removal.

Workaround:

Remove the Oracle home manually after the deinstall tool exits.

This issue is tracked with Oracle bug 10035858.

5.2.14 Deinstallation Tool Fails to Remove Shared Oracle RAC Home

When using the Deinstallation tool, deinstall.bat, to remove a shared Oracle RAC home, you get the error message, Failed to delete directory.., for the Oracle home being removed.

Workaround:

Use Process Monitor, PMON, to locate and stop the processes running out of the Oracle home being removed. Then remove the directory.

5.2.16 Issues While Installing Oracle Database with Oracle ASM

If you install Oracle Database release 11.1 or earlier and during installation choose to create a database with storage configured on Oracle ASM release 11.2.0.2, then the installation fails while the configuration tools are running, specifically Database Configuration Assistant.

Workaround:

Install the Oracle Database release 11.1 or earlier software and choose the software only installation option. After the installation completes, create the single-instance database by launching Database Configuration Assistant from the newly installed Oracle home. For example, run the following command from a command prompt:

If you run an Oracle Database release 10.2 or 11.1 on Oracle Grid Infrastructure release 11.2, after a node is restarted, the database instance resource running on that node may erroneously report an online state when it is actually offline. Any service associated with the instance fails to start.

Workaround:

Manually issue a start against the instance by running the following commands on the node that was restarted:

After a successful Oracle Clusterware installation, check the CRS status:

"crsctl stat res -t"

If any service is offline, start the service.

For example, if ora.DATA.dg service on node2 is offline, run the following command to start the service:

"srvctl start diskgroup -g data -n node2"

This issue is tracked with Oracle bug 10250914.

5.2.19 Database Configuration Assistant Does Not Run When Installing Oracle ACFS

The GetVolumePathname Microsoft API on Windows Server 2008 R2 shows incorrect results when installing an Oracle ACFS file system hosted on an Oracle ADVM volume. As a result, Database Configuration Assistant and other configuration tools cannot run during the Oracle ACFS file system install.

When using the Deinstallation Tool to remove a Clusterware home, you might encounter the issue that removing service, OracleClusterVolumeService, failed.

Workaround:

Manually remove the service, OracleClusterVolumeService.

This issue is tracked with Oracle bug 9405729.

5.2.22 Deinstallation Issues When Removing Oracle Home in Sequence

After removing a database Oracle home or a database client Oracle home, the deinstallation might hang if you try to remove another Oracle home, without any new Oracle home installed in between the two deinstallations.

Workaround:

Stop the reg.exe process from the Task Manager application to continue the deinstallation of the Oracle home.

This issue is tracked with Oracle bug 10354341.

5.3 Other Known Issues for Release 11.2.0.2

The following sections contain information about issues related to Oracle Database 11g and associated products:

Due to limitations in the Windows Server 2008 operating system, Oracle ACFS on Windows Server 2008 has certain limitations with file changes made through memory mapped access. If file changes are made through memory mapped access on one node, then those changes may not be seen on other nodes until the application on the first node either explicitly flushes the view of the file, or unmaps the view, and closes the file. In addition, if an Oracle ACFS snapshot is created while modifications to files made through memory mapping are in the page cache and have not been flushed to disk, these changes are not reflected in the snapshot.

These limitations do not exist on Windows Server 2008 R2.

5.3.3 Using Oracle ACFS for the Database Home and LOB Files

If you place the Oracle Database home on Oracle ACFS, and the database uses LOB files, which are also stored on Oracle ACFS, then the Oracle ACFS home must be of the format, DRIVE_LETTER:\directory. For example:

g:\dir
g:\dir1\dir2

Otherwise, LOB related errors are shown when accessing the LOB (as in the sample schema for a basic installation). For example:

ERROR at line 1:
ORA-22288: file or LOB operation FILEOPEN failed
ORA-06512: at "SYS.DBMS_LOB", line 744
ORA-06512: at "XDB.DBMS_XDB", line 301
ORA-06512: at line 4

When installing .NET related products such as Oracle Data Provider for .NET, Oracle Providers for ASP.NET, and so on, to an ORACLE_HOME and ORACLE_BASE that are located on a mapped drive on either 32-bit or 64-bit operating system, you may encounter a System.IO.FileLoadException exception indicating that .NET Framework failed to load OraProvCfg.exe due to a failure in granting minimum permission requests.

Workaround:

Install .NET Framework 2.0 SP2 or later for the appropriate operating system.

This issue is tracked with Oracle bug 10225338.

5.3.6 Issues While Specifying the Software Updates Download Location

Oracle Universal Installer does not support spaces and double quotation marks in the path of the download location when the Software Updates option is chosen.

Start the tools from a Windows command prompt with Administrator privileges.

This issue is tracked with Oracle bug 7525053.

5.3.8 Download Microsoft Handle Utility When Using Oracle ACFS

The Microsoft handle utility is required for proper operation of Oracle ACFS High Availability resources managed by Oracle Clusterware. Oracle Clusterware resources may not shut down properly if this command is not included.

After downloading, place the Handle utility in the BIN directory of your Grid home.

Note:

Ensure that the Grid home is included in the PATH environment variable for your current session.

This issue is tracked with Oracle bug 9349433.

5.3.9 Oracle Grid Infrastructure Listeners Issue

After installing Oracle Grid Infrastructure, the default listener does not listen on public addresses. As a result, even though the listener is available, the listener does not service the database or Oracle ASM instances.

Workaround 1:

If you are not using GNS with DHCP, then perform the following steps:

Add the local IP address and host name information to %Systemroot%\System32\Drivers\Etc\Hosts.

For example, IP addresshost name such as 192.0.2.254dbhost.

Restart the Oracle Grid Infrastructure listener.

This issue is tracked with Oracle bug 9382523.

Workaround 2:

If you have configured GNS and use DHCP to assign the addresses for the cluster nodes, then configure DHCP so that the IP address assigned to the host name for each cluster node (the public IP address) has a smaller numeric value than the IP addresses assigned for the Virtual IP (VIP) address, GNS VIP address, or SCAN VIP address for a node.

For example, you could use IP addresses in the range of xxx.xxx.xxx.0 – xxx.xxx.xxx.099 for only host IP addresses, and all other IP address assignments must use a value of xxx.xxx.xxx.100 or higher.

This issue is tracked with Oracle bug 9441288.

5.3.10 Installing Online Patches on Windows Systems

Opatch tool version 11.2.0.1.1 is available on My Oracle Support as Patch 6880880 for Oracle Database 11g Release 2. Download and install Opatch Tool version 11.2.0.1.1 before applying online patches on Windows systems.

To list the database instances patched by an online patch, run the opatch lsinventory -details command. Ensure that you run the opatch rollback command instead of opatch disableOnlinepatch command to disable and remove an online patch from the final database instance in a node. To remove the online patch that is in a disabled state, run the disableOnlinepatch command. To remove the online patch in a disabled state, use -no_sysmod flag with opatch rollback command, only when opatch lsinv -details does not list any instances for that patch. For example, use opatch rollback -id 1234 -no_sysmod, only when opatch lsinv -details show no instances patched for bug 1234.

This issue is tracked with Oracle bugs 8843060 and 9440270.

5.3.11 Inventory Issue with addNode.bat Script

After running the addNode.bat script, the inventory on the new nodes does not reflect the newly added home.

If you install Oracle Database release 11.1 or earlier and during installation choose to create a database with storage configured on Oracle ASM release 11.2.0.3, then the installation fails while the configuration tools are running, specifically Database Configuration Assistant.

Workaround:

Install the Oracle Database release 11.1 or earlier software and choose the software only installation option. After the installation completes, create the single-instance database by launching Database Configuration Assistant from the newly installed Oracle home. For example, run the following command from a command prompt:

If you install a 32-bit Oracle Database and a 64-bit Oracle Database in the same ORACLE_BASE, then it may lead to unexpected results when using the deinstallation tool to remove one of the databases. The deinstallation tool removes all the Oracle home under Oracle base if these Oracle homes do not use the same central inventory.

Workaround:

Avoid using multiple central inventories. Do not use the same ORACLE_BASE for 32-bit and 64-bit database installations.

This issue is tracked with Oracle bugs 12808859 and 12864734.

6.2.7 Deinstallation Tool Fails to Remove Registry Entries

When deinstalling a single instance Oracle Database, Oracle Database Client, or Oracle RAC (only 64-bit Windows servers), some registry entries are not removed.

You may also see ORA-00904 and ORA-00942 errors in the relod.log file, created by running catrelod.sql.

Workaround:

None

This issue is tracked with Oracle bug 12875131.

6.2.9 Prerequisite Check Issue with Firewall on Windows x64

While performing prerequisite checks during Oracle Grid Infrastructure installation on Windows x64, if the Windows Firewall is not disabled, then the Cluster Verification Utility displays the following warning:

PRVG-5906: Windows firewall is enabled on the node "node_list"
Cause: Windows firewall status was found to be enabled.
Action: To disable Windows firewall, add the REG_DWORD registry entry by name
'EnableFirewall' and value 0 to the
'HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Tcpip/SharedAccess/Param
eters/FirewallPolicy/StandardProfile' and
'HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Tcpip/SharedAccess/Param
eters/FirewallPolicy/DomainProfile' sub key. It is recommended to back up the
Windows Registry before proceeding with any changes, Restart your system to
make your changes effective after changing the registry.

Incorrect registry key to disable the firewall is specified in the message.

Workaround:

The correct registry key is HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/SharedAccess/Parameters/FirewallPolicy/StandardProfile and HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/SharedAccess/Parameters/FirewallPolicy/DomainProfile.

When you run the deinstallation tool in silent mode using ORACLE_HOME\deinstall\deinstall.bat, the temporary files and folders are not cleaned up after exiting the deinstallation tool and running the rootdeinstall.bat file.

Workaround:

Manually delete the files or folders that are not required under the system level %Temp%\deinstall_timestamp folder.

When running the deinstallation tool with the -silent and -paramfile options, and the parameter file specifies that the Oracle ASM disk groups should not be dropped, the command completes but the following services and entries are not removed from the registry:

When you upgrade Oracle Grid Infrastructure to release 11.2.0.3 and start installing Oracle RAC database release 11.2.0.1, then the Oracle Database Configuration Assistant shows the following error message towards the end of the database creation:

java.exe - Entry Point Not Found
The procedure entry point clsunsinit could not be located in the dynamic link library orahasgen11.dll.
---------------------------
OK
---------------------------

Workaround:

Click OK and proceed with the database creation process. Log into the Oracle Database Enterprise Manager Control and navigate to the Cluster home page. Click Monitoring Configuration and update the eONS port for cluster target property.

This issue is tracked with Oracle bug 13074121.

6.2.15 Service Not Removed When Deleting a Node on Shared Oracle RAC

When deleting a node on shared Oracle RAC home, OraClrAgnt service is stopped but not removed.

Removing Oracle home fails with file in use errors as the services and processes running from the Oracle home are not removed completely by Microsoft's Service Control Manager before the Oracle home removal.

When attempting to upgrade Cluster Ready Services or Oracle ASM to 11.2 release using the Automatic Storage Management Configuration Assistant, the upgrade succeeds, but the configuration changes made to the Agents on a remote host fail to reload. As a result, Oracle Enterprise Manager Grid Control and Database Control cannot monitor the Oracle ASM and Cluster Ready Services targets.

Workaround:

Manually reload the remote agents after the upgrade using the following command:

emctl reload agent

This issue is tracked with Oracle bug 9398380.

6.2.19 Deinstallation Tool Does Not Remove Oracle Home

When using the Deinstallation Tool to remove an Oracle home that has Oracle Enterprise Manager Database Control configured and that was installed on Oracle ACFS, the ORACLE_BASE\ORACLE_HOME\host_sid\sysman directory and its sub directories cannot be deleted, preventing the Oracle home from being removed.

Workaround:

Before performing these operations, run the following command as the Administrator user:

6.2.20 Oracle MTS Recovery Service Issue When Installing Oracle RAC

In an Oracle RAC database installation, Oracle MTS Recovery Service on the remote nodes does not have the correct host name registered for string variable HOST under registry key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Protid_0. This variable contains the name of the host from where the installation was performed instead of the name of the local host. This registry variable is used by COM+ applications to pass information to Oracle databases so that they can connect back to the Windows computer if the database must resolve in-doubt COM+ transactions. The incorrect host name that is registered can cause transaction recovery issues.

Workaround:

To fix this, use Registry Editor (regedit) on the remote Windows system and look under the registry key:

[INS-40406] There is no previous version of grid software detected on the system.

Workaround:

If you are performing the upgrade on a remote node, a node other than the one on which Oracle Clusterware 11g Release 1 (11.1.0.6) was installed, then the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\inst_loc may not have been set on that node.

Ensure that you manually set the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\inst_loc to the location of the Oracle Inventory directory of the node on which you are performing the upgrade installation.

Oracle Database 11.2 supports Oracle SID having an underscore but it is not compatible with the earlier client releases with a bequeath connection. The issue affects any Oracle Database Client 11.1.0.7 or earlier client, when connecting to the database over a bequeath connection. This includes all OCI clients and Oracle Enterprise Manager agents that monitor the database.

Workaround:

Use only alphanumeric characters including hyphens for Oracle SID or connect to the database using TCP connection.

If "Oracle America, Inc." is not in list of the trusted publishers of the node, then the following message appears:

Would you like to install this device software?
Name: Oracle Network Protocol
Publisher: Oracle America, Inc.

Select Install to install the driver.

Run the following command on all the nodes in the cluster after installing the oraarp driver:

sc config oraarpdrv start= auto

Stop the Oracle GNS service. To determine if GNS is configured, run the following command:

Grid_home\bin\srvctl config gns

To stop the GNS service, run the following command:

Grid_home\bin\srvctl stop gns

Stop the SCAN resource using the following command:

Grid_home\bin\srvctl stop scan -f

Stop all node applications running on the nodes in the cluster. To determine the node names for your cluster, run the following command:

Grid_home\bin\olsnodes -l

To stop the node application resources, use the following command where node_list is a comma-delimited list of node names:

Grid_home\bin\srvctl stop nodeapps -n node_list -f

Restart the node applications on all nodes in the cluster using the following command where node_list is a comma-delimited list of node names:

Grid_home\bin\srvctl start nodeapps -n node_list

Restart the SCAN resource using the following command:

Grid_home\bin\srvctl start scan

If necessary, here are the steps to uninstall Oracle ARP protocol driver:

Stop the Oracle ARP protocol driver:

net.exe stop oraarpdrv

Open the Windows Networks Connections management interface. Right-click Properties on a public network interface, or from the Start menu, select Control Panel, then Network and Internet, and then Network Connections.

If you run an Oracle Database release 10.2 or 11.1 on Oracle Grid Infrastructure release 11.2, after a node is restarted, the database instance resource running on that node may erroneously report an online state when it is actually offline. Any service associated with the instance fails to start.

Workaround:

Manually issue a start against the instance by running the following commands on the node that was restarted:

6.2.25 Oracle ASM Disk Group Does Not Mount on Remote Node After a Database Upgrade on Windows x64

After upgrading Oracle Grid Infrastructure to release 11.2.0.3, the Oracle Automatic Storage Management Configuration Assistant may attempt to start the disk group on a remote node before the disk group is created. As a result, the disk group fails to start.

If you perform a software-only installation of Oracle Grid Infrastructure release 11.2.0.3 on a system that is currently running 11.2.0.1 release, and then you start the software configuration wizard to upgrade Oracle Grid Infrastructure to 11.2.0.3 release, you may get the following error message:

[INS-40418] The installer has detected that Oracle Clusterware is not running on local node. Oracle recommends that you upgrade Oracle Clusterware in rolling manner.

Workaround:

Run cluvfy comp clu from the 11.2.0.3 home, before starting the configuration wizard.

This issue is tracked with Oracle bug 13321999.

6.2.28 ocfs.sys Driver Upgrade Issue on Windows x64

When you upgrade Oracle Grid Infrastructure to release 11.2.0.3, the ocfs.sys driver is not upgraded.

When installing .NET related products such as Oracle Data Provider for .NET, Oracle Providers for ASP.NET, and so on, to an ORACLE_HOME and ORACLE_BASE that are located on a mapped drive on either 32-bit or 64-bit operating system, you may encounter a System.IO.FileLoadException exception from OraProvCfg.exe.

Workaround:

Install .NET Framework 2.0 SP2 or later on the system where you run the installation.

6.3.5 Instance Terminates Following ORA-29770 Error on Windows x64

The default registry key setting for remote memory copy timeout (30 seconds) is too long. This results in an ORA-29770 error when the shared server feature is enabled and LMS processes are stuck in the memory copy code path with TCP library on Windows platform.

Workaround:

Enable the remote copy routine to time out in 5 seconds instead of the default 30 seconds and return the control back to LMS. Update the following registry entry:

6.3.6 Shortcuts for Oracle Software Not Removed from Start Menu When Removing a Node

Start menu shortcut entries are not removed when a node is deleted from a shared Oracle RAC home.

Workaround:

Manually remove the Start menu shortcut entries:

From the Start menu, select All Programs, then right-click Oracle-HOME_NAME.

Select the delete option and confirm the deletion.

This issue is tracked with Oracle bug 10074059.

6.3.7 PATH Variable Not Updated on Recently Deleted Node that Uses a Shared Oracle Home

If your Oracle RAC Database uses a shared Oracle home and you delete a node, then the PATH environment variable on the node being deleted is not updated to remove the location of the Oracle home.

Workaround:

Update the PATH variable manually on deleted node using the following steps:

From the Start menu, select Control Panel, then open System.

Select Advanced and click Environment Variables.

Select PATH variable from System Variables and double-click to get variable value.

Remove Oracle RAC home reference from variable value and click OK.

Click OK on Environment Variables dialog and then click Apply on System Properties dialog.

This issue is tracked with Oracle bug 10074038.

6.3.8 Issues While Deleting Oracle RAC on a Remote Node

When using Oracle Database Configuration Assistant to delete an Oracle RAC instance on a remote node, you may encounter the following error:

EMCA failed due to the following error - Error updating EM configuration for node node_name

Workaround:

Use Process Monitor, PMON, to identify and stop ohFilesPerm.pl perl process. Then remove the Oracle Enterprise Manager Database Control state directory:

ORACLE_HOME/nodename_db_unique_name

This issue is tracked with Oracle bug 10073887.

6.3.9 Using Oracle ACFS for the Database Home and LOB Files

If you place the Oracle Database home on Oracle ACFS, and the database uses LOB files, which are also stored on Oracle ACFS, then the Oracle ACFS home must be of the format, DRIVE_LETTER:\directory. For example:

g:\dir
g:\dir1\dir2

Otherwise, LOB related errors are shown when accessing the LOB (as in the sample schema for a basic installation). For example:

ERROR at line 1:
ORA-22288: file or LOB operation FILEOPEN failed
ORA-06512: at "SYS.DBMS_LOB", line 744
ORA-06512: at "XDB.DBMS_XDB", line 301
ORA-06512: at line 4

Click Ignore these errors to proceed, or click Abort to stop the database creation.

This issue is tracked with Oracle bug 9527303.

6.3.10 Download Microsoft Handle Utility When Using Oracle ACFS

The Microsoft handle utility is required for proper operation of Oracle ACFS High Availability resources managed by Oracle Clusterware. Oracle Clusterware resources may not shut down properly if this command is not included.

After downloading, place the Handle utility in the BIN directory of your Grid home.

Note:

Ensure that the Grid home is included in the PATH environment variable for your current session.

This issue is tracked with Oracle bug 9349433.

6.3.11 Oracle Grid Infrastructure Listeners Issue

After installing Oracle Grid Infrastructure, the default listener does not listen on public addresses. As a result, even though the listener is available, the listener does not service the database or Oracle ASM instances.

Workaround 1:

If you are not using GNS with DHCP, then perform the following steps:

Add the local IP address and host name information to %Systemroot%\System32\Drivers\Etc\Hosts.

For example, IP addresshost name such as 192.0.2.254dbhost.

Restart the Oracle Grid Infrastructure listener.

This issue is tracked with Oracle bug 9382523.

Workaround 2:

If you have configured GNS and use DHCP to assign the addresses for the cluster nodes, then configure DHCP so that the IP address assigned to the host name for each cluster node (the public IP address) has a smaller numeric value than the IP addresses assigned for the Virtual IP (VIP) address, GNS VIP address, or SCAN VIP address for a node.

For example, you could use IP addresses in the range of xxx.xxx.xxx.0 – xxx.xxx.xxx.099 for only host IP addresses, and all other IP address assignments must use a value of xxx.xxx.xxx.100 or higher.

This issue is tracked with Oracle bug 9441288.

6.3.12 ODP.NET Help Not Installed on 64-Bit Windows

If you install 32-bit Oracle software on a 64-bit Windows computer, then help for ODP.NET is not installed.

Workaround:

Use the .NET Help Setup Wizard to manually install the dynamic help. To start the wizard on an English locale, run the DataProviderHelp_en.msi file from the ORACLE_BASE\ORACLE_HOME\ODP.NET\help directory. For the Japanese locale, run the DataProviderHelp_ja.msi file from the same directory.

This issue is tracked with Oracle bug 9524039.

6.3.13 Help File Shortcut Not Working in Windows Server 2008

Starting Oracle Objects for OLE C++ Class Library Help from the Start menu shortcut does not open the help page in Windows Server 2008.

Workaround:

Complete the following steps to resolve this issue:

Right-click the shortcut.

Select Open With and click Internet Explorer.

Select the option to open the help page.

This issue is tracked with Oracle bug 8001859.

6.3.14 Shared Oracle Home Shortcuts Do Not Work on Windows Server 2008

6.3.15 Installing Online Patches on Windows Systems

Opatch tool version 11.2.0.1.9 is available on My Oracle Support as Patch 6880880 for Oracle Database 11g Release 2. Download and install Opatch Tool version 11.2.0.1.9 before applying online patches on Windows systems.

To list the database instances patched by an online patch, run the opatch lsinventory -details command. Ensure that you run the opatch rollback command instead of opatch disableOnlinepatch command to disable and remove an online patch from the final database instance in a node. To remove the online patch that is in a disabled state, run the disableOnlinepatch command. To remove the online patch in a disabled state, use -no_sysmod flag with opatch rollback command, only when opatch lsinv -details does not list any instances for that patch. For example, use opatch rollback -id 1234 -no_sysmod, only when opatch lsinv -details show no instances patched for bug 1234.

If you install Oracle Database release 11.1 or earlier and during installation choose to create a database with storage configured on Oracle ASM release 11.2.0.4, then the installation fails while the configuration tools are running, specifically Database Configuration Assistant.

Workaround:

Install the Oracle Database release 11.1 or earlier software and choose the software only installation option. After the installation completes, create the single-instance database by launching Database Configuration Assistant from the newly installed Oracle home. For example, run the following command from a command prompt:

If you install a 32-bit Oracle Database and a 64-bit Oracle Database in the same ORACLE_BASE, then it may lead to unexpected results when using the deinstallation tool to remove one of the databases. The deinstallation tool removes all the Oracle home under Oracle base if these Oracle homes do not use the same central inventory.

Workaround:

Avoid using multiple central inventories. Do not use the same ORACLE_BASE for 32-bit and 64-bit database installations.

When you upgrade Oracle Grid Infrastructure to release 11.2.0.4 and start installing Oracle RAC database release 11.2.0.1, then the Oracle Database Configuration Assistant shows the following error message towards the end of the database creation:

java.exe - Entry Point Not Found
The procedure entry point clsunsinit could not be located in the dynamic link library orahasgen11.dll.
---------------------------
OK
---------------------------

Workaround:

Click OK and proceed with the database creation process. Log into the Oracle Database Enterprise Manager Control and navigate to the Cluster home page. Click Monitoring Configuration and update the eONS port for cluster target property.

If you perform a software-only installation of Oracle Grid Infrastructure release 11.2.0.4 on a system that is currently running 11.2.0.1 release, and then you start the software configuration wizard to upgrade Oracle Grid Infrastructure to 11.2.0.4 release, you may get the following error message:

[INS-40418] The installer has detected that Oracle Clusterware is not running on local node. Oracle recommends that you upgrade Oracle Clusterware in rolling manner.

Workaround:

Run cluvfy comp clu from the 11.2.0.4 home, before starting the configuration wizard.

This issue is tracked with Oracle bug 13321999.

7.2.9 Deinstallation Tool Fails to Remove Registry Entries

When deinstalling Oracle Grid Infrastructure, some registry entries are not removed.

Oracle Database 11.2 supports Oracle SID having an underscore but it is not compatible with the earlier client releases with a bequeath connection. The issue affects any Oracle Database Client 11.1.0.7 or earlier client, when connecting to the database over a bequeath connection. This includes all OCI clients and Oracle Enterprise Manager agents that monitor the database.

Workaround:

Use only alphanumeric characters including hyphens for Oracle SID or connect to the database using TCP connection.

If "Oracle America, Inc." is not in list of the trusted publishers of the node, then the following message appears:

Would you like to install this device software?
Name: Oracle Network Protocol
Publisher: Oracle America, Inc.

Select Install to install the driver.

Run the following command on all the nodes in the cluster after installing the oraarp driver:

sc config oraarpdrv start= auto

Stop the Oracle GNS service. To determine if GNS is configured, run the following command:

Grid_home\bin\srvctl config gns

To stop the GNS service, run the following command:

Grid_home\bin\srvctl stop gns

Stop the SCAN resource using the following command:

Grid_home\bin\srvctl stop scan -f

Stop all node applications running on the nodes in the cluster. To determine the node names for your cluster, run the following command:

Grid_home\bin\olsnodes -l

To stop the node application resources, use the following command where node_list is a comma-delimited list of node names:

Grid_home\bin\srvctl stop nodeapps -n node_list -f

Restart the node applications on all nodes in the cluster using the following command where node_list is a comma-delimited list of node names:

Grid_home\bin\srvctl start nodeapps -n node_list

Restart the SCAN resource using the following command:

Grid_home\bin\srvctl start scan

If necessary, here are the steps to uninstall Oracle ARP protocol driver:

Stop the Oracle ARP protocol driver:

net.exe stop oraarpdrv

Open the Windows Networks Connections management interface. Right-click Properties on a public network interface, or from the Start menu, select Control Panel, then Network and Internet, and then Network Connections.

Select Oracle ARP Protocol Driver and click Uninstall.

This issue is tracked with Oracle bug 13087098.

7.2.12 Oracle MTS Recovery Service Issue When Installing Oracle RAC

In an Oracle RAC database installation, Oracle MTS Recovery Service on the remote nodes does not have the correct host name registered for string variable HOST under registry key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OracleMTSRecoveryService\Protid_0. This variable contains the name of the host from where the installation was performed instead of the name of the local host. This registry variable is used by COM+ applications to pass information to Oracle databases so that they can connect back to the Windows computer if the database must resolve in-doubt COM+ transactions. The incorrect host name that is registered can cause transaction recovery issues.

Workaround:

To fix this, use Registry Editor (regedit) on the remote Windows system and look under the registry key:

[INS-40406] There is no previous version of grid software detected on the system.

Workaround:

If you are performing the upgrade on a remote node, a node other than the one on which Oracle Clusterware 11g Release 1 (11.1.0.6) was installed, then the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\inst_loc may not have been set on that node.

Ensure that you manually set the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\inst_loc to the location of the Oracle Inventory directory of the node on which you are performing the upgrade installation.

This issue is tracked with Oracle bug 9210861.

7.2.14 Oracle ASM Disk Group Does Not Mount on Remote Node After a Database Upgrade on Windows x64

After upgrading Oracle Grid Infrastructure to release 11.2.0.4, the Oracle Automatic Storage Management Configuration Assistant may attempt to start the disk group on a remote node before the disk group is created. As a result, the disk group fails to start.

When doing an upgrade, deinstallation, or direct shutdown of Oracle Clusterware or Oracle ASM, to ensure that Oracle Clusterware (or Oracle ASM) comes down cleanly, you must dismount all Oracle ACFS file systems manually before Oracle Cluserware shutdown. Use the handle and wmic commands to identify processes which are active on the Oracle ACFS file systems. To ensure that these processes are no longer active, dismount all Oracle ACFS file systems and issue Oracle Clusterware shutdown. Otherwise, errors may be issued during Oracle Clusterware shutdown relating to activity on Oracle ACFS file systems which will stop the successful shutdown of Oracle Clusterware.

When attempting to upgrade Cluster Ready Services or Oracle ASM to 11.2 release using the Automatic Storage Management Configuration Assistant, the upgrade succeeds, but the configuration changes made to the Agents on a remote host fail to reload. As a result, Oracle Enterprise Manager Grid Control and Database Control cannot monitor the Oracle ASM and Cluster Ready Services targets.

Workaround:

Manually reload the remote agents after the upgrade using the following command:

emctl reload agent

This issue is tracked with Oracle bug 9398380.

7.2.21 Deinstallation Tool Does Not Remove Oracle Home

When using the Deinstallation Tool to remove an Oracle home that has Oracle Enterprise Manager Database Control configured and that was installed on Oracle ACFS, the ORACLE_BASE\ORACLE_HOME\host_sid\sysman directory and its sub directories cannot be deleted, preventing the Oracle home from being removed.

Workaround:

Before performing these operations, run the following command as the Administrator user:

Removing Oracle home fails with file in use errors as the services and processes running from the Oracle home are not removed completely by Microsoft's Service Control Manager before the Oracle home removal.

Workaround:

Remove the Oracle home manually after the deinstall tool exits.

This issue is tracked with Oracle bug 10035858.

7.2.24 Auto-Update Fails on a Shared Oracle RAC Home

With shared Oracle RAC homes, if you use the installer auto-update feature to download and apply the latest patches from My Oracle Support, the installer fails to apply the patches with a Java runtime Exception error.

Workaround:

Do not use the auto-update option during installation and apply the required patches using Opatch after the installation. Alternatively, if you use the auto-update option, after you have completed installation, manually download the patches which failed to be applied, from My Oracle Support, and then run the following command to apply the patches:

After upgrading Oracle Grid Infrastructure or Oracle RAC from release 10.2.0.4 to 11.2.0.4, the listener, SCAN listener, and SCAN VIP resources fail to start when you restart the node.

Workaround:

Manually install the Oracle ARP protocol driver and run the following command to start the oraarp driver automatically when restarting the node:

sc config oraarpdrv start= auto

This issue is tracked with Oracle bug 17084320.

7.2.26 No Available Nodes Listed During Oracle Grid Infrastructure Upgrades

During Oracle Grid Infrastructure upgrades, or during installations on servers where previous releases of Oracle Grid Infrastructure were installed, the Cluster Node Information window may indicate that there are no available cluster node candidates. The available nodes are not listed on systems with the registry key \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OSD9i\IPC. The registry key was a part of the configuration requirements for the previous releases for Oracle cluster software, but it is not used with Oracle Grid Infrastructure.

Workaround:

On each cluster node, remove the following registry entries to use the default values:

After modifying the registry, restart all cluster nodes, and continue with the installation.

This issue is tracked with Oracle bug 18504336.

7.2.27 INS-13001 Error on Windows Server 2012 R2

Installing Oracle Database using the command, setup.exe -jreLoc path-to-jdk7\jre results in the following error:

INS-13001: Environment does not meet minimum requirements.

Workaround:

Skip the preinstallation requirements check using the following command:

setup.exe -jreLoc path-to-jdk7\jre -ignorePrereq

This issue is tracked with Oracle bug 18435100.

7.2.28 Oracle ACFS Support on Windows Server 2012 R2

When creating an Oracle home on Oracle ACFS on Windows Server 2012 R2, the clusterware resources associated with the home may be in an ITERMEDIATE (versus ONLINE) state on selected nodes in the cluster due to an acfsutil error, as shown in the following example:

7.3.1 Issues When Using addnode.bat

When using the addnode script and specifying a response file, you may see the following error:

ERROR: Value for CLUSTER_NEW_NODES not specified.

Workaround:

Do not use a response file.

This issue is tracked with Oracle bug 17167249.

If you use fully-qualified domain names for the node as the value you specified in addnode.bat for the CLUSTER_NEW_NODES parameter, then the Database Configuration Assistant cannot retrieve the correct information for Oracle RAC instance management. This occurs if you add a node to Oracle Grid Infrastructure for a Cluster, and if you add Oracle RAC instances to cluster nodes. For example:

7.3.4 Using Oracle ACFS for the Database Home and LOB Files

If you place the Oracle Database home on Oracle ACFS, and the database uses LOB files, which are also stored on Oracle ACFS, then the Oracle ACFS home must be of the format, DRIVE_LETTER:\directory. For example:

g:\dir
g:\dir1\dir2

Otherwise, LOB related errors are shown when accessing the LOB (as in the sample schema for a basic installation). For example:

ERROR at line 1:
ORA-22288: file or LOB operation FILEOPEN failed
ORA-06512: at "SYS.DBMS_LOB", line 744
ORA-06512: at "XDB.DBMS_XDB", line 301
ORA-06512: at line 4

When installing .NET related products such as Oracle Data Provider for .NET, Oracle Providers for ASP.NET, and so on, to an ORACLE_HOME and ORACLE_BASE that are located on a mapped drive on either 32-bit or 64-bit operating system, you may encounter a System.IO.FileLoadException exception from OraProvCfg.exe.

Workaround:

Install .NET Framework 2.0 SP2 or later on the system where you run the installation.

This issue is tracked with Oracle bug 10225338.

7.3.9 Issues While Deleting Oracle RAC on a Remote Node

When using Oracle Database Configuration Assistant to delete an Oracle RAC instance on a remote node, you may encounter the following error:

EMCA failed due to the following error - Error updating EM configuration for node node_name

Workaround:

Use Process Monitor, PMON, to identify and stop ohFilesPerm.pl perl process. Then remove the Oracle Enterprise Manager Database Control state directory:

ORACLE_HOME/nodename_db_unique_name

This issue is tracked with Oracle bug 10073887.

7.3.10 Issue While Running clone.pl

On a Windows 32-bit system, where the msvcr71.dll file is not present in C:\Windows\System32, running the clone.pl script shows the following message:

The application had failed to start because MSVCR71.dll was not found. Reinstalling the application may fix the problem

Workaround:

Set the path of the msvcr71.dll file to include ORACLE_HOME\oui\lib\win32 from a command prompt. Run clone.pl from the same command prompt.

This issue is tracked with Oracle bug 17233850.

7.3.11 ODP.NET Help Not Installed on 64-Bit Windows

If you install 32-bit Oracle software on a 64-bit Windows computer, then help for ODP.NET is not installed.

Workaround:

Use the .NET Help Setup Wizard to manually install the dynamic help. To start the wizard on an English locale, run the DataProviderHelp_en.msi file from the ORACLE_BASE\ORACLE_HOME\ODP.NET\help directory. For the Japanese locale, run the DataProviderHelp_ja.msi file from the same directory.

This issue is tracked with Oracle bug 9524039.

7.3.12 Download Microsoft Handle Utility When Using Oracle ACFS

The Microsoft handle utility is required for proper operation of Oracle ACFS High Availability resources managed by Oracle Clusterware. Oracle Clusterware resources may not shut down properly if this command is not included.

Ensure that the current working directory is not the bin directory of 11.2.0.4 Oracle Grid Infrastructure home, GI_HOME\bin, when you execute the srvctl add service command for the 11.1.0.7. Oracle RAC.

This issue is tracked with Oracle bug 17573010.

7.3.18 Database Fails to Start After Private NIC Failure of One Node in a Two Node Cluster

In a two node cluster, when there is a failure of the private NIC on the node that has smallest node number (node A) after the other node B was evicted, then when the private network is reestablished on node A, the other node B joins the cluster but the database instance on the other node is unable to start.

Workaround:

Perform the following steps:

Stop the crs stack on both nodes, then start the crs stack on both nodes.

Stop the database instance on the node that has the private network failure (node A), then start the database on both nodes. The database instance fails to start on node A this time. After the instance starts on the other node B, then you will be able to start the instance on node A.

This issue is tracked with Oracle bug 19642240.

7.3.19 Cloning Issue on Windows Server 2012 R2

When you clone an Oracle home that has patch 20043415, it may result in Oracle ASM configuration issues with Oracle Grid Infrastructure or with Standard or Enterprise editions of Oracle Database.

Workaround:

Perform the following steps:

Unzip the Oracle Grid home or Oracle RAC home on the destination node.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.