Oracle® Database

3.1 Prerequisite Check for Kernel Version Fails

If you do not use the ignoreSysPrereqs flag when you install Oracle Database on Red Hat Enterprise Linux 5.0, SUSE Linux Enterprise Server 10, or SUSE Linux Enterprise Server 11, then the prerequisite check to validate the kernel version might fail.

The workaround is to ignore the error message and proceed with the installation if your system has one of the following kernel versions (or later):

Red Hat Enterprise Linux 5.0:
2.6.18

SUSE Linux Enterprise Server 10:
2.6.16

SUSE Linux Enterprise Server 11:
2.6.27

This issue is tracked with Oracle bug 11837867.

3.2 Install libaio Before Installing or Upgrading

Before upgrading to or installing Oracle Database 10g Release 2, install the libaio package.

3.3 Install oracleasm-support to use ASMLib

Install oracleasm-support package version 2.0.0.1 or higher to use ASMLib on Red Hat Enterprise Linux 4 Advanced Server or SUSE Linux Enterprise Server 9.

3.4 Configuring Kernel Parameters

After updating the values of kernel parameters in the /etc/sysctl.conf file, ensure that you either restart the computer or run the sysctl -p command to make the changes of the /etc/sysctl.conf file available in the active kernel memory.

On SUSE Linux Enterprise Server 9, ensure that you set the following kernel parameter:

disable_cap_mlock = 1

On SUSE Linux Enterprise Server 10, ensure that you set the hugetlb_shm_group kernel parameter to the gid of the group used as the dba group. For example, on a system using a group named dba with the dba:!:104:oracle entry in the /etc/group file, the hugetlb_shm_group kernel parameter should be set to the following value:

hugetlb_shm_group = 104

3.5 Oracle HTTP Server on Red Hat Enterprise Linux 4

If you intend to use Oracle HTTP server, which is included in Companion CD of Oracle Database 10g Release 2 (10.2) Media pack, refer to the My Oracle Support (formerly OracleMetaLink) note 317085.1 for more information on using Oracle HTTP server on Red Hat Enterprise Linux 4.

3.6 Oracle HTTP Server on Red Hat Enterprise Linux 5

If you intend to use Oracle HTTP Server, which is included in Companion CD of Oracle Database 10g Release 2 (10.2) Media pack, refer to the My Oracle Support (formerly OracleMetaLink) note 564174.1 for more information on using Oracle HTTP Server on Red Hat Enterprise Linux 5.

Legacy entry points required by this version of Apache (libdb.so.2) are moved to gdbm-1.8.0-26.2.1.i386. You must create a symlink using the following command:

$ ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2

4.1 Latest Upgrade Information

