patch_locked

OPATCH_JAVA_ERROR With "Can not lock OUI inventory (READ/WRITE Level)" in Logs [ID 1264274.1]

In this Document

Symptoms

Changes

Cause

Solution

References

---

Applies to:

Oracle Fusion Middleware - Version 10.1.2.3.0 to 10.1.4.3.0 [Release AS10gR2 to AS10gR3]
Information in this document applies to any platform.
Checked for relevance on 12-Sep-2012

Symptoms

This problem has been seen during an Identity Management 10g (10.1.4) installation on Microsoft Windows 2008 R2. The problem is actually with the OPatch utility while applying a one-off patch to a given Oracler home. This does occur 'automatically' when installing Identity Management 10g 10.1.4. The solution would apply to any Oracle Application Server 10g installation where OPatch is failing with the following commands and resulting errors:

%ORACLE_HOME%\OPatch apply
%ORACLE_HOME%\OPatch lsinventory

OPATCH_JAVA_ERROR : An exception of type "OPatchException" has occurred:
Can not get a list of inventory on this home.

ERROR: OPatch failed because of Inventory problem.
OPatch returns with error code = 100

When looking at the ORACLE_HOME\.patch_storage\<patch_directory>, the following is found:

java.lang.NullPointerException
at oracle.sysman.oii.oiix.OiixPathOps.concatPath(OiixPathOps.java:551)
at oracle.sysman.oii.oiic.OiicStandardInventorySession.updateProperties(OiicStandardInventorySession.java:401)
at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:243)
at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:218)
at oracle.sysman.oii.oiic.OiicStandardInventorySession.initSession(OiicStandardInventorySession.java:167)
at opatch.O2O.setupSession(O2O.java:535)
at opatch.O2O.setupInventory(O2O.java:597)
at opatch.O2O.setupInventoryThenRAC(O2O.java:1109)
at opatch.LsInventory.main(LsInventory.java:195)
LsInventory: OPatch Exception while accessing O2O


OPATCH_JAVA_ERROR : An exception of type "OPatchException" has occurred:
OPatch Exception: Can not lock OUI inventory (READ/WRITE Level)
An exception occurs
null
Can not lock OUI inventory (READ/WRITE Level)
An exception occurs
null
Can not lock OUI inventory (READ/WRITE Level)
An exception occurs
null
Can not lock OUI inventory (READ/WRITE Level)
An exception occurs
null
Can not lock OUI inventory (READ/WRITE Level)
An exception occurs
null
Can not lock OUI inventory (READ/WRITE Level)
An exception occurs
null
Can not lock OUI inventory (READ/WRITE Level)
An exception occurs
null
Can not lock OUI inventory (READ/WRITE Level)
An exception occurs
null
Can not lock OUI inventory (READ/WRITE Level)
An exception occurs
null
Can not lock OUI inventory (READ/WRITE Level)
An exception occurs
null

Changes

While this may happen with any patch installation for different reasons, if you are installing Identity Management 10g (10.1.4), you should be aware that this version is now past Premier Support and not eligible for new fixes. On newer platforms, there was a previous post-release certification, but there may be more issues without any resolution.

Reference:

Note 1290868.1 Error Correction Support Dates for Oracle Application Server 10g (10.1.2, 10.1.3, 10.1.4)

Note 465847.1 Oracle Identity Management 10g (10.1.4.0.1) Release Notes Addendum
  - Includes Microsoft Windows Vista, 2008 R1, 2008 R2, Linux Red Hat 5 and SuSE 10

Cause

There are different reasons for the error including processes running or a previously failed installation attempt which locked the inventory. In some cases, the root cause of such failures is because of a required update in the JRE installed by the OUI, which is used by the OPatch utility.

Solution

1. With this error, it is important to ensure there isn't a Oracle Universal Installer (OUI) or OPatch session running on the machine accessing the inventory, as this would lock the inventory from future updating. In normal cases, you are applying one-off patches with OPatch when there are no other processes running on the machine. If you applying this with an OUI (Installer) session is in-progress, the Inventory will be locked. If you have actually closed the Installer, you will want to stop any OUI processes holding a lock on the Inventory.

In Windows you can use the command:
> tasklist | findstr /R "setup.exe"
OR
> tasklist | findstr /R "oui.exe"
OR
> tasklist | findstr /R "javaw.exe"

2. If there was a failed installation, even with the session closed, there may still be a lock on the inventory and the following locations should be checked for this indication. If present, the following files can be safely removed.

C:\Program Files\Oracle\inventory\locks\writer.lock
and/or
ORACLE_HOME\.patch_storage\patch_locked

3. If none of the above are applicable then download and install Patch 6640838, which will update the OUI (installer) files to version 10.1.0.6.0 to correct a problem in the JRE installed on the system and used by the OUI and OPatch utilities. Apply this according to the readme and/or Note 565374.1. Note that this update is applicable to all 10.1.2, 10.1.3, and 10.1.4 where the 10.1 OUI has been used to install the Oracle Application Server or Identity Management 10g.

If this was an installation and you skipped the OC4J Instance Configuration Assistant before closing the Installer, note there will be a ORACLE_HOME/cfgtoollogs/configToolCommands created at the end. This is for running the failed Configuration Assistants later.

4. After applying Patch 6640838, "opatch lsinventory" commands should work and you can proceed to apply the patch originally intended.

5. If needing to re-run a failed Configuration Assistant, retry the OC4J Instance Configuration Assistant by running the generated script file named configtoolcmds.pl located in the ORACLE_HOME\bin directory. The configtoolcmds.pl script is generated after you exit the installer.

Note on Windows, you will need to rename ORACLE_HOME\cfgtoollogs\ configToolCommands to ORACLE_HOME\cfgtoollogs\ configToolCommands.bat before running ORACLE_HOME\bin\configtoolcmds.pl. More information on this is in the 10.1.4.0.1 Installation Guide, Appendix E.