Opatch PSU October 2014 Fails..Or “Why Did I Try This Again?”

After upgrading to Oracle 11.2.0.4.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/11.2.0.4/grid
Central Inventory : /home/oracle/oraInventory
from : /oracle/11.2.0.4/grid/oraInst.loc
OPatch version : 11.2.0.3.6
OUI version : 11.2.0.4.0
Log file location : /oracle/11.2.0.4/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/11.2.0.4/grid/lib/libclntsh.so.11.1
UtilSession failed: Prerequisite check "CheckActiveFilesAndExecutables" failed.
Log file location: /oracle/11.2.0.4/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 11.2.0.3.6 in BOTH the ORACLE DB HOME, as well as in the
    GRID HOME.
  •  Set the ORACLE_BASE variable.
  •  Double check if the file: /oracle/11.2.0.4/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.

Why?

The file /oracle/11.2.0.4/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/11.2.0.4/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 🙂 )

Advertisements

About GemsOfProgramming

Beeing a previously enthusiastic Java programmer, I rolled into the Oracle Database Administration world. It turned out I got a knack for this, and since approx. 2000 I'm a full time DBA. My experiences touches lot of Oracle products like Forms and Reports 9/10, JDAPI, Application Server, Weblogic Fusion and of course: Oracle Enterprise Databases, JavaFX, Swing and other Java components.
This entry was posted in Databases, Technical Stuff, upgrade. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s