Oracle log files


		< Previous \| TOC \| Index \| Next >

Review the information on the files that you must access.

To check the Oracle log file
- For Oracle 10g R1: $ORA_CRS_HOME/crs/log
- For Oracle 10g R2: $ORA_CRS_HOME/log/<hostname>/crsd/
  This file contains the logs pertaining to the CRS resources such as the virtual IP, Listener, and database instances. It indicates some configuration errors or Oracle problems, because CRS does not directly interact with any of the Veritas components.
To check for core dumps
- For Oracle 10g R1: $ORA_CRS_HOME/crs/init
- For Oracle 10g R2: $ORA_CRS_HOME/log/<hostname>/crsd/
  Core dumps for the crsd.bin daemon are written here. Use this file for further debugging.
To check the Oracle css log file
- For Oracle 10g R1: $ORA_CRS_HOME/css/log/
- For Oracle 10g R2: $ORA_CRS_HOME/log/<hostname>/cssd/
  The css logs indicate actions such as reconfigurations, missed checkins, connects, and disconnects from the client CSS listener. If there are membership issues, they will show up here. If there are communication issues over the private networks, they are logged here. The ocssd process interacts with vcsmm for cluster membership.
To check for ocssd core dumps
- For Oracle 10g R1: $ORA_CRS_HOME/css/init
- For Oracle 10g R2: $ORA_CRS_HOME/log/<hostname>/cssd/
  Core dumps from the ocssd and the pid for the css daemon whose death is treated as fatal are located here. If there are abnormal restarts for css the core files are found here.