OPatch lsinventory or Apply New Patch With Opatchauto Fails With Error "Unable to create patchObject" Inventory Corrupted (Doc ID 2286025.1)

Last updated on JULY 21, 2017

Applies to:

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.

Symptoms

Applying patch 25434018 (Combo of 12.1.0.2.170418 OJVM PSU and 12.1.0.2.170418 GI PSU (Apr 2017)) in 2 Node RAC Cluster environment

Node 1 was successful.

Node 2 fails with below errors (java.lang.NullPointerException).

Patch was applied using opatchauto method.

Node 2 (opatchauto -analyze) fails with corrupt inventory for db home.

Following patches FAILED in analysis for apply:

Patch: /u01/oracle/home/oracle/dba/25434018/25434003/25171037

Log:
Reason: Failed during listing in Analysis: java.lang.Exception: oracle.opatch.opatchsdk.OPatchException: Unable to create patchObject
Possible causes are:
ORACLE_HOME/inventory/oneoffs/25171037 is corrupted. java.lang.NullPointerException

 

"opatch lsinventory" on Node 2 Database Home fails :

 

Inventory load failed... OPatch cannot load inventory for the given Oracle Home.

LsInventorySession failed: Unable to create patchObject
Possible causes are:
ORACLE_HOME/inventory/oneoffs/25171037 is corrupted. PatchObject constructor: Input file "/u01/app/oracle/product/12.1.0/db_1/inventory/oneoffs/25171037/etc/config/actions" or "/u01/app/oracle/product/12.1.0/db_1/inventory/oneoffs/25171037/etc/config/inventory" does not exist.

OPatch failed with error code 73

 

Changes

Applied Grid / Database and OJVM patch in that order on node 1 successfully.

OJVM patch got propagated to Node 2 DB home successfully.

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