Last updated on SEPTEMBER 05, 2010
Applies to:Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 18.104.22.168 - Release: 10.2 to 11.1
Oracle Server Enterprise Edition - Version: 10.2.0.1 to 22.214.171.124
10gR2, 11gR1 Clusterware resources can crash when CheckResource fails with error 139 (SIGSEGV).
You may find many Clusterware resources (like VIP, Listener, Instances, Services, etc) status as OFFLINE when looking at output of command: crs_stat -t.
Starting them all will work fine until this issue is hit again.
2009-01-22 08:43:14.670: [ OCRSRV]th_select_answer: Failure in answer. clsc ret 
2009-01-22 08:43:14.675: [ CRSAPP] CheckResource error for ora.node1.vip error code = 139
2009-01-22 08:43:14.682: [ CRSRES] In stateChanged, ora.node1.vip target is ONLINE
2009-01-22 08:43:14.701: [ CRSRES] ora.node1.vip on node1 went OFFLINE unexpectedly
The ora.node1.vip.log does not have messages from problem time.
You may find a core file generated by racgmain in <CRS_HOME>/racg/racgmain .
node1:/u01/oracle/app/oracle/product/10.2.0/crs/lognode1/racg/racgmain# ls -ltr
-rw------- 1 root sys 7488128 Jan 22 08:43 core
node1:/u01/oracle/app/oracle/product/10.2.0/crs/log/node1/racg/racgmain# file core
core: ELF-64 core file - IA64 from 'racgmain' - received SIGSEGV
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms