How to obtain Oracle Inventory for your Oracle Home

Hello,

Here is a "how to" post.

Requirement:

You have accidentally deleted the oracle inventory or the oracle inventory is corrupt. You need the oracle inventory to be able to apply some patch using Opatch.

How to obtain your inventory back:

a. If your database is RAC:

$ORACLE_HOME/oui/bin/runInstaller -attachHome -local -invPtrLoc /var/opt/oracle/oraInst.loc ORACLE_HOME="/oracle/product/10.2.0.4/ORADB"
ORACLE_HOME_NAME="oradb_home_10_2_0_4" "CLUSTER_NODES={db-host-01,db-host-02}" LOCAL_NODE="db-host-01"

The above command will only update the inventory on the local node (where the command is being run) without affecting the other nodes in the cluster.

b. If your database is non-RAC:

$ORACLE_HOME/oui/bin/runInstaller -attachHome -invPtrLoc /var/opt/oracle/oraInst.loc ORACLE_HOME="/oracle/product/10.2.0.4/ORADB" ORACLE_HOME_NAME="oradb_home_10_2_0_4"


I believe this should work well with 11g db also.

Disclaimer: Please make sure to test these commands thoroughly if you plan to use these in your environment. These commands have worked well for me in the past, but you should use your judgement if you plan to use them in your environment. Ultimately, you are responsible for the outcome! :)


- Aravind Kamath Posral

The system property CV_NODE_ALL has not been set to the static nodelist

Hello Readers,

I think last couple months have been quiet ones for appsdbatechstuff with not much posts from my side. Here is an issue we faced while setting up CRS. The overall scope of the activity was 11g GRID Infrastructure Installation and a 11gR2 code tree setup for a two-node RAC system.

While running the cluster verify after the CRS installation, we faced the following error:

$cluvfy stage -post crsinst -n all -verbose

Performing post-checks for cluster services setup
The system property CV_NODE_ALL has not been set to the static nodelist
Verification cannot proceed

$


Fix:

Make sure your /var/opt/oracle/oraInst.loc is pointing to the GRID_HOME inventory and not the database code tree inventory. Re run the cluster verify utility.



- Aravind Kamath Posral