Located either in /home/oracle/exachk OR, later, /opt/oracle.SupportTools/exachk


  1. asm asm Checks
  2. clusterware clusterware checks
  3. dba dba Checks
  4. storage storage server checks
  5. switch switch checks
  6. sysadmin sysadmin checks
  7. virtual_infra all OVS checks , all control VM checks, all NTP related checks, and stale VNICs check (Exalogic Only)























Located either in /home/oracle/exachk OR, later, /opt/oracle.SupportTools/exachk






exachk can be executed with following arguments:



  • -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: exachk -a -o v
  • -r exclude High availability best practices checks (see user guide for more details)
  • -clusternodes Pass comma separated node names to run exachk only on selected nodes.
  • -cells Pass comma separated storage server names to run exachk only on selected storage servers.
  • -ibswitches Pass comma separated infiniband switch names to run exachk only on selected infiniband switches.
  • -localonly Run exachk only on local node.
  • -nopass Dont print PASS’ed checks in HTML report.
  • -diff [-outfile ] Diff two exachk reports. Pass directory name or zip file or html report file as &
  • -c Used only under the guidance of Oracle support or development to override default components
  • -profile Pass specific profile. List of supported profiles:


  • -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 scorecard (see userguide for more details)
  • -u Run exachk to check pre-upgrade or post-upgrade best practices.-o pre or –o post is mandatory with -u option like ./exachk -u -o pre
  • -f Run Offline.Checks will be performed on data already collected from the customer system


exachk can be executed with following arguments:

exachk version 2.2.1 uses the “nm2user” userid for IB switch validation. If you wish to have exachk use the “root” userid for IB switch validation (the original pre-version 2.2.1 behavior), please set the RAT_IBSWITCH_USER environment variable.










Detailed report (html) –


UPLOAD(if required) –



Typically, there is very little or no screen output following the clusterwide checks banner. The last screen

output to appear is the file reference information, as shown below: