While Applying a WebCenter Content Patch the Following Error Occurs: OPatch failed with error code = 73 (Doc ID 2005738.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle WebCenter Content - Version 11.1.1.8.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.1.8.0 version, Content Server

When attempting to apply WebCenter Content (WCC) patch# 20503268 on a Windows Server 2012 R2, the following error occurs,


ERROR
-----------------------
OPatch detects the Middleware Home as "E:\Oracle\Middleware"

Failed to load the patch object. Possible causes are:

  The specified path is not an interim Patch shiphome
  Meta-data files are missing from the patch area
  Patch location = E:\Oracle\Middleware\patch_20503268
  Details = PatchObject constructor: Input file "E:\Oracle\Middleware\patch_20503268\etc\config\actions" or "E:\Oracle\Middleware\patch_20503268\etc\config\inventory" does not exist.

OPatch failed: PatchObject constructor: Input file "E:\Oracle\Middleware\patch_20503268\etc\config\actions" or "E:\Oracle\Middleware\patch_20503268\etc\config\inventory" does not exist.
Log file location: E:\Oracle\Middleware\Oracle_ECM1\cfgtoollogs\opatch\opatch2015-04-27_11-58-47AM_1.log

OPatch failed with error code = 73


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Set ORACLE_HOME as E:\Oracle\Middleware
2. Navigate to directory where unzipped patch is located
3. Run %ORACLE_HOME%/OPatch/opatch apply

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot begin UAT testing as the environment is not up to the patchlevel needed for testing to begin. This delay is causing complaints by the users and client.

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