12.5 Oracle Clusterware or Oracle Database is not Detected or Connected Issues

Follow the procedures in this section to troubleshoot and fix Oracle Clusterware or Oracle Database issues.

12.5.1 Oracle Clusterware Software is Installed, but Cannot be Found

Description:

Oracle ORAchk discovers the location of the Oracle Clusterware home from the oraInst.loc and oraInventory files.

Cause:

Oracle Clusterware discovery fails due to:
  • Problems discovering the oraInst.loc and oraInventory  files

  • Problems with the oraInst.loc and oraInventory  files

  • One or more paths in the oraInst.loc and oraInventory  files are incorrect

Action:

  1. Ensure that the oraInst.loc file is located correctly and is properly formed.

    If the file is not in the default location, then set the RAT_INV_LOC environment variable to point to the oraInventory directory:
    $ export RAT_INV_LOC=oraInventory directory
  2. If necessary, set the RAT_CRS_HOME environment variable to point to the location of the Oracle Clusterware home:
    $ export RAT_CRS_HOME=CRS_HOME

12.5.2 Oracle Database Software Is Installed, but Cannot Be Found

Description:

Oracle ORAchk and Oracle EXAchk display this message if the tools cannot find the Oracle Database software installed.

Action:

If the Oracle Database software is installed, but Oracle ORAchk and Oracle EXAchk cannot find, then set the RAT_ORACLE_HOME environment variable to the applicable ORACLE_HOME directory.

For example, enter the following command, where your-oracle-home is the path to the Oracle home on your system:

$ export RAT_ORACLE_HOME=your-oracle-home

Oracle ORAchk and Oracle EXAchk perform best practice and recommended patch checks for all the databases running from the home specified in the RAT_ORACLE_HOME environment variable.

12.5.3 Oracle Database Software Is Installed, but Version cannot Be Found

Description:

Oracle ORAchk and Oracle EXAchk display this message if the tools cannot find the version of the Oracle Database software installed.

Action:

If Oracle ORAchk and Oracle EXAchk cannot find the correct version, then set the RAT_DB environment variable to the applicable version.

For example:
$ export RAT_DB=11.2.0.3.0

12.5.4 Oracle ASM Software is Installed, but Cannot be Found

Description:

Oracle ORAchk and Oracle EXAchk display this message if the tools cannot find the Oracle ASM software installed.

Action:

If Oracle ORAchk and Oracle EXAchk cannot find Oracle ASM, then set the RAT_ASM_HOME environment variable to the applicable home directory.
$ export RAT_ASM_HOME=ASM_HOME

12.5.5 Oracle Database Discovery Issues on Oracle Real Application Clusters (Oracle RAC) Systems

Description:

On Oracle Real Application Clusters (Oracle RAC) systems, Oracle ORAchk discovers the database resources registered in the Oracle Cluster Registry.

The ORACLE_HOME for the database resources is derived from the profile of the database resources.

Cause:

If there is a problem with any of the profiles of the database resources, then Oracle ORAchk cannot recognize or connect to one or more databases. Use the -dbnames option temporarily to fix the problem.

Action:

Specify the names of the database in a comma-delimited list as follows:
$ orachk -dbnames ORCL,ORADB
Alternatively, use the space-delimited environment variable RAT_DBNAMES:
$ export RAT_DBNAMES="ORCL ORADB"

Use double quotes to specify more than one database.

Note:

Configure the RAT_DBHOMES environment variable if you,

  • Configure RAT_DBNAMES as a subset of databases registered in the Oracle Clusterware

  • Want to check the patch inventories of ALL databases found registered in the Oracle Clusterware for recommended patches

By default, the recommended patch analysis is limited to the homes for the list of databases specified in the RAT_DBNAMES environment variable.

To perform the recommended patch analysis for additional database homes, specify space-delimited list of all database names in the RAT_DBHOMES environment variable.

For example:
export RAT_DBNAMES="ORCL ORADB"
export RAT_DBHOMES="ORCL ORADB PROD"

Best practice checks are applied to ORACL and ORADB.

Recommended patch checks are applied to ORACL, ORADB, and PROD.

12.5.6 Oracle Database Login Problems

Oracle Database login problems arise if you run Oracle ORAchk and Oracle EXAchk without sufficient privileges. If you run Oracle ORAchk and Oracle EXAchk as a user other than the database software installation owner, root or grid, and if you experience problems connecting to the database, then perform the following steps:
  1. Log in to the system as grid (operating system).
  2. Run export ORACLE_HOME=path of Oracle database home
  3. Run export ORACLE_SID=database SID
  4. Run export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/lib:$PATH
  5. Add alias in the $ORACLE_HOME/network/admin/tnsnames.ora file fordatabase SID.
  6. Connect to the database using $ORACLE_HOME/bin/sqlplus "sys@SID as sysdba", and enter the password.
  7. Ensure that you have a successful connection.

If this method of connecting to the database does not work, then Oracle ORAchk and Oracle EXAchk do not connect either.

  • If you have multiple homes owned by different users and you are not able to login to the target database as the user running Oracle ORAchk independently in SQL*Plus, then Oracle ORAchk does not login either.

  • If the operating system authentication is not set up, then it should still prompt you for user name and password.