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 220.127.116.11,18.104.22.168.0 and 22.214.171.124
-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 126.96.36.199 (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 188.8.131.52 and above as smooth as possible by automating many of the
manual pre and post checks detailed in various upgrade related documents.
Could not start the OracleCRService service on Local Computer.
Error 1067: The process terminated unexpectedly.
[ clsdmt]Listening to (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=61200))
[ OCRAPI]a_is_valid_user_group: User name [wnt-sim\27235] not in user database
[ OCRAPI]a_is_valid_user_group: scls ret  slos [Information of error OS: Category:  Operation: [scls_iddb_get_user_id_by_name] : [LookupAccoun] Others: [LookupAccountName failed] Dep: ]
[ OCRAPI]a_create_key: THE SECURITY ATTRIBUTE PASSED is invalid user [wnt-sim\27235] group 
2011-02-08 17:32:46.835: [ CRSOCR]32OCR api procr_create_key failed for key SYSTEM.crs.versions.config_versions.
OCR error code = 32OCR api procr_create_key failed for key SYSTEM.crs.versions.config_versions. OCR error code = 27 OCR error msg: PROC-27: Error in authentication layer Authentication error [SLOS error information: Category:  Operation: [scls_iddb_get_user_id_by_name] Location: [LookupAccoun] Other: [LookupAccountName failed] Dep: ] [ default]Error in writing config version to OCR
OracleCRService Will Not Start Due To Unavailability of CRS Install Owner User Account [ID 601299.1]
During the final stage (Remote operations) of a RAC install (CRS or RDBMS), the installer reports an error while copying files to a remote node.
WARNING: Error while copying directory C:\oracle\product\10.2.0\crs with exclude file list
'C:\DOCUME~1\oracle\LOCALS~1\Temp\OraInstall2011-02-07_09-14-01PM\installExcludeFile.lst' to nodes 'NODE2'.
[PRKC-1073 : Failed to transfer directory "C:\oracle\product\10.2.0\crs" to any of the given nodes "NODE2 ". Error on node NODE2:Access denied]
Disable Antivirus while install Oracle CRS or RAC
Or use this note…
RAC install reports ‘access denied’ error while copying files to remote node [ID 373470.1]
Runing patch102.bat fails with process running on Windows
Successful validation check of Oracle CRS services status
Failed to patch all the files in the ORA_CRS_HOME C:\oracle\product\10.2.0\crs
Please ensure that all processes running from the home have been stopped.
ERROR: “FAILED TO PATCH ALL THE FILES IN THE ORA_CRS_HOME…” running patch102.bat on Windows [ID 415526.1]
RMAN Performance Tuning Using Buffer Memory Parameters [ID 1072545.1]
The purpose of RMAN performance tuning is to identify the bottlenecks for a given backup or restore job and use RMAN commands, initialization parameters, or adjustments to physical media to improve overall performance.
Recently installed Oracle Database on AIX 6.1 system I’ll post here the problems and solutions encountered during implementation.
As problems arise I’ll post new problems and solutions.
Installing Oracle Database 11gR2 (184.108.40.206.0) on AIX fail at Prerequisites Check. Missing : IZ97457 and IZ89165
IZ97457: SEA/VIO CLIENT HANG – INTERRUPTS DO NOT REACH THE TRUNK ADAPTER APPLIES TO AIX 6100-05
IZ89165: BIND64 CORES WITH -BLAZY OPTION ON 61TL6 APPLIES TO AIX 7100-00
An Authorized Program Analysis Report, or APAR, is a formal report to IBM development of a problem caused by a suspected defect in a current release of an IBM program.
IBM release an new APAR number for each TL.
IZ97457: SEA/VIO CLIENT HANG - INTERRUPTS DO NOT REACH THE TRUNK ADAPTER APPLIES TO AIX 6100-05
5300-11 - use AIX APAR IZ98424
5300-12 - use AIX APAR IZ98126
6100-04 - use AIX APAR IZ97605
6100-05 - use AIX APAR IZ97457
6100-06 - use AIX APAR IZ96155
7100-00 - use AIX APAR IZ97035
IZ89165: BIND64 CORES WITH -BLAZY OPTION ON 61TL6 APPLIES TO AIX 7100-00
6100-03 - use AIX APAR IZ89304
6100-04 - use AIX APAR IZ89302
6100-05 - use AIX APAR IZ89300
6100-06 - use AIX APAR IZ89514
7100-00 - use AIX APAR IZ89165
In your case Oracle OUI don’t know if APAR is installed because it check only one APAR Number.
So see this example:
root:/> oslevel -r
#### Check if apar number IZ89165 is installed.
### Using APAR number required by Oracle
root:/> instfix -a -i |grep IZ89165
#### nothing found
root:/> instfix -a -i |grep IZ89514
IZ89514 Abstract: Linking with -blazy and -G or -brtl causes core dump
IZ89514 Symptom Text:
All filesets for IZ89514 were found.
So, just Ignore warning, if you make sure which APAR already installed.
Install Oracle 10g R2 on AIX 6.1 and the installation hangs at 83% in Prereqs Check.
I have installed the 220.127.116.11 Grid Infrastructure in different User and directory on the same system.
Oracle Grid Infrastructure for Standalone allows you to install the binaries to User (eg grid) different operating system User (eg Oracle) Oracle Database.
This helps in the administration and security. But I do not recommend doing this because many problems are still solved with workaround.
To solve this problem use note on MOS:
Instalation Software Oracle 10.2.0.1 In AIX hangs [ID 1162824.1]
Bug 9916876 the hang was due to 10.2 install attempting to connect to 11.2 Grid Infrastructure home.
It was unable to connect due to different OS Users and Groups for the different installation
Linking Fails With “ld: 0706-010 The binder was killed by a signal: Segmentation fault” On AIX 6.1
ld: 0706-010 The binder was killed by a signal: Segmentation fault
Check for binder messages or use local problem reporting procedures.
INFO: make: 1254-004 The error code from the last command is 254.
INFO: make: 1254-004 The error code from the last command is 2.
INFO: End output from spawned process.
INFO: Exception thrown from action: make
Exception Name: MakefileException
Exception String: Error in invoking target 'agent nmo nmb' of makefile '/u01/app/oracle/product/10.2.0/db_1/sysman/lib/ins_sysman.mk'.
Unable to create 10.2.0.4 database on 18.104.22.168 Grid Infrastructure on AIX 6.1
DBCA displays the following error:
" In order to use Automatic Storage Management (ASM), the ORacle CLuster Synchronization Service (CSS) must be up and running. Run $ORACLE_HOME/localconfig reset script from command prompt to start CSS.
The trace file in $ORACLE_HOME/cfgtoollogs/dbca contains the following error:
[AWT-EventQueue-0] [15:41:8:479] [StorageOptionsPage.validate:522] CSS Not Running
Pre 11.2 Database Issues in 11gR2 Grid Infrastructure Environment [ID 948456.1]
Due to unpublished bug 8288940, DBCA will fail if database files are located in ASM.
As of now, patch 8288940 is available for 10.2.0.4, 22.214.171.124 and 126.96.36.199 as a .jar file as it is platform independent; fix will be included in the 10.2.0.5 patchset.
OUI FAILS TO DETECT RUNNING PROCESSES CORRECTLY ON AIX 6.1 ML 4 SP1
Oracle Universal Installer has detected that there are processes running in the currently selected Oracle Home. The following processes need to be shutdown before continuing:
This a bug on AIX.
IZ67400: FUSER GIVES INCORRECT PIDS WITH -X OPTION
Check this note on MOS: The Installer (OUI) Detects Processes Running on ORACLE_HOME on AIX 6.1 TL04 SP1 [ID 980602.1]