Follow the steps explained in this section to troubleshoot and fix Oracle ORAchk and Oracle EXAchk related issues.
Follow these steps to fix Oracle ORAchk and Oracle EXAchk related issues.
Ensure that you are using the correct tool.
If you have an Oracle Engineered System other than Oracle Database Appliance, then use Oracle EXAchk. For all other systems, use Oracle ORAchk.
Ensure that you are using the latest versions of Oracle ORAchk and Oracle EXAchk.
New versions are released every three months.
$ ./orachk –v
$ ./exachk –v
Compare your version with the latest version available here:
For Oracle ORAchk, refer to My Oracle Support Note 1268927.2.
For Oracle EXAchk, refer to My Oracle Support Note 1070954.1.
Check the FAQ for similar problems in My Oracle Support Note 1070954.1.
Review files within the log
directory.
Check applicable error.log
files for relevant errors.
This file contains stderr
output captured during the run, not everything you see in here will mean you have a problem, but if you have a problem this may give more information.
output_dir/log/orachk _error.log
output_dir/log/exachk _error.log
Check applicable log for other relevant information.
output_dir/log/orachk.log
output_dir/log/exachk.log
Review My Oracle Support Notes for similar problems.
For Oracle ORAchk issues, check My Oracle Support Community (MOSC).
If necessary capture debug output, log a new SR and attach the resulting zip
file.
Follow these procedures to capture debug information.
To capture debug output, use the following process:
Before enabling debug, reproduce the problem with the least run necessary.
Debug captures a lot, the resulting zip
file can be large so try to narrow down the amount of run necessary to reproduce the problem.
Use relevant command line options to limit the scope of checks.
Enable debug.
–debug
option:
$ ./orachk –debug
$ ./exachk –debug
When debug is enabled, Oracle ORAchk and Oracle EXAchk create a new debug log file in:
output_dir/log/orachk _debug_date_stamp_time_stamp.log
output_dir/log/exachk _debug_date_stamp_time_stamp.log
The output_dir
directory retains a number of other temporary files used during health checks.
If you run health checks using the daemon, then restart the daemon with the –d start –debug
option.
$ ./orachk –d start –debug
$ ./exachk –d start –debug
orachk_daemon_debug.log
exachk_daemon_debug.log
Collect the resulting output zip
file, and the daemon debug log file if applicable.
Related Topics
Parent topic: Troubleshooting Oracle ORAchk and Oracle EXAchk
Follow these steps to troubleshoot and fix error messages and unexpected output.
watchdog
process that monitors and kills the commands that exceed default timeouts to prevent hangs.orachk_error.log
, some messages are expected and they are not indicative of problems.Parent topic: Troubleshooting Oracle ORAchk and Oracle EXAchk
Use any supported UNIX and Linux terminal type (character mode terminal, ILOM, VNC server) to run Oracle ORAchk and Oracle EXAchk.
Respond to the prompts during interactive runs, or while configuring the daemon.
Each terminal type has advantages and disadvantages. The effect of a dropped network connection varies based on the terminal type used.
For example, in an interactive run using a character mode terminal, if all the prompts are answered before the network drop, then the running process completes successfully even if the network connection drops. If the network connection drops before all the input prompts are answered, then all the running processes hang. Clean up the hung processes manually when the network connection is restored.
Using a remote connection to a VNC server running on the database where Oracle ORAchk and Oracle EXAchk are running minimizes the network drop interruptions.
If you use accessibility software or devices that prevent the use of a VNC server, and experience network drops, then contact your system administrator to determine the root cause and adjust the environment as necessary.
For example, if an accessibility aid inserts suspensions and restarts the interactive process running Oracle ORAchk and Oracle EXAchk leads to an operating system timeout due to terminal inactivity. Lengthen the inactivity timeouts of the environment before running the commands.
The timeout caused by an assistive tool at the operating system level due to terminal inactivity is not specific to Oracle ORAchk and Oracle EXAchk. The timeout could happen to any process managed by the assistive technology.
Parent topic: Error Messages or Unexpected Output
Oracle ORAchk and Oracle EXAchk create temporary files and directories at runtime, as well as output files for data collection.
If you cancel Oracle ORAchk using Ctrl+C or if Oracle ORAchk fails due to an error, then Oracle ORAchk cleans up the files that Oracle ORAchk created while running.
If Oracle ORAchk or Oracle EXAchk complete health check runs, but did not generate output files, then there is an error probably near the end of the run that caused an ungraceful exit. If the problem persists, then run the tool again in debug mode and examine the output. If necessary, contact Oracle Support for assistance.
Related Topics
Parent topic: Error Messages or Unexpected Output
Oracle ORAchk and Oracle EXAchk have a built-in watchdog
process that monitors and kills the commands that exceed default timeouts to prevent hangs.
Killing a command results in “line ****: **** Killed $perl_cmd 2>> $ERRFIL?” error.
Related Topics
Parent topic: Error Messages or Unexpected Output
There are a number of possible causes related to not having a supported platform or not being able to read or write into temporary, working or installation directories.
Oracle ORAchk and Oracle EXAchk display the same error message also as, RC-002- Unable to read driver files
Troubleshooting Process
Verify that you are running on a supported platform.
Verify that there is sufficient diskspace available in the temporary or output directory. If necessary increase disk space or direct temporary and output files elsewhere.
Verify the hidden subdirectory .cgrep
exists within the install location. This directory contains various support files some of which are platform-specific.
Verify that you are able to write into and read out of the temporary and working directory location.
Related Topics
Parent topic: Error Messages or Unexpected Output
Oracle ORAchk and Oracle EXAchk tools exit if the tools detect prompts in the user profile.
Oracle ORAchk and Oracle EXAchk fetch the user environment files on all nodes. If the user environment files contain prompts, for example, read -p
, or other commands that pause the running commands, then the commands timeout. The commands timeout because there is no way to respond to the messages when it is being called.
All such commands cannot be detected in the environment. However, the commands that can be detected lead to this message.
Troubleshooting Process
Comment all such prompts from the user profile file (at least temporarily) and test run again.
Parent topic: Error Messages or Unexpected Output
If you see messages similar to -bash: /usr/bin/ssh -q: No such file or directory or /usr/bin/scp -q: No such file or directory, then refer to "Remote Login Problems" to fix the issues.
Related Topics
Parent topic: Error Messages or Unexpected Output
When examining the orachk_error.log
, some messages are expected and they are not indicative of problems.
These errors are redirected and absorbed into the error.log
to keep them from being reported on the screen. You do not need to report these types of errors to Oracle Support.
For example, an error similar to the following is reported numerous times, once for each Oracle software home for each node:
/bin/sh: /u01/app/11.2.0/grid/OPatch/opatch: Permission denied chmod: changing permissions of `/u01/app/oracle_ebs/product/11.2.0.2/VIS_RAC/.patch_storage': Operation not permitted OPatch could not open log file, logging will not be possible Inventory load failed... OPatch cannot load inventory for the given Oracle Home.
These types of errors occur in role-separated environments when the tool runs as the Oracle Database software owner uses Opatch
to list the patch inventories of homes that are owned by Oracle Grid Infrastructure or other Oracle Database home owners. When you run Opatch
to list the patch inventories for other users, Opatch
fails because the current user does not have permissions on the other homes. In these cases, the Opatch
error is ignored and the patch inventories for those homes are gathered by other means. To avoid such errors, Oracle recommends that you run Oracle ORAchk and Oracle EXAchk as root
in role-separated environments.
Also, ignore the errors similar to the following:
./orachk: line [N]: [: : integer expression expected
The line number changes over time. However, the error indicates that the tool was expecting an integer return value and no value was found. The value was null that the shell was not able to compare the return values. The error is repeated many times for the same command, once for each node.
Parent topic: Error Messages or Unexpected Output
Oracle ORAchk and Oracle EXAchk display this message if the tools are not able to detect the operating system.
If Oracle ORAchk and Oracle EXAchk are not able to detect the operating system, then the tools prompt:
Data needed for the derived platform could not be found
Improperly detecting an unsupported platform
RAT_OS
environment variable to the correct operating system:
$ export RAT_OS=platform
Parent topic: Troubleshooting Oracle ORAchk and Oracle EXAchk
Follow the procedures in this section to troubleshoot and fix Oracle Clusterware or Oracle Database issues.
oraInst.loc
and oraInventory
files.Parent topic: Troubleshooting Oracle ORAchk and Oracle EXAchk
Oracle ORAchk discovers the location of the Oracle Clusterware home from the oraInst.loc
and oraInventory
files.
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
Troubleshooting Process
Ensure that the oraInst.loc
file is located correctly and is properly formed.
RAT_INV_LOC
environment variable to point to the oraInventory
directory:
$ export RAT_INV_LOC=oraInventory directory
RAT_CRS_HOME
environment variable to point to the location of the Oracle Clusterware home:
$ export RAT_CRS_HOME=CRS_HOME
Oracle ORAchk and Oracle EXAchk tools display this message if the tools cannot find the Oracle Database software installed.
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.
Oracle ORAchk and Oracle EXAchk tools display this message if the tools cannot find the version of the Oracle Database software installed.
If Oracle ORAchk and Oracle EXAchk cannot find the correct version, then set the RAT_DB
environment variable to the applicable version.
$ export RAT_DB=11.2.0.3.0
Oracle ORAchk and Oracle EXAchk tools display this message if the tools cannot find the Oracle ASM software installed.
RAT_ASM_HOME
environment variable to the applicable home directory.
$ export RAT_ASM_HOME=ASM_HOME
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.
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.
$ ./orachk -dbnames ORCL,ORADB
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.
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
.
Oracle Database login problems arise if you run Oracle ORAchk and Oracle EXAchk without sufficient privileges.
root
or grid
, and if you experience problems connecting to the database, then perform the following steps:grid
(operating system).export ORACLE_HOME=path of Oracle database home
export ORACLE_SID=database SID
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/lib:$PATH
$ORACLE_HOME/network/admin/tnsnames.ora
file fordatabase SID
.$ORACLE_HOME/bin/sqlplus "sys@SID as sysdba"
, and enter the password.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.
Troubleshoot and fix remote connections issues.
Parent topic: Troubleshooting Oracle ORAchk and Oracle EXAchk
If Oracle ORAChk and Oracle EXAchk tools have problem locating and running SSH or SCP, then the tools cannot run any remote checks.
Also, the root
privileged commands do not work if:
Passwordless remote root
login is not permitted over SSH
Expect utility is not able to pass the root
password
Note:
Set the RAT_EXPECT_DEBUG
and RAT_EXPECT_STRACE_DEBUG
variables only at the direction of Oracle support or development. The RAT_EXPECT_DEBUG
and RAT_EXPECT_STRACE_DEBUG
variables are used with other variables and user interface options to restrict the amount of data collected during the tracing. The script
command is used to capture standard output.
As a temporary workaround while you resolve remote problems, run reports local on each node then merge them together later.
./orachk -local
./exachk -local
./orachk –merge zipfile 1 zip file 2 > zip file 3 > zip file ...
./exachk –merge zipfile 1 zip file 2 > zip file 3 > zip file ...
Parent topic: Remote Connections
You must have sufficient directory permissions to run Oracle ORAchk and Oracle EXAchk.
Install Oracle EXAchk in /opt/oracle.SupportTools/exachk
as the Oracle Grid Infrastructure home owner
Install Oracle ORAchk in CRS_HOME/suptools/orachk
as the Oracle Grid Infrastructure home owner
Install Oracle EXAchk in /opt/oracle.SupportTools/exachk
as root
Install Oracle ORAchk (in a convenient location) as root
(if possible)
or
Install Oracle ORAchk (in a convenient location) as Oracle software install user or Oracle Database home owner
Parent topic: Troubleshooting Oracle ORAchk and Oracle EXAchk
Follow these procedures to address slow performance and other issues.
The watchdog.log
file also contains entries similar to killing stuck command.
Depending on the cause of the problem, you may not see skipped checks.