Patch Install Hangs: 'Unable to lock Central Inventory', OUI-10022
(Doc ID 2122118.1)
Last updated on DECEMBER 20, 2022
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Database Cloud Schema 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
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Encountering this error while attempting to apply a patch (PSU 184.108.40.206.8 hangs during 'opatch napply ...')
As we will see later below, the culprit was not the PSU patch or any steps missed and required before applying the patch.
Already checked the following, but still same error:
* <Note:257800.1> does not apply here because no entries are given like: OUI-67073:UtilSession failed: Lock file left by a different patch, OPatch will not try re-using the lock file.
Also, we see NO 'patch_lock' file under $ORACLE_HOME/.patch_storage
* There are no other OUI or opatch process running on the server or process locking the central inventory:
Checked via: 'ps -ef|grep -i runinstaller', 'ps -eg|grep -i opatch', '/sbin/fuser <path_to_oraInventory>'
* The owner:group and permissions for the central inventory are proper (ie, grid:oinstall 770)
* The gi_home exists in the central inventory file (<inventory_loc>/ContentsXML/inventory.xml)
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