< Previous  | TOC | Index | Next  >

Oracle troubleshooting topics

Headings indicate likely symptoms or procedures required for a solution.

Oracle user must be able to read /etc/llttab file

Check the permissions of the /etc/llttab file; the oracle user must be allowed to read it.

Error when starting an Oracle instance

If the VCSMM driver (the membership module) is not configured, an error is displayed on starting the Oracle instance that resembles:

ORA-29702: error occurred in Cluster Group Operation

To start the driver, enter the following command:

# /sbin/vcsmmconfig -c

The command included in the /etc/vcsmmtab file enables the VCSMM driver to be started at system boot.

Missing dialog box during installation of Oracle9i release 2

Symantec recommends using the installsfrac program to install Oracle9i RAC. The following troubleshooting steps only apply if you call the runInstaller utility directly.

During installation of Oracle9i Release 2 using the runInstaller utility, if you choose the Enterprise Edition or Custom Install (with RAC option), a dialog box prompting you about the installation nodes should appear. If the dialog box fails to appear, complete the following procedure.

 To resolve missing dialog box issue during Oracle9i installation

1. Exit the runInstaller utility.
2. On the cluster node, check for the Veritas CM library in the following location.

   For PA clusters:

    

   32-bit libnmapi2.sl	/opt/nmapi/nmapi2/lib/
   64-bit libnmapi2.sl	/opt/nmapi/nmapi2/lib/pa20_64

   For IA clusters:

    

   32-bit libnmapi2.so	/opt/nmapi/nmapi2/lib/hpux32/lib/
   64-bit libnmapi2.so	/opt/nmapi/nmapi2/lib/hpux64/lib/

3. Start the VCSMM driver on both the nodes.

   # /sbin/vcsmmconfig -c

Instance numbers must be unique (error code 205)

If you encounter error code 205 when the skgxnreg function fails (look in the Oracle trace files to find the error returned), make sure there is a unique instance number specified in the $ORACLE_HOME/dbs/init${ORACLE_SID}.ora file on each node.

ORACLE_SID must be unique (error code 304)

If you encounter error code 304 when the skgxnreg function fails (look in the Oracle trace file to find the error returned), make sure that the ORACLE_SID environment variable specified during Oracle startup is unique on each node in your cluster. Also, make sure that the SID attribute for the Oracle resource in the main.cf is specified locally and is unique.

Oracle log files show shutdown called even when not shutdown manually

The Oracle enterprise agent calls shutdown if monitoring of the Oracle/Netlsnr resources fails for some reason. On all cluster nodes, look at the following VCS and Oracle agent log files for any errors or status:

/var/VRTSvcs/log/engine_A.log

/var/VRTSvcs/log/Oracle_A.log

Set MLOCK privilege for DBA user

If ASYNCH_IO errors occur during select and update queries on the Oracle database, the workaround involves setting the MLOCK privilege for the dba user.

 To set MLOCK privilege for DBA user

1. Give the MLOCK privilege to the dba group:

   # setprivgrp dba MLOCK

2. Create the /etc/privgroup file and add the line:

   dba MLOCK

3. Verify the availability of MLOCK privilege for the dba group:

   # /usr/bin/getprivgrp dba