Oracle Database Appliance Diagnostic Information required for Disk Failures

Asset ID:	1-75-1390058.1
Update Date:	2018-03-21
Keywords:

Solution Type Troubleshooting Sure

Solution 1390058.1 : Oracle Database Appliance Diagnostic Information required for Disk Failures

Applies to:

Oracle Database Appliance
Oracle Database Appliance Software - Version 2.1.0.1 and later
Information in this document applies to any platform.

Purpose

The script needs to be executed as root on the ODA nodes having disk problems. The scripts collect diagnostic information required by Sun

Troubleshooting Steps

For systems using image version 2.2.0.0.0 or later, just execute odasundiag.sh as referenced below:

Usage:

# /root/Extras/odasundiag.sh

Execution will create a date stamped tar.bz2 file in /tmp/diskdiag_/tar.bz2

Upload this file to the Service Request.

For systems using image version before 2.2.0.0.0:

1. Download to the ODA Server with the disks failures, file odasundiag.zip

2. Unzip into /tmp directory

3. Change permissions (700) to file odasundiag.sh and execute:

As root ,
# chmod 700 odasundiag.sh
#./odasundiag.sh

4. Upload the tar.bz2 file generated. Under /tmp, will be a tar.bz2 file with the content of directory created by the execution of the script, format /tmp/diskdiag_/tar.bz2,

Note :

If you get below error

bash: ./odasundiag.sh: /bin/bash^M: bad interpreter: No such file or directory

then

vi odasundiag.sh

:set fileformat=unix
:wq!

and re-run

Running an odasundiag.sh on V1 and V2,you will notice below message.You can safely ignore this message

# /root/Extras/odasundiag.sh
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/dm-3 doesn't contain a valid partition table

Example: odasundiag_2011_12_31_05_35.tar.bz2

Upload this file to the Service Request.

This is the list of the files created by odasundiag.sh

odasundiag_2011_12_31_05_35/
odasundiag_2011_12_31_05_35/messages
odasundiag_2011_12_31_05_35/odarm1_system-serial_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_show-storage_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_show-diskgroup_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_sel-list_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_show-disk_detail_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/messages.1
odasundiag_2011_12_31_05_35/odarm1_show-expander_0_0_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/messages.2
odasundiag_2011_12_31_05_35/odarm1_show-expander_0_1_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_show-local_disk_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_lsscsi_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_lspci-xxxx_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_dmesg_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_show-version_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_show-disk_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_fdisk-l_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/odarm1_lspci_2011_12_31_05_35.out
odasundiag_2011_12_31_05_35/oakd.log
==============================================================================
Done the report files are in bzip2 compressed /tmp/odasundiag_2011_12_31_05_35.tar.bz2
==============================================================================

Attachments

This solution has no attachment