Best Exadata Health Check Tools

With the Introduction of Exadata in to market, the job of a remote DBA have became more tough. Now a remote DBA has look all of the following.

1. Traditional Database Software.
2. Real Application Cluster (RAC).
3. Automatic Storage Management (ASM).
4. Exadata Software Maintenance and Trouble shooting.
5. Exadata Hardware Health.

You can find lot of resource for helping a remote DBA for first three, but there are very few for last two, Since Exadata is new into the market. So, I decide to write about Two most important, free and easy to use tools  introduced by Oracle itself for Exadata Hardware and Software Health Check.

1. Sundiag.
2. Exachk.

Let's see how they help remote DBA to check Exadata Hardware and Software Health.


This is script provided by Oracle, available on each Cell Node (Storage Server) as /opt/oracle.SupportTools/ for check Exadate Hardware Status. When ever a remote DBA see an I/O related error, First thing needs to check is Disks status on all servers. You need to execute this script on each Cell Node one by one. Below are the steps to execute script.

Login to DB Server using root user, get IP of Cell Server from /etc/hosts in Unix and login to Cell Sever using ssh.

root@exadb07:~# ssh

[root@exadbcel11 ~]# cd /opt/oracle.SupportTools/

[root@exadbcel11 oracle.SupportTools]# ./

Oracle Exadata Database Machine - Diagnostics Collection Tool
Gathering Linux information
Skipping ILOM collection. Use the ilom or snapshot options, or login to ILOM
over the network and run Snapshot separately if necessary.
Generating diagnostics tarball and removing temp directory

Done. The report files are bzip2 compressed in /tmp/sundiag_exadbcel11_1038FMM04N_2013_04_07_07_34.tar.bz2

Report is generated as /tmp/sundiag_exadbcel11_1038FMM04N_2013_04_07_07_34.tar.bz2

Transfer this file to your local system and unzip it. Now, most important past what to look at for any issues  ?

After unzipping files, you will find around 40 files, find alert.log and exadbcel11_celldisk-detail_2013_04_04_14_32.out (file with prefix cellname_celldisk-detail_date.out).

check alter log for any ORA messages etc. Now in celldisk_detail file find "Status" field, the value for this field should be "normal" for all available cell disks.

If the value for "Status" field is "PREDICTIVE FAILURE", "POOR PERFORMANCE", "WARNING - POOR PERFORMANCE". You might need to change you disk, for this open a SR with

This is exadbcel11_celldisk-detail_2013_04_04_14_32.out for reference.


This is another tool used for checking Exadata
  • Software On Database Server, 
  • Software On Storage Server, 
  • System wide firmware, 
  • software versions, 
  • System wide Automatic Service Request (ASR) healthcheck. 
Exachk is one spot tool for Exadata Software Health check. The good part about this tool is you need to execute this only from one DB server and it will give you a combined report for all DB and Cell Server, Finally to make remote DBA life easy.

To execute this script, you need to download it from from Article ID 1070954.1. Copy script on DB node and unzip it and execute it like below.

-bash-4.1$ unzip

-bash-4.1$ ./exachk

CRS stack is running and CRS_HOME is not set. Do you want to set CRS_HOME to /u01/app/[y/n][y]y
Checking ssh user equivalency settings on all nodes in cluster
Searching for running databases . . . . .
List of running databases registered in OCR
1. dba4
2. None of above

Collecting patch inventory on  CRS HOME /u01/app/
Collecting patch inventory on ORACLE_HOME /u01/app/oracle/product/
                      CLUSTERWIDE CHECKS
Detailed report (html) - /export/home/oracle/exachk_exadbcel11_dba4_040713_084344.html
UPLOAD(if required) - /export/home/oracle/

This script will ask few inputs, Choose according to your environment setup. The final out put will be in two forms HTML and zip file shown above, Download on local machine check for "Status" value "FAIL" and provided details for it to resolve these problems.

After working on exachk Reports, I would say it is the best, only place, consolidate report with Recommendations for Exadata Environment. This report can be very help tool for remote DBA for checking over all health for environment before applying any big change like Upgrade, Patching etc.

Please share your views about this Article, or any experience with working on these two tools.

1 comment:

  1. Any impact on production server after/during running