Oracle® Database

4.2.1 Oracle Automatic Storage Management Configuration Assistant Fails While Installing Oracle Grid Infrastructure on a Standalone Server

If ASM_DISKSTRING attribute is set to the default empty "" string and if there is more than one path to the disk, then Oracle Automatic Storage Management fails to detect the disks while installing Oracle Grid Infrastructure on a standalone server. The following error message appears:

ORA-15020: discovered duplicate ASM disk "HPISIHA_0000" 

Workaround:

Use the command srvctl modify asm -d diskstring to set the ASM_DISKSTRING attribute to a valid directory path. You may also change the permission on the directory path of the devices in such a way that all the disks are accessed from the same directory path.

This issue is tracked with Oracle bug 9117353.

4.3.1 Help Files Translation Issue for Spanish and French

Oracle Universal Installer does not copy the translated help files to Oracle home directory when you select the Spanish or French language.

Workaround:

On the Select Product Languages page, select both the Latin American Spanish and Spanish to get the help files translated in Spanish; and select both the Canadian French and French for the translated help files in French.

This issue is tracked with Oracle bug 9147106.

4.3.2 Incorrect Reverse Ping Command from Oracle Management Service

Oracle Management Service provides incorrect reverse ping command with Oracle Enterprise Manager Database Control. The emoms.properties file shows:

emdrep.ping.pingCommand=/usr/sbin/ping <hostname>

Workaround:

Change the property in the emoms.properties file to:

emdrep.ping.pingCommand=/usr/sbin/ping <hostname> -n 3 -m 30

This issue is tracked with Oracle bug 9211800.

4.3.3 Help Pages Fail to Load for Oracle Database Client (32-Bit)

Oracle Universal Installer does not find the clientinstaller_help.map file and fails to load the help pages for locales other than English.

Workaround:

Set LANG=C before running Oracle Universal Installer. This changes the installer locale to English and the help content is available.

This issue is tracked with Oracle bug 9474214.

4.3.4 SQL Developer Fails to Start

After you install the Oracle Database, the SQL Developer might fail to start and the following error message appears:

/bin/bash: bad interpreter: No such file or directory

Workaround:

Open the sqldeveloper.sh file in a text editor and change #!/bin/bash to the actual location of Bash. For example:

#!/usr/local/bin/bash

This issue is tracked with Oracle bug 9335876.

5.2.1 Relinking Fails on 32-Bit Client Installations

Relinking fails on 32-bit client installations because the relink script tries to load 64-bit libraries.

Workaround:

After installation, manually remove the -d64 flag from JRE_MEMORY_OPTIONS in the $ORACLE_HOME/oui/oraparam.ini file.

This issue is tracked with Oracle bug 10027801.

5.2.2 Logical Volume Manager Issue

Oracle Automatic Storage Management Configuration Assistant attempts to filter out disks that are in use by the operating system's logical volume manager (LVM). The mechanism used to check the character device files from their default location, /dev/rdisk/*, may fail if the Oracle grid user does not have read permissions on the corresponding block device. In rare cases, that failure can result in Automatic Storage Management Configuration Assistant creating an Oracle ASM disk group on top of an existing LVM volume group, corrupting the LVM content.

/gridbase/asmdisks

Workaround:

