My Oracle Support Banner

ORA.CRF Resource Fails To Start When ROOTCRS.PL -POSTPATCH Is Executed (Doc ID 1997027.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 12.1]
Information in this document applies to any platform.


 Commands "opatchauto"  or " -postpatch" may fail to bring up the clusterware after applying a bundle patch:

root@racdb01:/export/home/oracle# opatchauto apply /u01/patches/19262534 -oh /u01/app/ -ocmrf /export/home/oracle/ocm.rsp
Applying patch(es) to "/u01/app/" ... Patch "/u01/ZIPs/patch/19262534/19262534" applied to "/u01/app/" with warning.
Starting CRS ... Failed <<<< command
Command "/u01/app/ -I/u01/app/ -I/u01/app/ /u01/app/ -postpatch" execution failed: Died at /u01/app/ line 880. <<<

 The CRSD log file (<orabase>diag/crs/<node>/crs/trace/crsd.trc) indicates that the CRSD daemon failed to connect to CRF resource to get the CHM host info:

2015-03-31 11:53:10.422174 : CRSPE:42: {1:20071:2} Getting CHM host info...
2015-03-31 11:53:10.486422 :GIPCXCPT:42: gipcSendSyncF [crfm_connect_timeout : crfm.c : 3265]: EXCEPTION[ ret gipcretConnectionInvalid (13) ] failed to send on endp 103fb8010 [00000000000009e8] { gipcEndpoint : localAddr 'ipc', remoteAddr 'ipc://sracnode1oraclepsatstdbsscanCRFM_SIPC', numPend 0,
numReady 0, numDone 0, numDead 0, numTransfer 0, objFlags 0x0, pidPeer 0, readyRef 0, ready 0, wobj 104ffc660, sendp 105036390 status 13flags  0x2008061a, flags-2 0x1, usrFlags 0x20 }, addr 0000000000000000, buf 104f26950, len 366, flags 0x0

2015-03-31 11:53:10.486443 : CRFM:42: crfm_connect_to: send fail(gipcret: 13)



 Executed -postpatch as part of the GI Home patching process


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.