aix OPATH ISSUE
issue 1:
In this Document
APPLIES TO:Oracle Service Bus - Version 11.1.1.7.0 and laterInformation in this document applies to any platform. SYMPTOMSWhen checking applied patch with opatch lsinventory, this issue occurs E:\app\fmw\osb\11.1.1.7\Oracle_OSB1\OPatch>opatch lsinventory
Invoking OPatch 11.1.0.8.2 Oracle Interim Patch Installer version 11.1.0.8.2 Oracle Home : e:\app\fmw\osb\11.1.1.7\Oracle_OSB1 Patch history file: e:\app\fmw\osb\11.1.1.7\Oracle_OSB1\cfgtoollogs\opatch\opatch_history.txt OPatch detects the Middleware Home as "E:\app\fmw\osb\11.1.1.7" OPatch cannot find a valid oraInst.loc file to locate Central Inventory. OPatch failed with error code = 104 CHANGESThis environment is not installed from OSB binary installation media, instead it's directly copied from another working OS. CAUSECentral Inventory Pointer File is missing, generally they are located in: For Solaris: /var/opt/oracle/oraInst.loc
For Linux: /etc/oraInst.loc For Windows this pointer is located in the registry key: \\HKEY_LOCAL_MACHINE\\Software\Oracle\inst_loc. In working environment, following Windows Register can be found: Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE] SOLUTIONDirectly adding this entry in Windows Registry, or export from working environment and import. For Linux/Unix like OS, verify if the ORACLE_HOME/oraInst.loc is present. If yes then execute opatch lsinventory with the option -invPtrLoc as: opatch lsinventory -invPtrLoc $ORACLE_HOME/oraInst.loc. Or if no central inventory location pointer file /etc/oraInst.loc exist, just copy the file $ORACLE_HOME/oraInst.loc to /etc (chmod o+r /etc/oraInst.loc with root) and then execute opatch lsinventory. |
The command "opatch lsinventory" fails with the following errors
Oracle Interim Patch Installer version 10.2.0.4.3
Copyright (c) 2007, Oracle Corporation. All rights reserved.
Oracle Home : /usr03/PROD/db/tech_st/10.2.0
Central Inventory : /var/opt/oracle/oraInventory
from : /var/opt/oracle/oraInst.loc
OPatch version : 10.2.0.4.3
OUI version : 10.2.0.4.0
OUI location : /usr03/PROD/db/tech_st/10.2.0/oui
Log file location : /usr03/PROD/db/tech_st/10.2.0/cfgtoollogs/opatch/opatch2009-07-16_19-19-22PM.log
List of Homes on this system:
Home name= UPG_DB__usr06_oracle_UPG_db_tech_st_10_2_0, Location=
"/usr06/oracle/UPG/db/tech_st/10.2.0/"
Home name= APPSIAS_UPG, Location= "/usr05/upgora/iAS"
Home name= ORAHOME_TEST, Location= "/usr04/test/testdb/9.2.0"
Home name= APPSDB_TEST, Location= "/usr05/testdb/9.2.0"
Home name= APPSIAS_TEST, Location= "/usr05/testora/iAS"
Home name= APPSDB_UPG, Location= "/usr05/proddb/9.2.0"
Inventory load failed... OPatch cannot load inventory for the given Oracle Home.
Possible causes are:
Oracle Home dir. path does not exist in Central Inventory
Oracle Home is a symbolic link
Oracle Home inventory is corrupted
LsInventorySession failed: OracleHomeInventory gets null oracleHomeInfo
OPatch failed with error code 73
CAUSE
ORACLE_HOME '/usr03/PROD/db/tech_st/10.2.0' is not registered in the Central Inventory (i.e oraInventory)
The error message shows that the following ORACLE_HOME's are registered:
Home name= UPG_DB__usr06_oracle_UPG_db_tech_st_10_2_0, Location=
"/usr06/oracle/UPG/db/tech_st/10.2.0/"
Home name= APPSIAS_UPG, Location= "/usr05/upgora/iAS"
Home name= ORAHOME_TEST, Location= "/usr04/test/testdb/9.2.0"
Home name= APPSDB_TEST, Location= "/usr05/testdb/9.2.0"
Home name= APPSIAS_TEST, Location= "/usr05/testora/iAS"
Home name= APPSDB_UPG, Location= "/usr05/proddb/9.2.0"
There is no information found for OracleHome '/usr03/PROD/db/tech_st/10.2.0' and so OPatch fails to load/list details of the OracleHome.
SOLUTION
To implement the solution, please execute the following steps:
1. Backup the existing oraInventory.(Central Inventory : /var/opt/oracle/oraInventory)
2. Register/Attach the OracleHome information to the existing Central Inventory using following command
- For OracleHome version 10.2.0.2 or higher :
% ./attachHome.sh
or
ORACLE_HOME=$ORACLE_HOME \
ORACLE_HOME_NAME="<Name_Of_The_Oracle_Home>"
- For OracleHome version 10.1.0.2 to 10.2.0.1:
% ./runInstaller -silent -attachHome \
ORACLE_HOME=$ORACLE_HOME \
ORACLE_HOME_NAME=<Name_Of_The_Oracle_Home>
Note : Please replace <Name_Of_The_Oracle_Home> with the name that you want to give this OracleHome.
'-attachHome' operation does not require any database downtime.
'-attachHome' operation does not work for Oracle Database Home versions 9.2.0.x or below.
For 9.2.0.x, incase central inventory is missing/corrupted OR OracleHome information is missing from existing central inventory, then only available options are
- restore the central inventory from last known good backup
OR
- reinstall the OracleHome
3. Now use OPatch command to check this OracleHome details
- following command should display all OracleHomes registered in the Central Inventory. Which should include your OracleHome as one of the entry
- following command should display installed components in the OracleHome set in the environment ($ORACLE_HOME)
FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Module=/oracle/product/11g/db/jdk/jre/bin/libj9jit23.so
Module_base_address=0900000003B13000
Target=2_30_20070131_11312_BHdSMr (AIX 7.1)
CPU=ppc64 (4 logical CPUs) (0x100000000 RAM)
JVMDUMP006I Processing Dump Event "gpf", detail "" - Please Wait.
JVMDUMP007I JVM Requesting System Dump using '/home/oracle/core.20111019.113613.
22151306.dmp'
JVMDUMP010I System Dump written to /home/oracle/core.20111019.113613.22151306.dm
p
JVMDUMP007I JVM Requesting Snap Dump using '/home/oracle/Snap0001.20111019.11361
3.22151306.trc'
UTE105: Error writing header to tracefile: /home/oracle/Snap0001.20111019.113613
.22151306.trc
JVMDUMP010I Snap Dump written to /home/oracle/Snap0001.20111019.113613.22151306.
trc
JVMDUMP007I JVM Requesting Java Dump using '/home/oracle/javacore.20111019.11361
3.22151306.txt'
JVMDUMP012E Error in Java Dump: /home/oracle/javacore.20111019.113613.22151306.t
xt
JVMDUMP013I Processed Dump Event "gpf", detail "".
CAUSE
The JAVA_COMPILER environment variable needs to be set to NONE.
SOLUTION
Disabling the JAVA_COMPILER will allow the DBUA/DBUA to run in it's native mode.The JAVA_COMPILER environment variable needs to be set to NONE.
% export JAVA_COMPILER=NONE
And then invoke the DBUA and DBCA