Saturday, March 12, 2016

OPatch Failed with lock file exists in ORACLE_HOME

Retrying to patch apply after a failed attempted resulted in following error "Lock file left by a different patch, OPatch will not try re-using the lock file"

Solutions: 
1. Look in the oraInventory and see if there is lock directory if so remove it. 
/apps/oracle/oraInventory/locks

2. Inside the .patch_storage there will be another file call "patch_locked" which basically has the information for which patch the lock is taken for. Removing "patch_locked" file resolved the issue.
/apps/soa/fmw11.1.1.7/Oracle_SOA/.patch_storage/patch_locked


.
Error Trace:
/apps/soa/fmw/oracle_common/OPatch/opatch apply
Oracle Interim Patch Installer version 11.1.0.9.9
Copyright (c) 2012, Oracle Corporation.  All rights reserved.

Verifying environment and performing prerequisite checks...
[ Error during Oracle Home discovery Phase]. Detail: OPatchSession cannot load inventory for the given Oracle Home /opt/app/11.2.0/grid4. Possible causes are:
   No read or write permission to ORACLE_HOME/.patch_storage
   Central Inventory is locked by another OUI instance
   No read permission to Central Inventory
   The lock file exists in ORACLE_HOME/.patch_storage
   The Oracle Home does not exist in Central Inventory

No comments:

Post a Comment