Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

OPatch failed with error code = 73

DelmonteMay 24 2012 — edited May 25 2012
- O/S: Windows Server 2008 R2 64 bits
- Oracle RAC Database: Oracle 11.2.0.2
- 02 nodes: NodeA and NodeB.
- Each node has a local Windows account named "adminrac", which belongs to Administrator and Ora_dba groups.
- On both Windows Servers 2008, UAC was inhabilitated, so user "adminrac" can create and modify any file in any folder.

Problem:
On NodeA, I have succesfully applied patch p12714463_112020_MSWIN-x86-64. Now I try t do it on NodeB, but get errors.

First, on NodeA and NodeB I updated opatch to version: 11.2.0.1.9. I downloaded and unzipped "p6880880_112000_MSWIN-x86-64.zip" at ORACLE_HOME:
C:\app\bd\product\11.2.0\dbhome_1\OPatch

Secondly, on NodeA I checked Oracle inventory with "opatch lsinventory" and was OK. Then I succesfully applied patch p12714463_112020_MSWIN-x86-64.

Now, on NodeB, I try to apply same patch and start to check Oracle inventory:

C:\app\bd\product\11.2.0\dbhome_1\OPatch> opatch lsinventory

Results:

---- Start of Message -----
C:\app\bd\product\11.2.0\dbhome_1\OPatch>opatch lsinventory

Oracle Interim Patch Installer version 11.2.0.1.9
Copyright (c) 2011, Oracle Corporation. All rights reserved.


Oracle Home : C:\app\bd\product\11.2.0\dbhome_1
Central Inventory : C:\Program Files\Oracle\Inventory
from : n/a
OPatch version : 11.2.0.1.9
OUI version : 11.2.0.2.0
Log file location : C:\app\bd\product\11.2.0\dbhome_1\cfgtoollogs\opatch\opatch2
012-05-24_13-51-28PM.log



Inventory load failed... OPatch cannot load inventory for the given Oracle Home.


LsInventorySession failed: Unable to create patchObject

OPatch failed with error code = 73
---- End of Message -----

What should I do to correct this error?
I already copied "C:\Program Files\Oracle\Inventory" from NodeA to NodeB and reboot NodeB, but appears same error.
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 22 2012
Added on May 24 2012
2 comments
5,246 views