ODA 18.104.22.168 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.
- Upgrading to ODA software version : 22.214.171.124.0
- GI patch failure on node
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 : 126.96.36.199.0
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 188.8.131.52.0 --server <--local> (per REF) below
This is the first error of this nature where we see OCW at the .12 or 184.108.40.206.170811
MISMATCH of CRS and OCW
[grid@]$ cd /u01/app/220.127.116.11/grid/OPatch
[grid@ OPatch]$ ./opatch lspatches
26609945;OCW Patch Set Update : 18.104.22.168.170814 (26609945) <<<<<<< 170814
25885938;ACFS Interim patch for 25885938
25171037;Database Patch Set Update : 22.214.171.124.170418 (25171037) <<< 170418
21436941;WLM Patch Set Update: 126.96.36.199.5 (21436941)
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