Oracle 11g R2 Log Structure Summary

Oracle began with the 11g, the log structure has made a relatively large adjustment, log storage directory and storage format has changed. The following summarizes the storage directory and directory structure for Oracle Database, Oracle snooping, ASM, and Oracle GI logs.

1. Oracle Database log

Oracle database logs are stored in the $oracle_base/diag/rdbms/<db_unique_name>/<oracle_sid> directory.

$ORACLE _base/diag/rdbms/<db_name>/<oracle_sid>/alert is used to store alert logs for ORACLE database, The logs are stored in an XML file, which is a new feature introduced by 11g.

$ORACLE _base/diag/rdbms/<db_name>/<oracle_sid>/trace is used to store alert logs and trace logs for ORACLE database. The alert log is stored as a text file with a naming convention of Alert_<oracle_sid>.log

$ORACLE _base/diag/rdbms/<db_name>/<oracle_sid>/cdump is used to store the memory dump directory directory.

$ORACLE _base/diag/rdbms/<db_name>/<oracle_sid>/incident is used to store event-related log and file information.

2. Listening log

The listening log is stored in $oracle_base/diag/tnslsnr/

The directory structure and function are similar to Oracle database.

3. ASM Log

ASM logs stored in $grid_base/diag/asm/<asm_name>/<sid>

The directory structure and function are similar to Oracle database.

4. Oracle Cluster log

The Oracle cluster components diagnostic log files are stored in the $grid_home/log/<nodename> directory. Each component in GI has its own directory in the $grid_home/log/<nodename> directory. The debug log files associated with the cluster components of the Oracle cluster are stored in the $grid_home/log/directory. In the typical 11g R2 gi directory, you can find the following directories, which contain debug log files for different GI components:

$GRID _home/log/<nodename>/alert<nodename>.log– for clusterware problem, check this file first

$GRID _home/log/<nodename>/agent contains Oraagent, Orarootagent, CRSD and OHASD daemons. Trace and diagnostic log files for oracssdagent and Oracssdmonitor.

$GRID _home/log/<nodename>/client contains trace and diagnostic logs for various GI clients, such as CLSCFG/GPNP/OCRCONFIG/OLSNODES/OIFCFG.

$GRID _home/log/<nodename>/crfmond contains trace and diagnostic log files that are recorded by the system monitoring service provided by the Oracle Cluster Health Monitor (Oracle CHM).

$GRID _HOME/LOG/<NODENAME>/CSSD contains the cluster synchronization CSS log, which includes actions from the client CSS listener, such as reconfiguration, missing check-in, connection, and disconnection. In some cases, the logger will record the message with the category Auth.crit the restart operation completed by Oracle. This information can be used to check the exact time that a restart occurred.

$GRID _HOME/LOG/<NODENAME>/CVU contains trace and debug logs generated by the Oracle Cluster Validation utility.

$GRID _HOME/LOG/<NODENAME>/EVMD contains trace and diagnostic files for the event Volume Manager (EVM) and the Evmlogger daemon. It is used less frequently in debugging than in the CRSD and CSSD directories.

$GRID _HOME/LOG/<NODENAME>/GNSD contains trace and debug log files for troubleshooting issues related to Oracle Grid Naming service, which was introduced in Oracle GI.

$GRID _HOME/LOG/<NODENAME>/MDNSD contains trace and diagnostic log files that are used to troubleshoot the multicast Domain Name service. The Oracle Grid Naming service uses this service to manage name resolution and service discovery.

$GRID _HOME/LOG/<NODENAME>/RACG includes trace and debug logs in each Oracle RACG executable file.

$GRID _HOME/LOG/<NODENAME>/CRFLOGD contains trace and diagnostic log files that are recorded by the cluster logger service provided by the Oracle Cluster Health Monitor (Oracle CHM).

$GRID _HOME/LOG/<NODENAME>/CRSD contains trace and diagnostic log files for the Oracle CRSD Daemon, starting processing from this directory is a good starting point when any Oracle cluster problem occurs.

The $GRID _HOME/LOG/<NODENAME>/CTSSD contains debug log files that are used to troubleshoot the Oracle Cluster time synchronization service, introduced in Oracle GI to synchronize clocks on cluster nodes.

$GRID _home/log/<nodename>/diskmon debug Log files that are used to troubleshoot Oracle Disk Monitor daemon processes.

$GRID _HOME/LOG/<NODENAME>/GIPLCD contains Debug and trace files that are used to troubleshoot the process of the Oracle grid inter-process Communication Gatekeeper program.

$GRID _HOME/LOG/<NODENAME>/GPNPD contains logs and output files for the Oracle grid Plug and Play daemon.

$GRID _HOME/LOG/<NODENAME>/OHASD contains logs and output files for the Oracle High Availability Service daemon. The OHASD log file is a truly important file for troubleshooting cluster startup issues in oracle11g and later versions.

$GRID _HOME/LOG/<NODENAME>/SRVM contains log files for the Oracle Server Manager service.

Reference: Oracle Database 11g RAC Handbook "Administrator's Guide"

This article is from the "DBA fighting!" blog, so be sure to keep this source http://hbxztc.blog.51cto.com/1587495/1924754

Oracle 11g R2 Log Structure Summary