Brief of RACcheck.
..... RACcheck - The Oracle RAC Configuration Audit Tool
RACcheck is designed to audit vital configuration settings for the Oracle Database, single instance databases, as well as Oracle Real Application Clusters (Oracle RAC) databases. It also includes checks for Oracle Clusterware, Oracle Automatic Storage Management (Oracle ASM) and Oracle Grid Infrastructure.
RACcheck provides best practices recommedations considering the whole stack, including Maximum Availability Architecture (MAA) configurations and is therefore the ideal tool for regular health checks as well as pre- and post-upgrade best practices assessments.
Now Oracle replace/renamed Oracle RACcheck to ORAchk.
ORAchk- Health Checks for the Oracle Stack
ORAchk replaces the popular RACcheck to support a wider range of products. ORAchk version 2.2.4 is now available for download and includes the following key features:
RACcheck renamed to ORAchk
ORAchk daemon auto-start mode after node reboot (init integration)
Merge multiple ORAchk collection reports
Upload of installed patches to database
Collection Manager for ORAchk, RACcheck and Exachk (Document 1602329.1)
ORAchk signature file in /tmp on all nodes to verify last ORAchk run
New checks and bug fixes, including
30 Oracle Ebusiness AP module data integrity checks
12 new Database checks
8 new Solaris system checks
Linux x86-64* (Enterprise Linux, RedHat and SuSE 9, SuSE 10 & SuSE 11)
Oracle Solaris SPARC (Solaris 10 and 11)
Oracle Solaris x86-64 (Solaris 10 and 11)
* 32-bit platforms not supported, no planned support for Linux Itanium
**Requires BASH Shell 3.2 or higher to be installed
Supported Oracle Releases
When to Run ORAchk
After initial Oracle RAC deployment
Before planned system maintenance
After planned system maintenance
At least once every three months
It is recommended to run the tool as the database software owner (e.g. oracle). The user may run the tool as the Grid Infrastructure software owner (e.g. grid) and it will collect the same data but database credentials must manually be supplied to perform the database related audit checks. Typically when run as oracle the customer will have OS authentication set up for the oracle database software owner and the database login credentials will not be needed.
17 of the included audit checks require root privileged data collection . If sudo is not configured or the root password is not available, audit checks which require root privileged data collection can be skipped.
1. Enter 1 if you will enter root password for each host when prompted
2. Enter 2 if you have sudo configured for oracle user to execute root_orachk.sh script
3. Enter 3 to skip the root privileged collections
4. Enter 4 to exit and work with the SA to configure sudo or to arrange for root access and run the tool later.
Please indicate your selection from one of the above options for root access[1-4]:- 2
*** Checking Best Practice Recommendations (PASS/WARNING/FAIL) ***
Collections and audit checks log file is
[oracle@node11g01 orachk]$ ./orachk -h
Usage : ./orachk [-abvhpfmsuSo:c:t:]
-a All (Perform best practice check and recommended patch check)
-b Best Practice check only. No recommended patch check
-h Show usage
-v Show version
-p Patch check only
-m exclude checks for Maximum Availability Architecture (MAA) scorecards(see user guide for more details)
-u Run orachk to check pre-upgrade or post-upgrade best practices for 22.214.171.124,126.96.36.199.0 and 188.8.131.52
-o pre or -o post is mandatory with -u option like ./orachk -u -o pre
-f Run Offline.Checks will be performed on data already collected from the system
-o Argument to an option. if -o is followed by v,V,Verbose,VERBOSE or Verbose, it will print checks which passs on the screen
if -o option is not specified,it will print only failures on screen. for eg: orachk -a -o v
Pass comma separated node names to run orachk only on subset of nodes.
Pass comma separated database names to run orachk only on subset of databases
Run orachk only on local node.
Run orachk in debug mode. Debug log will be generated.
eg:- ./orachk -debug
Skip PASS'ed check to print in orachk report and upload to database.
Do not print healthscore in HTML report.
-diff [-outfile ]
Diff two orachk reports. Pass directory name or zip file or html report file as &
Compare two different Exalogic rack and see if both are from the same release.Pass directory name or zip file as & (applicable for Exalogic only)
-c Used only under the guidance of Oracle support or development to override default components
initsetup : Setup auto restart. Auto restart functionality automatically brings up orachk daemon when node starts
initrmsetup : Remove auto restart functionality
initcheck : Check if auto restart functionality is setup or not
initpresetup : Sets root user equivalency for COMPUTE, STORAGE and IBSWITCHES.(root equivalency for COMPUTE nodes is mandatory for setting up auto restart functionality)
start : Start the orachk daemon
start_debug : Start the orachk daemon in debug mode
stop : Stop the orachk daemon
status : Check if the orachk daemon is running
info : Print information about running orachk daemon
stop_client : Stop the orachk daemon client
nextautorun : print the next auto run time
run orachk only if daemon is running
Dont use daemon to run orachk
configure orachk daemon parameter like "param1=value1;param2=value2... "
Supported parameters are:-
AUTORUN_INTERVAL :- Automatic rerun interval in daemon mode.Set it zero to disable automatic rerun which is zero.
AUTORUN_SCHEDULE * * * * :- Automatic run at specific time in daemon mode.
- - - -
▒ ▒ ▒ ▒
▒ ▒ ▒ +----- day of week (0 - 6) (0 to 6 are Sunday to Saturday)
▒ ▒ +---------- month (1 - 12)
▒ +--------------- day of month (1 - 31)
+-------------------- hour (0 - 23)
example: orachk -set "AUTORUN_SCHEDULE=8,20 * * 2,5" will schedule runs on tuesday and friday at 8 and 20 hour.
AUTORUN_FLAGS : orachk flags to use for auto runs.
example: orachk -set "AUTORUN_INTERVAL=12h;AUTORUN_FLAGS=-profile sysadmin" to run sysadmin profile every 12 hours
orachk -set "AUTORUN_INTERVAL=2d;AUTORUN_FLAGS=-profile dba" to run dba profile once every 2 days.
NOTIFICATION_EMAIL : Comma separated list of email addresses used for notifications by daemon if mail server is configured.
PASSWORD_CHECK_INTERVAL : Interval to verify passwords in daemon mode
COLLECTION_RETENTION : Purge orachk collection directories and zip files older than specified days.
unset the parameter
example: orachk -unset "AUTORUN_SCHEDULE"
Print the value of parameter
Pass specific profile.
List of supported profiles is same as for -profile.
Pass comma separated collection names(directory or zip files) to merge collections and prepare single report.
eg:- ./orachk -merge orachk_hostname1_db1_120213_163405.zip,orachk_hostname2_db2_120213_164826.zip
Pass comma separated filenames containing exalogic guest VM list(applicable for Exalogic only)
-profile Pass specific profile.
List of supported profiles:
asm asm Checks
clusterware Oracle clusterware checks
compute_node Compute Node checks (Exalogic only)
control_VM Checks only for Control VM(ec1-vm, ovmm, db, pc1, pc2). No cross node checks
dba dba Checks
ebs Oracle E-Business Suite checks
el_extensive Extensive EL checks
el_lite Exalogic-Lite Checks(Exalogic Only)
el_rackcompare Data Collection for Exalogic Rack Comparison Tool(Exalogic Only)
goldengate Oracle GoldenGate checks
maa Maximum Availability Architecture Checks
obiee obiee Checks(Exalytics Only)
storage Oracle Storage Server Checks
switch Infiniband switch checks
sysadmin sysadmin checks
timesten timesten Checks(Exalytics Only)
virtual_infra OVS, Control VM, NTP-related and stale VNICs check (Exalogic Only)
zfs ZFS storage appliances checks (Exalogic Only)
Pass comma separated storage server names to run orachk only on selected storage servers.
Pass comma separated infiniband switch names to run orachk only on selected infiniband switches.
Pass comma separated ZFS storage appliance names to run orachk only on selected storage appliances.
ORAchk Other Useful Options Not Covered Here
Using ORAchk Silently
ORAchk can be optionally run in “silent” or “non-interactive” mode in order to enable scheduling and automation
Is required only if customer does not want to use orachk daemon functionality.
Using ORAchk Daemon Mode Operation
This functionality permit non-interactive (batch or silent mode) execution on a regular interval.
When running ORAchk in daemon mode, the most recent and next most recent (if any) collection reports are automatically compared. If the mail address is configured a summary will be emailed along with attachments for the reports and the comparison report.
Report Comparisons with ORAchk
ORAchk has the ability to perform report comparisons between 2 ORAchk reports.
This allows for trending of Success Factor and Best Practice changes over time, after planned maintenance, etc within a user friendly HTML report.
ORAchk in Upgrade Readiness Mode
ORAchk can be used to obtain an automated 184.108.40.206 (or above) Upgrade Readiness Assessment.
The goal of the ORAchk Upgrade Readiness Assessment is to make the process of upgrade planning for Oracle RAC and Oracle Clusterware target versions 220.127.116.11 and above as smooth as possible by automating many of the
manual pre and post checks detailed in various upgrade related documents.