1 description
In 11g, view the log of the grid and enter $oracle_hom/log.
[[email protected] ~]$ cd $ORACLE _home/log/[[email protected] log]$ lscrs diag rac1[[email protected] log]$ cd rac1[[email protected] rac1]$ lsacfs admin afd alertrac1.log client crflogd crfmond crsd cssd ctssd diskmon evmd gipcd gnsd gpnpd mdnsd ohasd racg srvm xag[[email protected] rac1]$ lltotal 76drwxr-xr-x 6 Grid oinstall 4096 dec 11 01:02 acfsdrwxr-x--- 2 grid oinstall 4096 dec 11 01:02 admindrwxr-xr-x 2 grid oinstall 4096 dec 11 01:02 afd-rw-rw-r-- 1 grid oinstall 0 Dec 11 19:58 alertrac1.Logdrwxrwxrwt 2 grid oinstall 4096 dec 11 19:22 clientdrwxr-x--- 2 root oinstall 4096 dec 11 01:02 crflogddrwxr-x--- 2 root Oinstall 4096 dec 11 01:02 crfmonddrwxr-x--- 2 root oinstall 4096 dec 11 01:02 crsddrwxr-x--- 2 grid oinstall 4096 dec 11 01:02 cssddrwxr-x--- 2 root oinstall 4096 Dec 11 01:02 Ctssddrwxr-x--- 2 grid oinstall 4096 dec 11 01:02 diskmondrwxr-x--- 2 grid oinstall 4096 dec 11 01:02 evmddrwxr-x--- 2 grid oinstall 4096 dec 11 01:02 gipcddrwxr-x--- 2 root oinstall 4096 dec 11 01:02 gnsddrwxr-x--- 2 grid oinstall 4096 dec 11 01:19 gpnpddrwxR-x--- 2 grid oinstall 4096 dec 11 01:02 mdnsddrwxr-x--- 2 Root oinstall 4096 dec 11 01:17 ohasddrwxrwxr-t 5 grid oinstall 4096 dec 11 01:02 racgdrwxr-x--- 2 grid oinstall 4096 dec 11 01:02 srvmdrwxrwxr-x 2 grid oinstall 4096 dec 11 01:02 xag[[email protected] rac1]$
However, in the 12c, there is still the above directory structure, but there is nothing in the content. Since 12c, the log structure of the RAC has changed.
There are two types of RAC in 12c:
1. Standard Cluster
Name of Alert Log:alert.log
Location of alert log: $ORACLE _base/diag/crs/host01/crs/trace
2. Flex Cluster
Name of Alert Log:alertLocation of alert log: $ORACLE _home/log/host01
My test environment is standard cluster, so I don't see any information in the 11g RAC architecture. But if it is flex cluster, then the log structure is the same as the cluster before 12c.
[[Email protected] trace]$ crsctl query crs activeversionoracle clusterware active version on the cluster is [12.1.0.2.0][[email protected] Trace]$ pwd/u01/app/grid/diag/crs/rac1/crs/trace[[email protected] trace]$ lsalert.log crsctl_130341.trm crsctl_139270.trm gpnptool_131848.trmclscfg_108107.trc crsctl_130399.trc crsctl_139276.trc gpnptool_137540.trcclscfg_108107.trm crsctl_130399.trm crsctl_139276.trm gpnptool_137540.trmclscfg_88148.trc crsctl_130457.trc crsctl_139287.trc gpnptool_141922.trcclscfg_88148.trm crsctl_130457.trm crsctl_139287.trm gpnptool_141922.trmclscfg_94297.trc crsctl_130754. Trc crsctl_139288.trc gpnptool_ 144685.trcclscfg_94297.trm crsctl_130754.trm crsctl_139288.trm gpnptool_144685.trmcrsctl_103046.trc crsctl_130819. Trc crsctl_139320.trc gpnptool_ 89849.trc
2 Verification
[[email protected] ~]# cd /proc/' ps -c crsd.bin -o pid= '/fd[[email protected] fd]# pwd/proc/114497/fd[[email protected] fd]# ll |grep / U01/APP/LRWX------ 1 ROOT ROOT 64 DEC 11 01:20 1 -> /U01/ APP/GRID/CRSDATA/RAC1/OUTPUT/CRSDOUT.TRCLRWX------ 1 root root 64 Dec 11 01:20 111 -> /u01/app/12.1.0/grid/rdbms/mesg/diaus.msblr-x------ 1 root root 64 dec 11 01:20 120 -> /u01/app/12.1.0/grid/rdbms/mesg/ DIAUS.MSBL-WX------ 1 root root 64 dec 11 01:20 15 -> / U01/app/grid/diag/crs/rac1/crs/trace/crsd.trc ... [[email protected] fd]#[[email protected] fd]# cd /proc/' ps -C Ocssd.bin -o pid= '/fd[[email protected] fd]#[[email protected] fd]# ll |GREP /U01/APP/LRWX------ 1 grid oinstall 64 dec 11 01:19 1 -> /u01/app/grid/crsdata/rac1/output/ocssdout.trclr-x------ 1 grid oinstall 64 dec 11 01:20 118 -> /u01/app/12.1.0/grid/has/mesg/rdeus.msblr-x------ 1 grid oinstall 64 dec 11 01:20 124 -> /u01/app/12.1.0/ grid/has/mesg/clswus.msblr-x------ 1 grid oinstall 64 dec 11 01:20 135  -> /U01/APP/12.1.0/GRID/RDBMS/MESG/DIAUS.MSBLRWX------ 1 grid oinstall 64  DEC 11 01:19 2 -> /U01/APP/GRID/CRSDATA/RAC1/OUTPUT/OCSSDOUT.TRCLRWX------ 1 grid oinstall 64 dec 11 01:19 3 -> /u01/app/grid/ CRSDATA/RAC1/OUTPUT/OCSSDOUT.TRCLRWX------ 1 grid oinstall 64 dec 11 01:19 7 -> /u01/app/grid/diag/crs/rac1/crs/trace/ocssd.trc ...
In fact, this change is another trend of Oracle's log management. Oracle introduced ADR (automaticdiagnostic Repository) from 11g, an ADR is a file-based repository for database diagnostic data such as tracking, accidental event dumps and packages, alert logs, Health Monitor reports, Core dumps, etc.).
Starting with 11g R1, databases, automated storage management (ASM), Cluster readiness Services (CRS), and other Oracle products or components store all diagnostic data in ADR. Each instance of each product stores diagnostic data in its own ADR home directory.
[[email protected] fd]# su-grid[[email protected] ~]$ adrciadrci:release 12.1.0.2.0-production on Fri Dec 11 21:13:42 2015Copyright (c) 1982, Oracle and/or its affiliates. All rights reserved. ADR base = "/u01/app/grid" adrci> show Homeadr Homes:diag/tnslsnr/rac1/mgmtlsnrdiag/tnslsnr/rac1/listener_ scan1diag/tnslsnr/rac1/listenerdiag/crs/rac1/crsdiag/clients/user_grid/host_1874443374_82diag/rdbms/_mgmtdb/- Mgmtdbdiag/asm/+asm/+asm1
The new directory structure in this 12c is the directory structure of the ADR. As you can see from the changes in 12c, Oracle has used ADR to manage a variety of logs.
Starting with 12.1.0.2 Oracle Grid Infrastructure have adapted the Automatic Diagnostic Repository (ADR) based management O F Diagnostic information. As a result of this adaptation, all diagnostic information have been moved under the ADR folder tree. This applies to the host alert logs as well as to ASM alert logs and other logs as well as traces.
Ext.: http://www.cndba.cn/dave/article/160
Changes to the Oracle 12c RAC log Architecture