Opatch fails with Lock file error
(Doc ID 257800.1)
Last updated on SEPTEMBER 24, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 9.2 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
While applying Oracle Patch, Opatch reports the below error :
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
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!