Last updated on OCTOBER 01, 2017
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Information in this document applies to any platform.
Encountering this error while attempting to apply a patch (PSU 18.104.22.168.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)
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