B
Troubleshooting

Specific topics covered in this chapter are:

• Understanding the Trace Files

• PGMS

• Using PhysicalDrive for Raw Partitions

• Performing SHUTDOWN

Understanding the Trace Files

Oracle Parallel Server offers the following trace files in ORACLE_HOME\RDBMS80\TRACE for troubleshooting:

Trace File	Description
SIDLCKn.TRC	Trace file for the LCKn process. This trace file shows lock request for other background processes.
SIDLMDn.TRC	Trace file for the LMDn process. This trace file shows lock requests.
SIDLMON.TRC	Trace file for the LMON process. This trace file show status of cluster, including the "Reconfiguration complete" message.
SIDP00n.TRC	Trace file for the parallel query slaves.

PGMS

If you are having difficulty starting services or the database, it could be because of PGMS. Check the PGMS.LOG file stored in WINNT\SYSTEM32\PGMS.LOG.

If you used the CRTSRV script in "Step 4: Create Services" in Chapter 5, "Configuring Oracle Parallel Server", OraclePGMSService automatically starts up and shuts down when the OracleServiceSID service is started.

You can still have OraclePGMSService start up automatically with a OracleServiceSID service by entering the following at the command for each node:

C:\> OPSREG80 ADD SID 

You can also discontinue the OraclePGMSService service automatic start up with OracleServiceSID service by entering the following at the command line for each node:

C:\> OPSREG80 DEL SID 

Using PhysicalDrive for Raw Partitions

When creating symbolic links for the logical drives with SETLINKS utility, do not use \\.\PhysicalDrive. If you use \\.\PhysicalDrive as a symbolic link, you can corrupt your system. Use the symbolic links provided in the ORALINKx.TBL file(s), as described in Chapter 5, "Configuring Oracle Parallel Server".

Performing SHUTDOWN

This section describes issues with:

• SHUTDOWN NORMAL

• SHUTDOWN ABORT

SHUTDOWN NORMAL

Do not perform SHUTDOWN NORMAL on more than one node at a time. Simultaneous SHUTDOWN NORMAL commands will cause the system to hang. If you need to bring down more than one node, be sure to complete one SHUTDOWN NORMAL at a time. This restriction also means that you should not use the Oracle Enterprise Manager console to perform a SHUTDOWN NORMAL on the database.

SHUTDOWN ABORT

SHUTDOWN ABORT is not supported for nodes in a cluster. If you must perform a SHUTDOWN ABORT, shut down the OracleServiceSID in one of two ways:

• From the MS-DOS command line, enter:

  C:\> NET STOP OracleServiceSID
  

• From the Control Panel's Services window, select the OracleServiceSID service, then choose Stop.

---