GIPC Startup Failing With "gipcdsMemorySearchKey: list empty, key gipc_round_trip_time not found, ret gipcretFail "
(Doc ID 2901156.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 21.7 [Release 12.1 to 21.0]Information in this document applies to any platform.
Symptoms
GIPC unable to start on one of nodes in a two nodes cluster .
alert.log
=========
2022-09-29 00:06:45.397 [GIPCD(158548)]CRS-7509: The 'worker thread' of Oracle Grid Interprocess communication (GIPC) has been non-responsive for '27384480' milliseconds. Additional diagnostics: process name: 'gipcd'.
2022-09-29 00:06:58.610 [GIPCD(158548)]CRS-7509: The 'worker thread' of Oracle Grid Interprocess communication (GIPC) has been non-responsive for '27397690' milliseconds. Additional diagnostics: process name: 'gipcd'.
GIPC process is looping with below errors
gipcd.trc
===============================
*** TRACE CONTINUED FROM FILE /u01/app/grid_base/diag/crs/<Hostname>/crs/trace/gipcd_77.trc ***
2022-09-29 06:30:36.203 :GIPCDCLT:4262950656: gipcdClientCheckHaThreadHealth: Alert! GIPCHA worker thread health of gipcd is not good, time lapsed since last worker HB msg 50415290, time lased since last recv msg 0
2022-09-29 06:30:47.213 :GIPCHTHR:4250298112: gipchaDaemonWork: DaemonThread heart beat, time interval since last heartBeat 30830 loopCount 33
2022-09-29 06:30:49.415 :GIPCDCLT:4262950656: gipcdClientCheckHaThreadHealth: Alert! GIPCHA worker thread health of gipcd is not good, time lapsed since last worker HB msg 50428500, time lased since last recv msg 0
2022-09-29 06:30:53.002 :GIPCXCPT:4258748160: gipcdsMemorySearchKey: list empty, key gipc_round_trip_time not found, ret gipcretFail (1)
2022-09-29 06:30:53.002 :GIPCDMON:4258748160: gipcdMonitorPublishDiags: failed to open the RTT key, ds_ret 1
2022-09-29 06:31:02.629 :GIPCDCLT:4262950656: gipcdClientCheckHaThreadHealth: Alert! GIPCHA worker thread health of gipcd is not good, time lapsed since last worker HB msg 50441710, time lased since last recv msg 0
2022-09-29 06:31:15.841 :GIPCDCLT:4262950656: gipcdClientCheckHaThreadHealth: Alert! GIPCHA worker thread health of gipcd is not good, time lapsed since last worker HB msg 50454930, time lased since last recv msg 0
2022-09-29 06:31:18.044 :GIPCHTHR:4250298112: gipchaDaemonWork: DaemonThread heart beat, time interval since last heartBeat 30830 loopCount 33
2022-09-29 06:31:25.628 :GIPCXCPT:4258748160: gipcdsMemorySearchKey: list empty, key gipc_round_trip_time not found, ret gipcretFail (1)
Changes
GIPC unable to start on one of nodes after reboot in a two node cluster.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |