What Are The Reasons For "OPatch failed with error code = 73"?
(Doc ID 2671436.1)
Last updated on DECEMBER 16, 2023
Applies to:
Oracle WebLogic Server - Version 12.1.2.0.0 and laterInformation in this document applies to any platform.
Purpose
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.
Scope
This document is intended for WebLogic administrators who need to apply a one-off or PSU patch using OPatch.
Details
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
| Purpose |
| Scope |
| Details |
| On Windows: |
| Error "ApplySession::apply failed: oracle.glcm.opatch.common.api.install.HomeOperationsException: A failure occurred while processing patch: nnnnnn" |
| Error "ApplySession::apply failed: Error: "com.oracle.cie.common.xmldiff.XmlDiffException" |
| 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? |
| References |