Oracle® Database

6.1 Adding a Node to a Shared Oracle Clusterware Configuration

Before running root.sh in the first node of a shared Oracle Clusterware home, add the following line in the $ORA_CRS_HOME/opmn/conf/ons.config file:

usesharedinstall=true

This issue is tracked with Oracle bug 4454562.

6.2 Installing Enterprise Security Manager

To install Enterprise Security Manager (ESM), install Oracle Client and choose the Administrator installation type.

6.3 extjob Executable Required Directory Permissions

To enable the extjob executable to locate required libraries, the $ORACLE_HOME/lib directory and all of its parent directories must have execute permissions for group and other.

6.4 Modifying a Virtual IP Address Node Application

When modifying the name, IP address, or netmask of an existing virtual IP address (VIP) resource, use the following command:

srvctl modify nodeapps

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.

7.1 European Language Locale

If your system uses a European language, then you must not use the UTF-8 locale. For example, if your system uses German, set the LANG and LC_ALL environment variables to de_DE instead of de_DE.UTF-8.

This issue is tracked with Oracle bug 3957096.

7.2 Oracle Clusterware Files Issues

The following note applies if you are using Red Hat Enterprise Linux 4.0 and using raw devices to store the Oracle Cluster Registry (OCR) and the voting disk for Oracle Clusterware, or using raw devices for Automatic Storage Management (ASM) database files. For each raw device used for the purposes listed, you must add two entries in the /etc/rc.d/rc.local file after running the root.sh script following the installation of Oracle Clusterware.

For each OCR file, the entries should look as follows, where oinstall is the Oracle install group and /dev/raw/rawn is an individual device file:

chown root:oinstall /dev/raw/rawn
chmod 640 /dev/raw/rawnmar

For each voting disk file, the entries should look as follows, where oracle is the Oracle user, oinstall is the Oracle install group, and /dev/raw/rawn is an individual device file:

chown oracle:oinstall /dev/raw/rawn
chmod 644 /dev/raw/rawnmar

For each ASM file, the entries should look as follows, where oracle is the Oracle user, oinstall is the Oracle install group, and /dev/raw/rawn is an individual device file:

chown oracle:oinstall /dev/raw/rawn
chmod 660 /dev/raw/rawnmar

7.3 Cluster Verification Utility Issues

This section lists the issues with Cluster Verification Utility on Red Hat Enterprise Linux 4.0 and SUSE Linux Enterprise Server 9:

• The preinstallation stage verification checks for Oracle Clusterware and Oracle Real Applications Clusters and reports missing packages. Ignore the following missing package and continue with the installation:

  compat-libstdc++-33-3.2.3-47.3
  
  

7.4 VLM Window Size on Red Hat Enterprise Linux 4.0

To use hugepages or to accommodate the VLM window size on Red Hat Enterprise Linux 4.0, you must increase the default maximum size of the per-process locked memory. To increase the per-process max locked memory limit, add the following lines to the /etc/security/limits.conf file, where oracle is the user that administers the database:

oracle soft memlock 3145728 oracle hard memlock 3145728

7.5 Link Error While Running genorasdksh on Red Hat Enterprise Linux 4.0

Installing Oracle Database 10g release 2 (10.2.0.1) on Red Hat Enterprise Linux 4.0 Update 1 (2.6.9-11.ELsmp) produces a link error during creation of liborasdkbase.so.10.2. The following error message is thrown:

INFO: gcc:
INFO: /usr/lib/libstdc++.so.5: No such file or directory
INFO:
INFO: $OH/bin/genorasdksh: Failed to link liborasdkbase.so.10.2

This is because Oracle Database 10g release 2 (10.2) requires Red Hat Enterprise Linux 3.0 libraries (/usr/lib/libstdc++.so.5).

Workaround: Install the compatible libraries as follows:

rpm -ql compat-libstdc++-33-3.2.3-47.3

This issue is tracked with Oracle bug 4605635.

7.6 Removing Metrics for Wait Classes Removes Them Permanently

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.

7.7 Interim Fix for the IBM XL C/C++ Advanced Edition V7.0 for Linux Runtime Environment Component

You must apply the interim Fix for the IBM XL C/C++ Advanced Edition V7.0 for Linux Runtime Environment Component after installing IBM XL C/C++ Advanced Edition V7.0 for Linux Runtime Environment Component and XL Optimization Libraries component from the following link:

http://www.ibm.com/support/docview.wss?rs=2030&context=SSJT9L&context=SSENT9&context=SSEP5D&dc=D400&dc=D410&dc=D420&dc=D430&q1=Run-time+Environment+Component&uid=swg24007906&loc=en_US&cs=utf-8&lang=en

This URL contains information and installation instructions about the interim fix. All the above installations must to be done before installing Oracle database.

If the interim fix is not available (for example, if update ptf is available) then you need not apply the interim fix.

This issue is being tracked with Oracle bug 4712830.

7.8 Using the org.w3c.dom.ls Package With IBM JDK 1.4.2

When using IBM JDK 1.4.2 to build an application that uses the org.w3c.dom.ls package, the following errors might be thrown:

cannot resolve symbol
symbol  : method getConfig ()
location: interface org.w3c.dom.ls.LSParser

Or

cannot resolve symbol
symbol  : method getConfig ()
location: interface org.w3c.dom.ls.LSSerializer

To resolve these errors, the application should be built using the -J-Djava.endorsed.dirs=$ORACLE_HOME/endorsed command line option of the Java compiler.

For example:

javac -J-Djava.endorsed.dirs=$ORACLE_HOME/endorsed Test.java

Additionally, the application should be run using the -Djava.endorsed.dirs=$ORACLE_HOME/endorsed command line option of Java.

For example:

java -Djava.endorsed.dirs=$ORACLE_HOME/endorsed Test