Shulou(Shulou.com)05/31 Report--

This article mainly introduces the "oracle cluster cluster-related log viewing method". In the daily operation, I believe that many people have doubts about the oracle cluster cluster-related log viewing method. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "oracle cluster cluster-related log viewing method". Next, please follow the editor to study!

Cluster-related logs are mainly placed in $GRID_HOME/log and $ORACLE_HOME/log.

Note that the $GRID_HOME (often named $ORACLE_HOME) refers to the directory where the cluster software is installed, depending on your grid environment variable configuration (su-grid and then cat. Bash _ profile to see). The $ORACLE_HOME here refers to the directory where the oracle software is installed, depending on your oracle user's environment variables (su-oracle and then cat .bash _ profile to see)

The contents of the $GRID_HOME/log directory are as follows

[root@ora101 bin] # su-grid

[grid@ora101 ~] $cd $ORACLE_HOME

[grid@ora101 grid] $cd log/

[grid@ora101 log] $ls

Crs diag ora101

The content of $ORACLE_HOME/log is as follows

[root@ora102 bin] # su-oracle

[oracle@ora102 ~] $cd $ORACLE_HOME

[oracle@ora102 dbhome_1] $cd log/

[oracle@ora102 log] $ls

Diag ora101 ora102

Corresponding description of specific log and directory:

1) CRS logs are stored under $GRID_HOME/log/HOSTNAME/crsd

[grid@ora102 grid] $cd $ORACLE_HOME/log/ora102/crsd

[grid@ora102 crsd] $tail-n 10 crsd.log

2017-11-30 15 08 UiServer 41.814: [UiServer] [1900590848] {2V 25778v 543} Done for ctx=0x7fa30400c970

2017-11-30 15 0x7fa308009c40 09 set Properties 41.812: [UiServer] [1898489600] CS (0x7fa308009c40) set Properties (grid,0x7fa33c0dc150)

2017-11-30 15 09V 41.823: [UiServer] [1900590848] {2V V 25778v 544} Sending message to PE. Ctx= 0x7fa30400cdf0, Client PID: 15860

2017-11-30 15 09V 41.828: [UiServer] [1900590848] {2V V 25778v 544} Done for ctx=0x7fa30400cdf0

2017-11-30 15 set Properties 10 0x7fa308009c40 41.817: [UiServer] [1898489600] CS (0x7fa308009c40) set Properties (grid,0x7fa33c0dc150)

2017-11-30 15 10 41.827: [UiServer] [1900590848] {2 25778 545}. Ctx= 0x7fa304007af0, Client PID: 15860

2017-11-30 15 10 41.833: [UiServer] [1900590848] {2v 25778v 545} Done for ctx=0x7fa304007af0

2017-11-30 15 set Properties 11V 41.812: [UiServer] [1898489600] CS (0x7fa308009c40) set Properties (grid,0x7fa33c0dc150)

2017-11-30 15 11V 41.822: [UiServer] [1900590848] {2V V 25778v 546} Sending message to PE. Ctx= 0x7fa3040093e0, Client PID: 15860

2017-11-30 15 11V 41.828: [UiServer] [1900590848] {2v 25778v 546} Done for ctx=0x7fa3040093e0

2) CSS logs are stored in the "$GRID_HOME/log/HOSTNAME/crsd" directory

[grid@ora102 cssd] $pwd

/ u01/app/11.2.0/grid/log/ora102/cssd

[grid@ora102 cssd] $tail-n 10 ocssd.log

2017-11-30 15 sending status msg to all nodes 16V 43.636: [CSSD] [370063104] clssnmSendingThread: sending status msg to all nodes

2017-11-30 15 sent 16 sent 43.636: [CSSD] [370063104] clssnmSendingThread: sent 5 status msgs to all nodes

2017-11-30 15 16-48. 637: [CSSD] [370063104] clssnmSendingThread: sending status msg to all nodes

2017-11-30 15 sent 16 sent 48.637: [CSSD] [370063104] clssnmSendingThread: sent 5 status msgs to all nodes

2017-11-30 15 sending status msg to all nodes 16 sending status msg to all nodes 53.639: [CSSD] [370063104]

2017-11-30 15 sent 16 sent 53.639: [CSSD] [370063104] clssnmSendingThread: sent 5 status msgs to all nodes

