opatch auto failed with error message OPatch failed with error code 73 and OUI-67124 (Doc ID 1283964.1)

Last updated on JUNE 06, 2017

Applies to:

Oracle Exadata Hardware - Version 11.2.0.2 to 11.2.0.3 [Release 11.2]
Oracle Universal Installer - Version 11.2.0.2 to 11.2.0.3 [Release 11.2]
Oracle Database - Enterprise Edition - Version 11.2.0.4 to 11.2.0.4 [Release 11.2]
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Information in this document applies to any platform.
***Checked for relevance on 09-Dec-2013***

Symptoms

IMPORTANT!!!!!!   This could happen with any Bundle Patch version, any binary that is replaced as part of the patch and on any oracle home

UtilSession failed: ApplySession failed in system modification phase... 'ApplySession::apply failed: Copy failed from '/tmp/patches/BP3/10387939/10626132/files/bin/diskmon.bin' to '/u01/app/11.2.0/grid/bin/diskmon.bin'...
'
--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1) OUI-67124:Copy failed from '/tmp/patches/BP3/10387939/10626132/files/bin/diskmon.bin' to '/u01/app/11.2.0/grid/bin/diskmon.bin'...

2) OUI-67124:ApplySession failed in system modification phase... 'ApplySession::apply failed: Copy failed from '/tmp/patches/BP3/10387939/10626132/files/bin/diskmon.bin' to '/u01/app/11.2.0/grid/bin/diskmon.bin'...
'
3) OUI-67124:
NApply was not able to restore the home. Please invoke the following scripts:
- restore.[sh,bat]
- make.txt (Unix only)
to restore the ORACLE_HOME. They are located under
"/u01/app/11.2.0/grid/.patch_storage/NApply/2011-01-13_10-31-58AM"
 
 
 
  •  This is an example AFTER applying a bundle patch to 11.2.0.3 GI.  The CRS will fail to start:
# cd /u01/app/11.2.0.3/grid/bin
# ./crsctl check crs
CRS-4638: Oracle High Availability Services is online

Errors :-
CRS-4535: Cannot communicate with Cluster Ready Services
CRS-4529: Cluster Synchronization Services is online
CRS-4534: Cannot communicate with Event Manager
#
# ./crsctl start crs
CRS-4640: Oracle High Availability Services is already active
CRS-4000: Command Start failed, or completed with errors.
#

Cause

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 hundreds of Community platforms