After upgrading to Oracle 220.127.116.11.0, it was a fine moment to also apply the latests PSU, while working at it anyway.
However, after running all the prerequisites and checks who where all claiming success, the patch did not want to apply at all. Following the log trail is fairly easy to do, and soon the underlying failing issue was found:
Copyright (c) 2013, Oracle Corporation. All rights reserved. Oracle Home : /oracle/18.104.22.168/grid Central Inventory : /home/oracle/oraInventory from : /oracle/22.214.171.124/grid/oraInst.loc OPatch version : 126.96.36.199.6 OUI version : 188.8.131.52.0 Log file location : /oracle/184.108.40.206/grid/cfgtoollogs/opatch/opatch2014-11-19_13-53-38PM_1.log Verifying environment and performing prerequisite checks... Prerequisite check "CheckActiveFilesAndExecutables" failed. The details are: Following executables are active : /oracle/220.127.116.11/grid/lib/libclntsh.so.11.1 UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed. Log file location: /oracle/18.104.22.168/grid/cfgtoollogs/opatch/opatch2014-11-19_13-53-38PM_1.log OPatch failed with error code 73
This led to some steps to take into account BEFORE attempting the patch:
- The OPatch version is 22.214.171.124.6 in BOTH the ORACLE DB HOME, as well as in the
- Set the ORACLE_BASE variable.
- Double check if the file: /oracle/126.96.36.199/grid/crs/install/crsconfig_params
actually contains the correct base.
- If the patch keeps failing: make sure all connections to the database are gone, NO SQLPLUS sessions should be active. Neither any Listeners. One might even shutdown the database.
The file /oracle/188.8.131.52/grid/lib/libclntsh.so.11.1 should NOT be in use when the patch wants to roll..if in use, the patch will fail.
To find the process(es) holding a lock on this file, run the following command:
$ sudo /sbin/fuser /oracle/184.108.40.206/grid/lib/libclntsh.so.11.1
If anything returns, it is the process number holding the lock. ‘ps -ef |grep
‘ (minus the ‘m’) and the culprit becomes visible.
The RAC processes will be shutdown by the OPatch process, however any sessions will not.
Hope this helps! Happy patching (if such thing is possible 🙂 )