For late breaking updates and best practices about preupgrades, postupgrades, compatibility, and interoperability discussions refer to note 466181.1 on My Oracle Support (formerly OracleMetaLink) (https://support.oracle.com/) that links to "10g Upgrade Companion" page.

4.2 Default Makefile Issue on Red Hat Enterprise Linux 5

The default makefile version on Red Hat Enterprise Linux 5 is make 3.81. In this makefile version, the default database name (db_name) is not recognized by the client. Therefore, you should use makefile version 3.79 or use @db_name whenever username/password is used in the makefile.

4.3 Voting Disk Permissions

In Chapter 4, Section 4.2, "Preparing to Install Oracle Clusterware with OUI," of the Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide for Linux 10g Release 2 (10.2) for Linux, required voting disk permissions are listed as 644. This is incorrect. Voting disk permissions should be set to 640.

4.4 Oracle Universal Installer Operating System Prerequisite Checks

If you are installing Oracle Database 10g on Red Hat Enterprise Linux 5 , SUSE Linux Enterprise Server 10, or SUSE Linux Enterprise Server 11, then the current version of Oracle Universal Installer does not recognize these operating systems as supported operating systems and does not perform the installation.

Workaround #1 (recommended): Run the Oracle Universal Installer using the ignoreSysPrereqs flag which causes the installer to skip the operating system check and continue with the installation:

./runinstaller -ignoreSysPrereqs

As a side effect, the installer also skips other checks during the installation.

Workaround #2:

This workaround causes Oracle Universal Installer to consider the system to be an earlier version of the operating system and the operating system check passes. The changes to the release file should be reverted after the installation of all Oracle software is complete. The changes to the release file could impact the ability of other tools to be properly installed on the operating system.

On Red Hat Enterprise Linux 5, the installation passes the operating system prerequisite checks if you change each Red Hat Enterprise Linux 5 to Red Hat Enterprise Linux 4 in the /etc/redhat-release file. Ensure that you replace the original values in the /etc/redhat-release file after the Oracle installation is complete.

On SUSE Linux Enterprise Server 10, the installation passes the operating system prerequisite checks if you change each SUSE Linux Enterprise Server 10 to SUSE Linux Enterprise Server 9 in the /etc/SuSE-release file. Ensure that you replace the original values in the /etc/SuSE-release file after the Oracle installation is complete.

On SUSE Linux Enterprise Server 11, the installation passes the operating system prerequisite checks if you change each SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 9 in the /etc/SuSE-release file. Ensure that you replace the original values in the /etc/SuSE-release file after the Oracle installation is complete.

4.5 Installing Oracle Clusterware

Near the end of the installation of Oracle Clusterware, Oracle Universal Installer prompts for the $CRS_HOME/root.sh script to be run on all of the nodes in the cluster. When the root.sh script is run on the last node in the cluster, the script calls the VIPCA utility, which fails on Red Hat Enterprise Linux 5 and SUSE Linux Enterprise Linux 10. Refer to the "SRVCTL and VIPCA Utilities Set the LD_ASSUME_KERNEL Parameter" section for more details.

Workaround: Before running the root.sh script on the last node in the cluster, alter the $CRS_HOME/bin/vipca script commenting out lines 119 through 123:

arch='uname -m'
#       if [ "$arch" = "i686" -o "$arch" = "ia64" -o "$arch" = "x86_64" ]
#       then
#            LD_ASSUME_KERNEL=2.4.19
#            export LD_ASSUME_KERNEL
#       fi

With the lines commented out, root.sh should be able to call VIPCA successfully. Ensure that you do not comment out line 118, which sets the arch variable as that is needed by the root.sh script.

4.6 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.

4.7 Installing Enterprise Security Manager

To install Oracle Security Manager, install Oracle Database Client and then select the Administrator installation type.

4.8 extjob Executable Requires 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.

4.9 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.

4.10 Raw Devices on Red Hat Enterprise Linux

When you restart an Red Hat Enterprise Linux 4, or Red Hat Enterprise Linux 5 system, raw devices revert to their original owners and permissions by default. If you are using raw devices with this operating system for the Oracle files, for example, for ASM storage or Oracle Clusterware files, you need to override this default behavior. To do this, add an entry to the /etc/rc.d/rc.local file for each raw device containing the chmod and chown commands required to reset them to the required values.

As an example, here are sample entries in a /etc/rc.d/rc.local file that control the restart behavior of raw devices for two ASM disk files (/dev/raw/raw6 and /dev/raw/raw7), two Oracle Cluster Registry files (/dev/raw/raw1 and /dev/raw/raw2), and three Oracle Clusterware voting disks (/dev/raw/raw3, /dev/raw/raw4, and /dev/raw/raw5):

# ASM
chown oracle:dba /dev/raw/raw6
chown oracle:dba /dev/raw/raw7
chmod 660 /dev/raw/raw6
chmod 660 /dev/raw/raw7
# OCR
chown root:oinstall /dev/raw/raw1
chown root:oinstall /dev/raw/raw2
chmod 660 /dev/raw/raw1
chmod 660 /dev/raw/raw2
# Voting Disks
chown oracle:oinstall /dev/raw/raw3
chown oracle:oinstall /dev/raw/raw4
chown oracle:oinstall /dev/raw/raw5
chmod 644 /dev/raw/raw3
chmod 644 /dev/raw/raw4
chmod 644 /dev/raw/raw5

4.11 Oracle Clusterware Daemon Fails on Computer Restart

If different user IDs are used for installing Oracle Database 10g and Oracle Clusterware, then restarting the system results in OCR errors. Refer to the My Oracle Support (formerly OracleMetaLink) note 551478.1 for more information.

Workaround: Oracle recommends that you apply patch set 10.2.0.3 or higher to Oracle Clusterware installation before patching Oracle Database.

This issue is tracked with the Oracle bug 4748946.

4.12 Configuring Storages Devices for Oracle Clusterware on 2.6 Kernel Distributions

This section is for database and system administrators who intend to install or migrate to Oracle RAC 10g Release 2 (10.2.0) on Red Hat Enterprise Linux 5 and who need to configure raw devices for Oracle RAC and Oracle Clusterware. The Linux 2.6 kernel with these distributions requires additional configuration steps. The section contains the following topics:

• Overview of Device Naming Persistence Changes

• Configuring Raw Devices for Clusterware on Red Hat

• Relocate Oracle Clusterware Files from Raw to Block Devices

4.13 Installing Oracle Database Client into an Existing Oracle Home

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.

4.14 Database Installation Types

If you perform a Custom installation, then ensure that you install only the components covered by your license. You cannot install Standard Edition using Custom installation.

4.15 Oracle Storage Compatibility Program Obsolete

Oracle Storage Compatibility Program (OSCP) is no longer valid. Disregard any content about OSCP in the Oracle Database Installation Guide for Linux on POWER.

5.1 Building Pro*C Applications if PostgreSQL is Installed

If the postgresql-devel package is installed on the system, then you must add the following directory to the beginning of the sys_include parameter in the $ORACLE_HOME/precomp/admin/pcscfg.cfg file before building Pro*C applications:

$ORACLE_HOME/precomp/public

If you do not make this change, then you may encounter errors similar to the following when linking the applications:

/tmp/ccbXd7v6.o(.text+0xc0): In function `drop_tables': 
: undefined reference to `sqlca'

This issue is tracked with Oracle bug 3933309.

This issue is fixed with the 10.2.0.5 patch set.

5.2 Floating Point and Integer Formal Arguments Compilation Issue

An external C call specification with both floating point and integer formal arguments may not work correctly with a shared libary compiled to the ELF32 ABI.

Workaround: This problem is confined to external procedures compiled in Linux ppc32 architecture and will not affect the ones in Linux ppc64 architecture. You may have to change the external C call specification to use different formal arguments.

This issue is tracked with Oracle bug 7695347.

5.3 Encoding Information Not Present in Translated Help Files

If the system uses a European language, you might see corrupted characters in Table of Contents of database tools, such as Database Configuration Assitant.

This issue is tracked with Oracle bug 3957096.

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

5.4 Oracle Clusterware Files Issues

The following note applies if you are using Red Hat Enterprise Linux 4, Red Hat Enterprise Linux 5, or SUSE Linux Enterprise Server 10 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 on Red Hat Enterprise Linux 4, and Red Hat Enterprise linux 5, or the /etc/init.d/after.local file on SUSE Linux Enterprise Server 10 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 660 /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

5.5 Link Error During genorasdksh on Red Hat Enterprise Linux 4

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

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 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.

5.6 Cluster Verification Utility

This section lists the issues with Cluster Verification Utility on Red Hat Enterprise Linux 4, Red Hat Enterprise Linux 5, SUSE Linux Enterprise Server 9, and SUSE Linux Enterprise Server 10:

• Cluster Verification Utility (CVU) does not support shared checks for raw disks used for Oracle Cluster File System version 2 on Red Hat Enterprise Linux 4.0, Red Hat Enterprise Linux 5, SUSE Linux Enterprise Server 9, and SUSE Linux Enterprise Server 10.

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

  compat-libstdc++-devel-7.3-2.96.128
  

5.7 VLM Window Size on Red Hat Enterprise Linux

To use hugepages or to accommodate the VLM window size on Red Hat Enterprise Linux 4, or Red Hat Enterprise Linux 5, 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

5.8 Oracle C++ Call Interface Compiler Support

The current GNU C++ compiler version that OCCI supports with Red Hat Enterprise Linux 4.0 is GCC 3.2.3.

Workaround: Install Red Hat Enterprise Linux 4 with GCC 3.2.3.

http://www.oracle.com/technetwork/database/features/oci/index-090820.html

5.9 Oracle XML Developer's Kit Compiler Support

On Red Hat Enterprise Linux 4, Oracle XML Developer's Kit (XDK) is not supported with GCC. XDK is supported with Intel C++ compiler (ICC).

5.10 Link Error During genorasdksh on Red Hat Enterprise Linux 4

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

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 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.

5.11 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.

5.12 SRVCTL and VIPCA Utilities Set the LD_ASSUME_KERNEL Parameter

The SRVCTL and VIPCA utilities set the environmental variable LD_ASSUME_KERNEL. Setting this parameter on SUSE Linux Enterprise Server 10 and SUSE Linux Enterprise Server 11 causes the SRVCTL and VIPCA utilities to exit with the following error:

/opt/oracle/crs/jdk/jre/bin/java: 
error while loading shared libraries: 
libpthread.so.0: cannot open shared object file:
No such file or directory

Workaround: Remove the LD_ASSUME_KERNEL variable from the VIPCA and SRVCTL utilities. For the VIPCA utility, alter the $CRS_HOME/bin/vipca script on all nodes to remove LD_ASSUME_KERNEL. After the "if" statement in line 123, add an unset command to ensure LD_ASSUME_KERNEL is not set as follows:

arch='uname -m'
#       if [ "$arch" = "i686" -o "$arch" = "ia64" -o "$arch" = "x86_64" ]
#       then
#            LD_ASSUME_KERNEL=2.4.19
#            export LD_ASSUME_KERNEL
#       fi
            unset LD_ASSUME_KERNEL

With the newly inserted line, root.sh should be able to call VIPCA successfully.

For the SRVCTL utility, alter the $CRS_HOME/bin/srvctl scripts on all nodes by adding a line, unset LD_ASSUME_KERNEL, after line 174 as follows:

LD_ASSUME_KERNEL=2.4.19
export LD_ASSUME_KERNEL
unset LD_ASSUME_KERNEL

Oracle recommends explicitly removing LD_ASSUME_KERNEL and not merely commenting it out to handle cases where LD_ASSUME_KERNEL might be set in the environment (login shell).

These files must be altered after applying the 10.2.0.2 or 10.2.0.3 patch sets, as these patch sets include the LD_ASSUME_KERNEL settings for Red Hat Enterprise Linux 5, SUSE Linux Enterprise Server 10, and SUSE Linux Enterprise Server 11. This issue is fixed in the 10.2.0.4 patch set.

5.13 Error While Loading Shared Library When SELinux is Enabled on Red Hat Enterprise Linux 5

SQL*Plus and Oracle Call Interface (OCI) program calls fail when selinux is in Enforcing mode on Red Hat Enterprise Linux 5.

Workaround: Shift selinux to Permissive mode on the system.

This issue is tracked with Oracle bug 6079461.

5.14 Linking Applications with Oracle Database Client Libraries

The use of the client static library is not supported.

5.15 MAX_IDLE_BLOCKER_TIME Does Not Work in Oracle RAC Environment

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.

5.16 Mapping of 127.0.0.2 to the Local Host Name

By default, the host name of a computer is mapped to the IP address 127.0.0.2 through an entry in the /etc/hosts similar to the following on SUSE Linux Enterprise Server 10:

127.0.0.2       test test.example.com

YaST does this to provide compatibility with earlier versions of the applications that had problems running on desktops with dynamically assigned host names from DHCP. This mapping may cause certain Oracle networking libraries to encounter errors when they attempt to resolve the host name of the computer. To avoid these problems, the entry should be removed from the /etc/hosts file. Note that several network related YaST utilities may add this entry back to the file.

The host name must be included in the /etc/hosts file. if you do not include the host name in this file, then the following error is displayed:

ORA-00600: internal error code, arguments: [keltnfy-ldmInit],[46],[1],[],[],[],[],[]

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

You must install the 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. All the above installations must to be done before installing Oracle database.

On SUSE Linux Enterprise Server 9, install the following components:

• The RTE component: vacpp.rte.70.sles9.jan2006.update.tar.gz

• The XL Optimization Libraries: vac.lib.70.sles9.tar

On Red Hat Enterprise Linux 4, install the following components:

• The RTE component: vacpp.rte.70.rhel4.dec2005.update.tar.gz

• The XL Optimization Libraries: vac.lib.70.rhel4.tar

5.18 Relink of Database 10g Release 2 Fails

Relink of Database 10g Release 2 fails when you install Database 10g Release 2 (10.2.0.1) on Red Hat Enterprise Linux 4 (Update 2 or later). To resolve this issue, you need to install the patch mentioned in Oracle bug 4767801 and retry linking.

5.19 Blank Help Pages for Oracle Universal Installer

Help pages for Oracle Universal Installer appear blank for Japanese language locale that has the following settings:

NLS_LANG=Japanese_Japan.JA16EUC
LANG=ja_JP.eucJP

Workaround: Run the following command to start Oracle Universal Installer:

./runInstaller -J-Dibm.stream.nio=TRUE

This issue is tracked with Oracle bug 5106619.

5.20 Error While Installing 10.2.0.1

An error is generated while installing Oracle Database 10.2.0.1 on Red Hat Enterprise Linux 4 Update 2 or later and SUSE Linux Enterprise Server 9 with service pack 2 or later. Most of the times, the error is generated when you perform any of the following tasks:

• While installing Oracle Database 10.2.0.1 after a fresh and complete installation of Red Hat Enterprise Linux 4 Update 2

• While installing Oracle Database 10.2.0.1 after a fresh and complete installation of SUSE Linux Enterprise Server 9 with service pack 2 or later

• When you start dbca or netca from the command line or Oracle Universal Installer, if Standard installation is selected

Workaround: Before installing Oracle Database 10g Release 2, verify the contents of the /etc/resolv.conf file. Edit the file to make the following change:

Change the line similar to:

domain=my.net.com

To:

search=my.net.com

The original /etc/resolve.conf file can be restored after the database installation is complete.

5.21 Database Control Does not Display the Listener Details

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 shut down the Database Control with the emctl stop dbconsole command. Modify the targets.xml file located in $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.

5.22 Vendor Clusterware Restrictions for Node Names

If you use a vendor clusterware with Oracle Clusterware and Oracle Real Application Clusters, then you must use the node names and host names registered with that vendor clusterware you have installed. Refer to the Certifications page on My Oracle Support (formerly OracleMetaLink) for information about vendor clusterware supported for your Linux distribution.

6.1 Incorrect Kernel Parameter Values

In Oracle Database Installation Guide for Linux on POWER, Chapter 2, section, "Configuring Kernel Parameters," and Oracle Database Quick Installation Guide for Linux on POWER, section "Configuring Kernel Parameters," update or add the following to the existing list of Kernel Parameters:

6.2 Incorrect Shell Limit Setting

In Oracle Database Installation Guide for Linux on POWER, Chapter 2, section, "Setting Shell Limits for the oracle User," the values and the process to increase the shell limits is incorrect.

Update the following in the "Setting Shell Limits for the oracle User" section:

Add or edit the following line in the /etc/pam.d/login file, if it does not exist:

session required pam_limits.so

Add the following lines in the /etc/security/limits.conf file:

oracle soft nproc 16384
oracle hard nproc 16384
oracle soft nofile 65536
oracle hard nofile 65536

After you set the hard and soft values in the /etc/security/limits.conf file, you do not have to modify the /etc/profile file.

6.3 List of Packages for Asianux 2 and Red Hat Enterprise Linux 5

The following packages (or later versions) must be installed for Asianux 2 and Red Hat Enterprise Linux 5:

binutils-2.17.50.0.6-2.el5
compat-libstdc++-33-3.2.3-61
elfutils-libelf-0.125-3.el5
elfutils-libelf-devel-0.125
gcc-4.1.2-14
gcc-c++-4.1.1-52
glibc-2.5-18
glibc-common-2.5-12
glibc-devel-2.5-18
glibc-headers-2.5-18
libaio-0.3.106
libaio-devel-0.3.106
libgcc-4.1.1-52
ibstdc++-4.1.1
libstdc++-devel-4.1.1-52.e15
make-3.81-1.1

6.4 List of Packages for SUSE Linux Enterprise Server 10

The following packages (or later versions) must be installed for SUSE Linux Enterprise Server 10:

binutils-2.16.91.0.5-23.4 (ppc)
libaio-64bit-0.3.104-14.2 (ppc)
libaio-devel-64bit-0.3.104-14.2 (ppc)
libaio-0.3.104-14.2 (ppc)
libaio-devel-0.3.104-14.2 (ppc)
gcc-4.1.0-28.4 (ppc)
gcc-c++-4.1.0-28.4 (ppc)
libgcc-64bit-4.1.0-28.4 (ppc)
libgcc-4.1.0-28.4 (ppc)
glibc-devel-2.4-31.63 (ppc)
glibc-devel-64bit-2.4-31.63 (ppc)
libstdc++-devel-4.1.0-28.4 (ppc)
libstdc++-devel-64bit-4.1.0-28.4 (ppc)
sysstat-6.0.2-16.4 (ppc)
compat-libstdc++-64bit-5.0.7-22.2 (ppc) 
make-3.80-202.2 (ppc)

6.5 List of Packages for SUSE Linux Enterprise Server 11

The following packages (or later versions) must be installed for SUSE Linux Enterprise Server 11:

binutils-2.19-11.28 (ppc64)
libgcc43-4.3.3_20081022-11.18 (ppc64)
libstdc++43-32bit-4.3.3_20081022-11.18 (ppc64)
libstdc++43-4.3.3_20081022-11.18 (ppc64)
libstdc++43-devel-32bit-4.3.3_20081022-11.18 (ppc64)
libstdc++43-devel-4.3.3_20081022-11.18 (ppc64)
sysstat-8.1.5-7.8 (ppc64)
gcc-4.3-62.198 (ppc64)
ksh
make-3.81 make-3.81
glibc-2.9-13.2 (ppc64)
glibc-32bit-2.9-13.2 (ppc64)
glibc-devel-2.9-13.2 (ppc64)
glibc-devel-32bit-2.9-13.2 (ppc64)
libaio-0.3.104-140.22 (ppc64)
libaio-32bit-0.3.104-140.22 (ppc64)
libaio-devel-0.3.104-140.22 (ppc64)
libaio-devel-32bit-0.3.104-140.22 (ppc64)

6.6 Incorrect Oracle Clusterware Home Example

In Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide for Linux, Chapter 2, "Pre-Installation Tasks," in the section "Oracle Clusterware Home Directory," it incorrectly lists the path /u01/app/oracle/product/crs as a possible Oracle Clusterware home path. A default Oracle base path is /u01/app/oracle, and the Oracle Clusterware home must never be a subdirectory of the Oracle base directory.

A possible Oracle Clusterware home directory is in a path outside of the Oracle base directory. for example, if the Oracle base directory is u01/app/oracle, then the Oracle Clusterware home can be an option similar to one of the following:

u01/crs/
/u01/crs/oracle/product/10/crs
/crs/home

6.7 Oracle Clusterware and Oracle RAC Virtual IP Address Status

In Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide for Linux, Chapter 2, "Pre-Installation Tasks,"section 2.6.1, "IP Address Requirements," the following text states that the virtual IP address (VIP) should respond to a ping command:

During installation, OUI 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.

6.8 Incorrect Value for MAXINSTANCES

In Oracle Database Administrator's Reference for UNIX-Based Operating Systems, Appendix H, "Database Limits," states the incorrect maximum value (63) for the MAXINSTANCES variable. The correct maximum limit for the variable is 1055.

6.9 Oracle RAC and the Hangcheck_reboot Parameter on Linux 2.6 Kernels

In Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide for Linux, Chapter 2, "Pre-Installation Tasks," Section 2.16, "Checking the Configuration of the Hangcheck-timer Module,"as initially released, information about the hangcheck_reboot parameter is missing.

The hangcheck_reboot parameter indicates whether the hangcheck-timer should restart the node. The hangcheck-timer restarts the node if the kernel fails to respond within the time determined by the sum of the hangcheck_tick and hangcheck_margin parameter values, and the hangcheck_tick parameter value is greater than or equal to 1. If the hangcheck_reboot parameter is set to zero (0), then the hangcheck-timer will not restart the node.

By default, on 2.4 Linux kernels, the value of hangcheck_reboot is 1. However, on 2.6 kernels, the default value is 0. In an Oracle RAC environment, you must set the hangcheck_reboot parameter to 1.

Set hangcheck_reboot=1 while loading the hangcheck-timer module. If you find that the cluster produces false node evictions, then increase the hangcheck_margin parameter value, and retest the cluster.

6.10 Configuring Oracle Clusterware Process Monitor Daemon

The 10.2.0.4 patch release for Oracle Clusterware on Linux includes the Oracle Clusterware Process Monitor Daemon (oprocd). It is started automatically by Oracle Clusterware to detect system hangs. When it detects a system hang, it restarts the hung node.

Review the following configuration information if you have installed the 10.2.0.4 patch set.

Oracle has found wide variations in scheduling latencies observed across operating systems and versions of operating systems. Because of these scheduling latencies, the default values for oprocd can be overly sensitive, particularly under heavy system load, resulting in unnecessary oprocd-initiated restarts (false restarts).

Oracle recommends that you address scheduling latencies with your operating system vendor to reduce or eliminate them as much as possible, as they can cause other problems.

To overcome these scheduling latencies, Oracle recommends that you set the Oracle Clusterware parameter diagwait to the value 13. This setting increases the time for failed nodes to flush final trace files, which helps to debug the cause of a node failure. You must shut down the cluster to change the diagwait setting. However, if you prefer, you can use the default timing threshold for diagwait. In that case, you do not need to perform the procedure documented here.

If you require more aggressive failover times to meet more stringent service level requirements, then you should open a service request with Oracle Support to receive advice about how to tune for lower failover settings.

To change the diagwait setting:

1. Log in as root, and run the following command on all nodes, where CRS_home is the home directory of the Oracle Clusterware installation:

   # CRS_home/bin/crsctl stop crs
   

2. Enter the following command, where CRS_home is the Oracle Clusterware home:

   # CRS_home/bin/oprocd stop
   

   Repeat this command on all nodes.

3. From one node of the cluster, change the value of the diagwait parameter to 13 seconds by issuing the following command as root:

   # CRS_home/bin/crsctl set css diagwait 13 -force
   

4. Restart the Oracle Clusterware by running the following command on all nodes:

   # CRS_home/bin/crsctl start crs
   

5. Run the following command to ensure that Oracle Clusterware is functioning properly:

   # CRS_home/bin/crsctl check crs
   

6.11 DB_BLOCK_SIZE Initialization Parameter Update

In Oracle Database Administrator's Reference for UNIX-Based Operating Systems, chapter 1,section "DB_BLOCK_SIZE Initialization Parameter," lists the incorrect value of DB_BLOCK_SIZE parameter. The maximum value to which you can set the DB_BLOCK_SIZE is 16 KB on Linux x86. It is 32 KB on all other UNIX platforms.

6.12 Oracle Inventory Group Name

In Oracle Database documentation, Oracle inventory group is represented as oinstall. However, it is not mandatory to use the same name, you can enter a different name for the group.

6.13 Incorrect /etc/profile Reference

In Oracle Database Installation Guide for Linux on POWER, under Section 2.6, "Configure Kernel Parameters", subsection "Setting Shell Limits for the oracle User", the third list item has an incorrect reference to the /etc/profile file. Ignore the entire third list item as making changes in the /etc/profile file is not required.

6.14 Incorrect Control File Size Limits

In Oracle Database Administrator's Reference for UNIX-Based Operating Systems , Appendix H, "Database Limits," Table H-2, "File Size Limits," states an incorrect value of 20000 database blocks as control file size. The correct value is 25000 control file blocks with a block size of 4096 bytes.

6.15 Kernel Version Requirements

The system must be running the following kernel version (or a later version):

• Red Hat Enterprise Linux 4.0:

  2.6.9-11.EL

• Red Hat Enterprise Linux 5.0:

  2.6.18

• SUSE Linux Enterprise Server 9:

  2.6.5-7.191-pseries64

• SUSE Linux Enterprise Server 10:

  2.6.16

• SUSE Linux Enterprise Server 11:

  2.6.27

6.16 Incorrect Information About JPublisher and Oracle SQLJ Installation

• In Oracle Database Installation Guide for Linux on POWER, Chapter 4, section, "Installing Oracle Database 10g Products from the Companion CD," erroneously states that JPublisher and Oracle SQLJ are installed. The correct information is that JPublisher is not a part of Companion CD and Oracle SQLJ Demos are installed with the Companion CD instead of Oracle SQLJ.

• In Oracle Database Companion CD Installation Guide for Linux on POWER, Chapter 1, section, "Products Available in the Oracle Database 10g Products Installation Type," erroneously states that JPublisher and Oracle SQLJ are installed. The correct information is that JPublisher is not a part of Companion CD and Oracle SQLJ Demos are installed with the Companion CD instead of Oracle SQLJ.

  Note:

  The SQLJ Demos are installed if Oracle SQLJ was installed before running the Companion CD installation.