issue 1:
OPatch cannot find a valid oraInst.loc file to locate Central Inventory (OPatch failed with error code = 104) (文档 ID 2308329.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 Copyright (c) 2010, Oracle Corporation. All rights reserved.Oracle Home : e:\app\fmw\osb\11.1.1.7\Oracle_OSB1 Central Inventory : n/afrom : n/aOPatch version : 11.1.0.8.2OUI version : 11.1.0.9.0OUI location : e:\app\fmw\osb\11.1.1.7\Oracle_OSB1\ouiLog file location : e:\app\fmw\osb\11.1.1.7\Oracle_OSB1\cfgtoollogs\opatch\opatch2017-09-18_05-59-35AM.logPatch 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] "inst_loc"="C:\\Program Files\\Oracle\\Inventory"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
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 :or
Note : Please replace <Name_Of_The_Oracle_Home> with the name that you want to give this OracleHome.
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.soModule_base_address=0900000003B13000Target=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.dmpJVMDUMP007I JVM Requesting Snap Dump using '/home/oracle/Snap0001.20111019.113613.22151306.trc'UTE105: Error writing header to tracefile: /home/oracle/Snap0001.20111019.113613.22151306.trcJVMDUMP010I Snap Dump written to /home/oracle/Snap0001.20111019.113613.22151306.trcJVMDUMP007I JVM Requesting Java Dump using '/home/oracle/javacore.20111019.113613.22151306.txt'JVMDUMP012E Error in Java Dump: /home/oracle/javacore.20111019.113613.22151306.txtJVMDUMP013I 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