Opatch fails with Lock file error

(Doc ID 257800.1)

Last updated on JUNE 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.1 to 11.2.0.3 [Release 9.2 to 11.2]
Information in this document applies to any platform.

Symptoms

 While applying Oracle Patch, Opatch reports the below error :

OUI-67064:OPatchSession cannot load inventory for the given Oracle Home /ora01/app/oracbr/product/11.2.0/dbhome_1. Possible causes are:
                               No read or write permission to ORACLE_HOME/.patch_storage
                               Central Inventory is locked by another OUI instance
                               No read permission to Central Inventory
                               The lock file exists in ORACLE_HOME/.patch_storage
                               The Oracle Home does not exist in Central Inventory
[Dec 20, 2013 8:29:05 AM]    OUI-67073:UtilSession failed: Lock file left by a different patch, OPatch will not try re-using the lock file.

 

Note : It has been noticed that opatch lock error also leads to the error "OPatch failed with error code 255"

 

In earlier releases, error used to look like:

Problems with the lock file
Lock file exists, details are:
Interim Patch is holding the lock from this patch xxxxxx,
probably due to previous unsuccessful operation

ERROR: OPatch failed during pre-reqs check

 

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