On servers where the system administrator has explicitly granted read/write access to any /dev/rdisk/* files for use by Oracle ASM, enable read permissions on the corresponding block device. The ownership of the block device need not be changed. For example, if disk11 is available to Oracle ASM, a listing of the device files for that disk usually shows the following:

$ ls -l /dev/*disk/disk11
brw-r-----   1 bin       sys         5 0x000001 Apr 21 2009 /dev/disk/disk11
crw-rw----   1 grid      oinstall  132 0x00001c Apr 21 2009 /dev/rdisk/disk11

As the root user, enable read access to the block device with the following command:

chmod a+r /dev/disk/disk11

This results in:

$ ls –l /dev/*disk/disk11
 
brw-r--r--   1 bin    sys            5 0x000001 Apr 21  2009 /dev/disk/disk11
 
crw-rw----   1 grid   oinstall     132 0x000001 Apr 21  2009 /dev/rdisk/disk11

This issue is tracked with Oracle bug 9956769.

5.2.3 Owner and Group Permissions Issue with Database Upgrade

When you upgrade from Oracle Database release 10.x or 11.1 to 11.2 release using the Oracle ASM discovery path, /dev/rdsk/* as default, ensure that the corresponding /dev/rdisk* disks use the same owners and group permissions as the legacy device special file, /dev/rdsk/* disks. Otherwise, the database may fail to start.

Run the following command to map the legacy device special file disks and persistent device special file disks:

ioscan -m dsf

Based on the mapping result, change the permissions in the corresponding persistent device special file disks.

This issue is tracked with Oracle bug 10148343.

5.2.4 Network Connection Issue Between Nodes in a Cluster

When installing Oracle Grid Infrastructure for a Cluster, the root.sh script fails on the second node with the following errors in the ocssd.log:

CSSD][105]clssnmLocalJoinEvent: takeover aborted due to cluster member node found on disk 
CRS-5818:Aborted command 'start for resource: ora.cssd 1 1' for resource 'ora.cssd'

Solution:

Servers with the latest 10 Gigabit Ethernet adapter require revision B.11.31.1009.01 or later of the 10GigEthr-02 software bundle.

Run swlist 10GigEthr-02 command to identify the current version on your HP server. If it is older than the above mentioned version, then enter 10GigEthr-02 in the Search field and download the latest software from the HP site:

https://h20392.www2.hp.com/portal/swdepot/index.do

This issue is tracked with Oracle bug 10175794.

5.2.5 Performance Statistics Issue with Oracle Enterprise Manager Database Control

The summary chart on the Oracle Enterprise Manager Cluster Performance page does not show any data.

Workaround:

Perform the following steps:

1. Stop Oracle Enterprise Manager Database Control.

2. Add the following to the properties file, $ORACLE_HOME/host_dbuniquename/sysman/config/emoms.properties:

   oracle.sysman.db.rac.useRemoteCollection=false
   

3. Restart the Oracle Enterprise Manager Database Control.

This issue is tracked with Oracle bug 10129539.

5.3.1 SQL Developer Fails to Start

After you install the Oracle Database, the SQL Developer might fail to start and the following error message appears:

/bin/bash: bad interpreter: No such file or directory

Workaround:

Open the sqldeveloper.sh file in a text editor and change #!/bin/bash to the actual location of Bash. For example:

#!/usr/local/bin/bash

This issue is tracked with Oracle bug 9335876.

6.2.1 SEMMNU Kernel Parameter Issue During Oracle Grid Infrastructure Installation

During an Oracle Grid Infrastructure installation, if you are prompted to run the runfixup.sh script to adjust the value of the SEMMNU kernel parameter, you might see the following error message:

NOTE:    The requested changes could not be applied to the currently
         running system, for the following reasons:
         - The tunable 'semmnu' cannot be changed without a reboot.
        * The requested changes have been saved, and will take effect at
         next boot.

Workaround:

Set the value of SEMMNU to an appropriate value before installation, or ignore the error message and continue the installation. After the installation completes, restart the server to implement the kernel parameter change.

This issue is tracked with Oracle bug 12811986.

6.2.2 Oracle Grid Infrastructure Upgrade Fails with Oracle ASM Upgrade

When attempting to upgrade to Oracle Grid Infrastructure 11.2.0.2 or 11.2.0.3 from Oracle ASM from version 11.1.0.7, if you choose to upgrade Oracle ASM during the Oracle Grid Infrastructure upgrade and the Oracle ASM 11.1.0.7 installation is owned by a different user than the Oracle Clusterware installation, the upgrade fails.

Workaround:

Change the working path to the new Grid Infrastructure home created by the upgrade attempt.

Run the following command to manually upgrade the Oracle ASM installation:

Grid_home_for_11_2/bin/asmca 

This issue is tracked with Oracle bug 12741662.

6.2.3 Permission Issues with Oracle Cluster Registry

When the Cluster Verification Utility performs the OCR Integrity check, the sharedness check might fail due to the user not having the permission to access the device used for the Oracle Cluster Registry. The error might look similar to the following:

PRVF-4172 : Check of OCR device "device_used_for_OCR" for sharedness
failed Could not find the storage

Workaround:

Check the permissions of the device identified in the error message, device_used_for_OCR. While logged in as the root user, grant the user permission to access the device.

This issue is tracked with Oracle bug 10064738.

6.2.4 Fixup Script Does Not Set maxssiz_64bit Kernel Parameter

The fixup.sh script does not set the kernel parameter, maxssiz_64bit, to a minimum value required for the successful database installation.

Workaround:

Run the following command as the root user to tune the parameter:

# /usr/sbin/kctune maxssiz_64bit=1073741824

This issue is tracked with Oracle bug 12746701.

6.2.5 Fixup Script Does Not Set shmmni and shmseg Kernel Parameters

The fixup.sh script does not set the kernel parameters, shmmni and shmseg, to a minimum value required for the successful database installation.

Workaround:

Run the following commands as the root user to tune the parameters:

# /usr/sbin/kctune shmmni=4096
# /usr/sbin/kctune shmseg=512

This issue is tracked with Oracle bug 12739313.

6.2.6 OC4J Error After Upgrading Oracle Grid Infrastructure to 11.2.0.3 Release

OC4J may remain enabled causing an error after you upgrade Oracle Grid Infrastructure to 11.2.0.3 release. The rootupgrade.sh log file shows the following error message:

PRKO-2116: OC4J is already enabled. 

Workaround:

Use the following procedure to disable and stop the OC4J resource:

1. While the Oracle Clusterware stack is running, enter the following command:

   $ srvctl config oc4j
   

   If the output of this command shows that OC4J is enabled, then enter the following command to disable OC4J:

   $ srvctl disable oc4j
   

2. Run the following command to check if OC4J is running:

   $ srvctl status oc4j
   

3. If the output of the command in the earlier step shows that OC4J is running, then stop OC4J as follows:

   $ srvctl stop oc4j
   

4. Confirm that the OC4J resource is no longer running by entering the following command:

   $ srvctl status oc4j
   

This issue is tracked with Oracle bug 12845598.

6.2.7 Automatic SSH Configuration Issue for HP-UX

Automatic SSH configuration is not available at the time of this release due to an issue with the installer.

Workaround:

Perform manual SSH configuration as described in section "D.1 Configuring SSH Manually on All Cluster Nodes" in Oracle Grid Infrastructure Installation Guide for HP-UX.

This issue is tracked with Oracle bug 9979216.

6.2.8 Network Connection Issue Between Nodes in a Cluster

When installing Oracle Grid Infrastructure for a Cluster, the root.sh script fails on the second node with the following errors in the ocssd.log:

CSSD][105]clssnmLocalJoinEvent: takeover aborted due to cluster member node found on disk 
CRS-5818:Aborted command 'start for resource: ora.cssd 1 1' for resource 'ora.cssd'

Solution:

Servers with the latest 10 Gigabit Ethernet adapter require revision B.11.31.1009.01 or later of the 10GigEthr-02 software bundle.

Run swlist 10GigEthr-02 command to identify the current version on your HP server. If it is older than the above mentioned version, then enter 10GigEthr-02 in the Search field and download the latest software from the HP site:

https://h20392.www2.hp.com/portal/swdepot/index.do

This issue is tracked with Oracle bug 10175794.