My Oracle Support Banner

Opatchauto: Applying GIRU fails with error " OPATCHAUTO-68061" (Doc ID 2390188.1)

Last updated on NOVEMBER 03, 2021

Applies to:

Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Linux x86-64

Symptoms

Applying GIRU fails with error " OPATCHAUTO-68061"

Output of opatchauto apply:

# opatchauto apply /u01/app/patches/27100009

OPatchauto session is initiated at Tue Mar 27 23:12:27 2018

System initialization log file is $GRID_HOME/cfgtoollogs/opatchautodb/systemconfig2018-03-27_11-12-28PM.log.

Session log file is $GRID_HOME/cfgtoollogs/opatchauto/opatchauto2018-03-27_11-13-07PM.log
The id for this session is SA4W

Executing OPatch prereq operations to verify patch applicability on home $GRID_HOME

Executing OPatch prereq operations to verify patch applicability on home $DB_HOME
Patch applicability verified successfully on home /u01/app$DB_HOME

Patch applicability verified successfully on home $GRID_HOME

Verifying SQL patch applicability on home $DB_HOME
"/bin/sh -c 'cd $DB_HOME; ORACLE_HOME=$DB_HOME ORACLE
_SID=HDBLGS12 $DB_HOME/OPatch/datapatch -prereq -verbose'" command failed with error
s. Please refer to logs for more details. SQL changes, if any, can be analyzed by manually retrying the same comman
d.

SQL patch applicability verified successfully on home $DB_HOME

Preparing to bring down database service on home $DB_HOME
Successfully prepared home $DB_HOME to bring down database service

Bringing down CRS service on home $GRID_HOME
Prepatch operation log file location: $GRID_BASE/crsdata/node2/crsconfig/crspatch_node2_2018-03-27_11-16-05PM.log
CRS service brought down successfully on home $GRID_HOME

Performing prepatch operation on home $DB_HOME
Perpatch operation completed successfully on home $DB_HOME

Start applying binary patch on home $DB_HOME
Failed while applying binary patches on home $DB_HOME

[OPatchAutoBinaryAction]patch action failed, check log for more details. Failures:
Patch Target : node2->$DB_HOME Type[rac]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home:$DB_HOME, host: node2.
Command failed: $DB_HOME/OPatch/opatchauto apply /u01/app/patches/27100009 -oh $DB_HOME -target_type rac_database -binary -invPtrLoc $GRID_HOME/oraInst.loc
-jre /u01/app/12.2.0/grid/OPatch/jre -persistresult /u01/app/oracle/product/12.2.0/dbhome_1/OPatch/auto/dbsessionin
fo/sessionresult_node2_rac.ser -analyzedresult $DB_HOME/OPatch/auto/dbsessioninfo
/sessionresult_analyze_node2_rac.ser
Command failure output:
==Following patches FAILED in apply:

Patch: /u01/app/patches/27100009/27335416
Log: $DB_HOME/cfgtoollogs/opatchauto/core/opatch/opatch2018-03-27_23-17-21PM_1.log
Reason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException: Re-link fails on target "install_srvm".

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 Tue Mar 27 23:18:38 2018
Time taken to complete the session 6 minutes, 11 seconds

opatchauto failed with error code 42

Output of opatch log:

[2018/03/28 3:23:51] [WARNING] OUI-67200:Make failed to invoke "/usr/bin/make -f ins_srvm.mk install_srvm ORACLE_HOME=$DB_HOME"....
'/bin/sh: /usr/bin/gcc: No such file or directory
make: *** [$DB_HOME/rdbms/lib/config.o] Error 127
'
[2018/03/28 3:23:51] [INFO] Stack Description: java.lang.RuntimeException: /bin/sh: /usr/bin/gcc: No such file or directory
make: *** [$DB_HOME/rdbms/lib/config.o] Error 127
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.MakeAction.apply(MakeAction.java:534)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.OPatchSession.runMake(OPatchSession.java:781)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.OPatchSession.runMake(OPatchSession.java:723)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.MergedPatchObject.invokeConsolidatedMake(MergedPatchObject.java:1754)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.opatchutil.NApply.legacy_process(NApply.java:1454)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.opatchutil.NApply.legacy_process(NApply.java:359)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.opatchutil.NApply.process(NApply.java:341)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.opatchutil.OUSession.napply(OUSession.java:1104)
[2018/03/28 3:23:51] [INFO] StackTrace: sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[2018/03/28 3:23:51] [INFO] StackTrace: sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[2018/03/28 3:23:51] [INFO] StackTrace: sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[2018/03/28 3:23:51] [INFO] StackTrace: java.lang.reflect.Method.invoke(Method.java:498)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.UtilSession.process(UtilSession.java:352)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.OPatchSession.main(OPatchSession.java:3941)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.OPatchSDK.NApply(OPatchSDK.java:1124)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatch.opatchsdk.OPatchTarget.NApply(OPatchTarget.java:3772)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatchauto.core.binary.OPatchAutoBinary.patchPRsWithoutAnalyze(OPatchAutoBinary.java:1051)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatchauto.core.binary.OPatchAutoBinary.patchWithoutAnalyze(OPatchAutoBinary.java:999)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatchauto.core.binary.OPatchAutoBinary.applyWithoutAnalyze(OPatchAutoBinary.java:931)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatchauto.core.OPatchAutoCore.runOPatchAutoBinary(OPatchAutoCore.java:195)
[2018/03/28 3:23:51] [INFO] StackTrace: oracle.opatchauto.core.OPatchAutoCore.main(OPatchAutoCore.java:70)

 

Cause

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
Symptoms
Cause
Solution
References


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