What is the Oracle Exadata Diagnostics Collection Tool sundiag.sh
Very often when creating a Support Request (SR) for an issue on an Oracle Exadata Database Machine, you’ll need to run the script “sundiag.sh“. Which is the “Oracle Exadata Database Machine – Diagnostics Collection Tool“.
The tool collects a lot of diagnostics information that assist the support analyst in diagnosing your problem, such as failed hardware like a failed disk, etc.
More information can be found on My Oracle Support (MOS) Note:
SRDC – EEST Sundiag (Doc ID 1683842.1)
Oracle Exadata Diagnostic Information required for Disk Failures and some other Hardware issues (Doc ID 761868.1)
How to run the Diagnostics Collection Tool
To run “sundiag.sh“, is very simple as shown below:
[root@v1ex1dbadm01 ~]# /opt/oracle.SupportTools/sundiag.sh Oracle Exadata Database Machine - Diagnostics Collection Tool Gathering Linux information Skipping collection of OSWatcher/ExaWatcher logs, Cell Metrics and Traces Skipping ILOM collection. Use the ilom or snapshot options, or login to ILOM over the network and run Snapshot separately if necessary. /var/log/exadatatmp/sundiag_v1ex1dbadm01_xxxxxxxxxx_2018_01_17_13_49 Gathering dbms information Generating diagnostics tarball and removing temp directory ============================================================================== Done. The report files are bzip2 compressed in /var/log/exadatatmp/sundiag_v1ex1dbadm01_xxxxxxxxxx_2018_01_17_13_49.tar.bz2 ============================================================================== [root@v1ex1dbadm01 ~]#
For more advanced collections, use the option switches to override default behaviour as shown in the help:
[root@v1ex1dbadm01 ~]# /opt/oracle.SupportTools/sundiag.sh -h Oracle Exadata Database Machine - Diagnostics Collection Tool Version: 126.96.36.199.3.161109 By default sundiag will collect OSWatcher/ExaWatcher, Cell Metrics and traces, if there was an alert in the last 7 days. If there is more than one alert, latest alert is chosen to set the time range for data collection. Time range is 8hrs prior to and 1hr after the latest alert, for the total of 9 hrs e.g: latest alert timestamp = 2014-03-29T01:20:04-05:00 echo Time range = 2014-03-28_16:00:00 and 2014-03-29_01:00:00 User can also specify time ranges (as explained in usage below), which takes precedence over default behavior of checking for alerts Usage: /opt/oracle.SupportTools/sundiag.sh [ilom | snapshot] [osw <time ranges>] osw - This argument when used expects value of one or more comma separated time ranges. OSWatcher/ExaWatcher, cell metrics and traces will be gathered in those time ranges. The format for time range(s) is <from>-<to>,<from>-<to> and so on without spaces where <from> and <to> format is <date>_<time> <date> and <time> format should be any valid format that can be recognized by 'date' command. The command 'date -d <date>' or 'date -d <time>' should be valid e.g: /opt/oracle.SupportTools/sundiag.sh osw 2014/03/31_15:00:00-2014/03/31_18:00:00 Note: Total time range should not exceed 9 hrs. Only the time ranges that fall within this limit are considered for the collection of above data ilom - User level ILOM data gathering option via ipmitool, in place of separately using root login to get ILOM snapshot over the network. snapshot - Collects node ILOM snapshot- requires host root password for ILOM to send snapshot data over the network. [root@v1ex1dbadm01 ~]#
Then just upload the bzip2 file to your SR on MOS.
I tend to run this as part of my SR creation and upload to save time.
If you found this blog post useful, please like as well as follow me through my various Social Media avenues available on the sidebar and/or subscribe to this oracle blog via WordPress/e-mail.
Zed DBA (Zahid Anwar)