2017-11-30 15 sending status msg to all nodes 16V 57.640: [CSSD] [370063104] clssnmSendingThread: sending status msg to all nodes

2017-11-30 15 sent 16 sent 57.640: [CSSD] [370063104] clssnmSendingThread: sent 4 status msgs to all nodes

2017-11-30 15 sending status msg to all nodes 1702.641: [CSSD] [370063104] clssnmSendingThread: sending status msg to all nodes

2017-11-30 15 sent 1714 02.641: [CSSD] [370063104] clssnmSendingThread: sent 5 status msgs to all nodes

3) EVM logs are stored in the "$GRID_HOME/log/HOSTNAME/crsd" directory

[grid@ora102 evmd] $pwd

/ u01/app/11.2.0/grid/log/ora102/evmd

[grid@ora102 evmd] $tail-n 10 evmd.log

2017-11-30 09 ora102', name 2015 01.300: [GIPCHGEN] [3279111936] gipchaResolveF [gipcmodGipcResolve: gipcmodGipc.c: 806]: EXCEPTION [ret gipcretKeyNotFound (36)] failed to resolve ctx 0x1d7c3f0 [000000000010] {gipchaContext: host 'ora102', name' 2533-5b5b-d375-7024, luid '7d1a6e2eMew 00000011, numNode 1, numInf 1, usrFlags 0x0, flags 0x5}, host' ora102', port '4fffran ca7amurf20cmurf19a, flags 0x0

2017-11-30 09VO 01.300: [CRSCCL] [3272427264] clsCclNewConn: added new conn to tempConList: newPeerCon = a8007ba0

2017-11-30 09 Disconnecting our connection to node 20V 01.300: [CRSCCL] [3272427264] PNC: Disconnecting our connection to node

2017-11-30 09 Accept connection from peer 20V 01.300: [CRSCCL] [3272427264] PNC: Accept connection from peer

