SYMPTOMS
When applying 19c GI JULY 2020 RU ( 19.8.0.0), opatchauto failed with following errors:
#opatchauto apply /tmp/31305339/ ... .. . Patch: /tmp/31305339/31281355 Log: Reason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException: Unable to create patchObject Possible causes are: ORACLE_HOME/inventory/oneoffs/31281355 is corrupted. PatchObject constructor: Input file "/u01/app/19.0.0/grid/inventory/oneoffs/31281355/etc/config/actions" or "/u01/app/19.0.0/grid/inventory/oneoffs/31281355/etc/config/inventory" does not exist. After fixing the cause of failure Run opatchauto resume ] OPATCHAUTO-68061: The orchestration engine failed. OPATCHAUTO-68061: The orchestration engine failed with return code 1 OPATCHAUTO-68061: Check the log for more details. OPatchAuto failed. OPatchauto session completed at Mon Aug 3 21:06:44 2020 Time taken to complete the session 0 minute, 35 seconds opatchauto failed with error code 42
Subscribe to get access
Read more of this content when you subscribe today.
Make DBA Life Easy 
Hi, if the patch 31281355 is not found on the other node 2. Will it not cause a problem for the missing patch in the racnode2 with node 1? If so, should the patch be installed manually, right?
LikeLike
sure, always keep the same patches on all nodes. otherwise CRS won’t start up properly , or the following issue might occur for future operations.
https://dbalifeeasy.com/2018/08/20/ora-15137-the-asm-cluster-is-in-rolling-patch-state/
LikeLike
Hi dbalifeeasy,
Looks it’s not the right way to do it ,,
added my findings in https://www.jcraju.com/2020/10/gi-july-2020-ru-1980031305339-patching.html
LikeLike
thanks Jay for your information. You are right. I have just updated and linked another blog to cover the mentioned issue. And also linked yours as great reference if you don’t mind.
LikeLike