My Oracle Support Banner

ODA GI Patch Fails with Timeout After CRS Fails to Start Within 6+ Minutes (Doc ID 2375032.1)

Last updated on AUGUST 20, 2018

Applies to:

Oracle Database Appliance X5-2 - Version All Versions and later
Information in this document applies to any platform.



The source of the problem can be reproduced by manually
by confirming the time it takes after a stop and restarting of CRS

Restarting CRS manually work fine, however a manual CRS startup may take 6+ minutes.

Upgrading to which ODA software version :

Q Have you executed the cleanup job and retried the GI patch again.
A Yes when "oakcli show version -detail "showed that the GI was not patched,
I executed the cleanup and retried the patched before I opened the SR.

/opt/oracle/oak/bin/oakcli update -patch --server <--local> (per REF) below

This is the first error of this nature where we see OCW at the .12 or

[grid@]$ cd /u01/app/
[grid@ OPatch]$ ./opatch lspatches

26609945;OCW Patch Set Update : (26609945) <<<<<<< 170814
25885938;ACFS Interim patch for 25885938

25171037;Database Patch Set Update : (25171037) <<< 170418
21436941;WLM Patch Set Update: (21436941)
OPatch succeeded.




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.