2017-11-30 09initiated discconnect umsg 0x7f73ac00b330 2001.300: [GIPCHAUP] [3279111936] gipchaUpperDisconnect: initiated discconnect umsg 0x7f73ac00b330 {msg 0x7f73ac00c838, ret gipcretRequestPending (15), flags 0x2}, msg 0x7f73ac00c838 {type gipchaMsgTypeDisconnect (5), srcCid 00000000-0000062b, dstCid 00000000-00000581}, endp 0x7f739c00a5f0 [0000000000062b] {gipchaEndpoint: port '911d-a70c-59c0-6f2f, peer' ora101:EVMDMAIN2_1/232c-8a2c-944a-d9a9', srcCid 00000000-0000062b, dstCid 00000000-00000581, numSend 0, maxSend 100, groupListType 2, hagroup 0x1d0ff90, usrFlags 0x4000, flags 0x21c}

2017-11-309 gipchaUpperProcessDisconnect: dropping Disconnect to unknown msg 0x7f73ac0224e8 {type gipchaMsgTypeDisconnect (5), srcCid 00000000-00000581, dstCid 00000000-0000062b}, node 0x7f73ac00bab0 {host 'ora101', haName' a4a1-648b dstLuid 5549d389-6bbf9712 numInf 1, contigSeq 7, lastAck 5, lastValidAck 7, sendSeq [6: 7], createTime 41098124, sentRegister 1, localMonitor 0, flags 0x208}, ret gipcretFail (1)

2017-11-309 gipchaUpperProcessDisconnect: EXCEPTION [ret gipcretFail (1)] error during DISCONNECT processing for node 0x7f73ac00bab0 {host 'ora101', haName' a4a1-648b dstLuid 5549d389-6bbf9712 numInf 1, contigSeq 7, lastAck 5, lastValidAck 7, sendSeq [6: 7], createTime 41098124, sentRegister 1, localMonitor 0, flags 0x208}

2017-11-309 gipchaUpperCallbackDisconnect: completed DISCONNECT ret gipcretSuccess (0), umsg 0x7f73ac00b330 {msg 0x7f73ac00c838, ret gipcretSuccess (0), flags 0x2}, msg 0x7f73ac00c838 {type gipchaMsgTypeDisconnect (5), srcCid 00000000-0000062b, dstCid 00000000-00000581}, hendp 0x7f739c00a5f0 [0000000000062b] {gipchaEndpoint: port '911d-a70c-59c0-6f2f, peer' ora101:EVMDMAIN2_1/232c-8a2c-944a-d9a9', srcCid 00000000-0000062b, dstCid 00000000-00000581, numSend 0,100,groupListType 2, hagroup 0x1d0ff90, usrFlags 0x4000, flags 0x21c}

2017-11-3009VOV 20RV 01.316: [EVMD] [3596752704] Authorization database built successfully.

2017-11-30 09VOV 20V 01.427: [CLSE] [3596752704] clse_get_auth_loc: Returning default authloc: / u01/app/11.2.0/grid/auth/evm/ora102

4) the log corresponding to the RACG executable file is recorded in the racg directory in the $GRID_HOME/log/ and $ORACLE_HOME/log/ directories

[grid@ora102 racg] $pwd

/ u01/app/11.2.0/grid/log/ora102/racg

[grid@ora102 racg] $ll

Total 4

-rw-rw-r-- 1 grid oinstall 754 Nov 30 09:16 evtf.log

Drwxrwxrwt 2 grid oinstall 6 Aug 10 18:37 racgeut

Drwxrwxrwt 2 grid oinstall 6 Aug 10 18:37 racgevtf

Drwxrwxrwt 2 grid oinstall 6 Aug 10 18:37 racgmain

5) the $GRID_HOME/log/ and $ORACLE_HOME/log/ directories record log information corresponding to the srvctl, ocrdump, ocrconfig, and ocrcheck commands.

[grid@ora102 client] $pwd

/ u01/app/11.2.0/grid/log/ora102/client

[grid@ora102 client] $ll

Total 400

-rw-r--r-- 1 grid oinstall 1150 Nov 30 09:19 crsctl_grid.log

-rw-r--r-- 1 root root 23067 Nov 30 09:36 crsctl_root.log

-rw-r--r-- 1 root root 243Nov 30 09:18 crswrapexece.log

-rw-r--r-- 1 root root 279 Aug 10 18:51 css.log

-rw-r--r-- 1 grid oinstall 495 Nov 29 21:46 ocrcheck_6773.log

-rw-r- 1 root root 2228 Aug 10 18:39 ocrconfig_22491.log

-rw-rw-rw- 1 grid oinstall 3981 Aug 11 15:20 oifcfg.log

-rw-rw-rw- 1 grid oinstall 126999 Nov 30 15:36 olsnodes.log

[oracle@ora102 client] $pwd

/ u01/app/oracle/product/11.2.0/dbhome_1/log/ora102/client

Since no ocrdump has been executed, there is no related log

[oracle@ora102 client] $ll

Total 0

After executing ocrdump, the corresponding log will be generated in the corresponding directory.

[grid@ora102 client] $pwd

/ u01/app/11.2.0/grid/log/ora102/client

[grid@ora102 client] $ll ocrdump*

-rw-r--r-- 1 grid oinstall 2473 Nov 30 16:01 ocrdump_783.log

6) the location of the ALERT file in the cluster under $GRID_HOME/log/

[grid@ora102 ora102] $pwd

/ u01/app/11.2.0/grid/log/ora102

[grid@ora102 ora102] $tail-n 10 alertora102.log

2017-11-30 09For 34-19. 907:

[ohasd (12860)] CRS-2765:Resource 'ora.crsd' has failed on server' ora102'.

2017-11-30 09For 34-19. 908:

[ohasd (12860)] CRS-2771:Maximum restart attempts reached for resource 'ora.crsd'; will not restart.

2017-11-30 09For 34-19. 908:

[ohasd (12860)] CRS-2769:Unable to failover resource 'ora.crsd'.

2017-11-30 09For 36RV 39.500:

[crsd (15778)] CRS-1012:The OCR service started on node ora102.

2017-11-30 09For 36RV 39.832:

[crsd (15778)] CRS-1201:CRSD started on node ora102.

Note that the altert of the cluster differs from the alarm log of the asm instance. The latter is in

$ORACLE_BASE/diag/asm/+asm/+ASM2/trace path.

At this point, the study on "oracle cluster cluster-related log viewing method" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.