Oracle® Database

4.1 Oracle Real Application Clusters (RAC) Support

The list of supported installation options and supported storage types for Oracle Clusterware, Oracle Real Application Clusters, and vendor clusterware are described in this section. Oracle plans to support additional Oracle Clusterware and RAC configurations in the future. Please check for updates to this document for the latest list of supported installation scenarios on the OTN Web site at:

http://www.oracle.com/technology/documentation/

Supported Oracle Real Application Clusters Configurations at the Time of This Publication

Oracle supports the software and storage configurations shown in the following table:

^Footnote 1 For Oracle Clusterware, the stored files are the OCR and voting disk. For RAC, the stored files are the database files.

4.2 Upgrading of Oracle9i to Oracle Database 10g Release 2 on Raw Devices

Use the following upgrade process if the database files are created on plain raw devices not using Logical Volume Manager (LVM). These steps are needed due to the skip offset differences between Oracle9i release 2 and Oracle Database 10g release 2. The skip offset for Oracle9i release 2 is 4k bytes. Starting with Oracle Database 10g release 2, the skip offset is 0 bytes.

1. Back up the database.

2. Back up each of the database file on the plain raw disks to a file using following command:

   # dd if=db_disk_name of=backup_file_name bs=512  skip=8
   
   

3. Restore the backed up database file to the disk using following commands:

   # dd if=backup_file_name of=db_disk_name bs=512
   
   

4. Follow the manual upgrade steps documented in Oracle Database Upgrade Guide.

4.3 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.4 Installing Oracle Security Manager

To install Oracle Security Manager, install Oracle Client and choose the Administrator installation type.

4.5 Upgrading Oracle Cluster Ready Services (CRS) from Release 10.1.0.2

This section lists the additional steps required when running the preupdate and rootupgrade scripts:

• When upgrading Oracle Cluster release 10.1 to 10.2, run the following command as the root user after running the preupdate.sh script and then complete the Oracle Clusterware release 10.2 installation:

  /usr/sbin/slibclean
  
  

• When upgrading Oracle Clusterware release 10.1.0.2, activate the volume group before running the rootupgrade script. Use the following command to activate the volume group:

  /usr/sbin/vgchange -a s vg1
  
  

  where vg1 is the volume group that stores the OCR and voting disks.

4.6 Installing Standard Edition on Automated Storage Management (ASM)

When installing Standard Edition and the starter database on Oracle Automated Storage Management (ASM), the Email enabled notification check box on the Select Database Management Option page is disabled.

This issue is tracked with Oracle bug 4553151.

4.7 Modifying a Virtual IP Address Node Application

When modifying the name, IP address, or netmask of an existing virtual IP address (VIP) resource, run 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.8 Pinging the Gateway for VIP Address

In Chapter 2, Preinstallation, the section IP Address Requirements contains the following sentence:

During installation, OUI pings the VIP, so ensure that the VIP responds to a ping command before starting installation.

This information is incorrect. The following is the correct information:

During installation, OUI pings the gateway to ensure that the VIP is reachable. Therefore, you should ensure that the default gateway responds to a ping command. To find the default gateway, use the route command. Refer to your operating system help for details.

4.9 listener.ora File Corrections

In Chapter 9, Understanding the Oracle Real Application Clusters Installed Configuration, the section "How Oracle Uses the Listener (listener.ora File)" contains a sample listener.ora file. The parameter entry, (IP=FIRST), should be added to the second address parameter of the listener_node1 definition. Additionally, two closing parentheses are required at the end of the sid_list_listener_node1 definition. The revised example should look like this:

listener_node1=
   (description=
    (address=(protocol=ipc)(key=extproc))
    (address=(protocol=tcp)(host=node1-vip)(port=1521)(IP=FIRST))
    (address=(protocol=tcp)(host=node1-ip)(port=1521)))
sid_list_listener_node1=
   (sid_list=
     (sid_desc=
      (sid_name=plsextproc)
       (oracle_home=/private/system/db)
      (program=extproc)))

7.1 Performance Issues with Generic Connectivity

There is a performance issue with Generic Connectivity (hsodbc). On the first query of a new connection, there could be significant delay up to several minutes. All subsequent SQL issued through the same dblink session will proceed without delay.

Check Oracle bug 4549924 for patch availability.

7.2 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.3 Importing a User Certificate Into Oracle Wallet Using Oracle Wallet Manager

Oracle Wallet Manager will fail to recognize the user certificate as valid if you capture the user certificate contents from the Oracle Certificate Authority site and save this as a flat file. This is because when saving as a flat file, all the lines of the user certificate are run together with no line breaks.

Workaround: Edit the user certificate. Insert a new line after -----BEGIN CERTIFICATE----- and a new line before -----END CERTIFICATE-----.

7.4 Using 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

This issue is being tracked with Oracle bug 4286338.