What Are The Reasons For "OPatch failed with error code = 73"?
(Doc ID 2671436.1)
Last updated on OCTOBER 23, 2020
Applies to:Oracle WebLogic Server - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
This document lists the most common reasons for "OPatch failed with error code = 73" error while using OPatch. "Error code 73" is a very generic error. Check the previous log messages for more information on the OPatch failure.
This document is intended for WebLogic administrators who need to apply a one-off or PSU patch using OPatch.
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
|Error "ApplySession::apply failed: oracle.glcm.opatch.common.api.install.HomeOperationsException: A failure occurred while processing patch: nnnnnn"|
|Error "ApplySession::apply failed: oracle.glcm.opatch.common.api.install.HomeOperationsException"|
|Error "File Name Or Extension Is Too Long"|
|Error ""File does not exist or is not readable"|
|On All Platforms:|
|Error "Conflicts/Supersets" or "error code 73"|
|Error "lsinventory does not exist error"|
|Error 'ApplySession::apply failed: oracle.sysman.nextgen.NextGenPatchingException: Failed to process patch 27342434'|
|Error "[SEVERE] OUI-67073:UtilSession failed: ApplySession failed in system modification phase"|
|Error "utilSession failed: com.oracle.cie.nextgen.common.utils.Util.getCanonicalPath"|
|Error: Prerequisite "Check OPatchMinimumVersion" failed|
|Error "Inventory load failed... OPatch cannot load inventory for the given Oracle Home"|
|Error "fuser could not be located"|
|Error "Patch nnnnn requires component(s) that are not installed in OracleHome"|
|How to debug OPatch?|