Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1358795.1
Update Date:2013-11-21
Keywords:

Solution Type  Technical Instruction Sure

Solution  1358795.1 :   Gathering data for the Oracle Database Appliance server  


Related Items
  • Oracle Database Appliance
  •  
Related Categories
  • PLA-Support>Sun Systems>x86>Engineered Systems HW>SN-x64: ORA-DATA-APP
  •  




In this Document
Goal
Solution
References


Applies to:

Oracle Database Appliance - Version All Versions and later
Information in this document applies to any platform.
***Checked for relevance on 21-Nov-2013***

Goal

Collecting data for the ODA (Oracle Database Appliance) server, originally called the Sun Fire X4370M2.

Solution

The "oakcli" utility can be used to collect diagnostic information.
There are two main diagnostic files that should be collected with oakcli, depending on the type of issue that you have.
The "validate" module will collect hardware configuration information and should be collected if you suspect a hardware issue. The "diagcollect" module will collect software logs, and should be collected if you suspect a software issue.



The validate module is located in:

/opt/oracle/oak/bin

 

Example of how to run the command as root:

# ./oakcli validate -d -f /tmp/validate.output
The file (validate.output) should be used for analysis.

By default, the validate.output file is in the same directory as oakcli utility, however, you may choose any directory.  In the command above here, we demonstrate the output file is located in /tmp.

The options are: 

# ./oakcli validate -h
Usage
 oakcli  validate [-V | -l | -h]
 oakcli  validate [-v] [-f output_file_name] [-a | -d | -c check1[,check2]]
        ARGUMENTS:
                -v      verbose output
                -f      output_file_name.The output is sent to the file instead of standard output
                -a      run all checks
                -d      run only default checks.
                -c      check1[,check2] run specific checks
                -l      list the checks and description
                -V      Print the Version
                -h      print help
        EXAMPLES:
        oakcli validate -l
        oakcli validate -a
        oakcli validate -c DiskCalibration
        oakcli validate -c SystemComponents,NetworkComponents
 
# ./oakcli validate -l
        Checkname -- Description

       =========    ===========
        *SystemComponents -- Validate system components based on ilom sensor data readings
        *OSDiskStorage -- Validate OS disks and filesystem information
        *SharedStorage -- Validate Shared storage and multipathing information
        DiskCalibration -- Check disk performance with orion
        *NetworkComponents -- Validate public and private network components
* -- Default check

 

It is recommended to run -d (default) option and -a option should be used during downtime since it will run diskcalibration.

 

The diagcollect module is located in:

/opt/oracle/oak/bin

 

Example of how to run the command as root:

# ./oakcli manage diagcollect
        Collecting crs data
        Collecting information from core files
        No corefiles found
        Collecting OCR data
        Oracle base not specified or invalid, will try to get correct oracle base
        Get valid oracle base /u01/app/grid and will collect it.
        Collecting Oracle base data
        Collecting Oracle home data
        Collecting OS logs
        Collecting Oracle installation logs
        Logs are at: /opt/oracle/oak/onecmd/tmp/invtData_rac04box1_20110915_1610.tar.gz
        Disk /dev/sdaw doesn't contain a valid partition table
        Disk /dev/md1 doesn't contain a valid partition table
        printk: 44 messages suppressed.
        Buffer I/O error on device dm-16, logical block 4
        Disk /dev/md0 doBuffer I/O error on device dm-16, logical block 5
        Doesn't contain a Buffer I/O error on device dm-16, logical block 6
        Invalid partition Buffer I/O error on device dm-16, logical block 7        
        ....
        ....
        Collecting OSW logs..
        Collecting oak data, it will take a while...
        mpt2sas0: log_info(0x3112011a): originator(PL), code(0x12), sub_code(0x011a)
        mpt2sas1: log_info(0x3112011a): originator(PL), code(0x12), sub_code(0x011a)
        mpt2sas0: log_info(0x3112011a): originator(PL), code(0x12), sub_code(0x011a)
        mpt2sas1: log_info(0x3112011a): originator(PL), code(0x12), sub_code(0x011a
Logs are collected to: /opt/oracle/oak/onecmd/oakdiag/rac04box1-20110915_1610.tar.gz
######### Log Collection Finished.#######
The output file in in /opt/oracle/oak/onecmd/oakdiag.  Please use this file for analysis.




Disk Related Issues

You will need to collect the output of the "odasundiag " script. Download the latest version which includes usage details from:

Oracle Database Appliance Diagnostic Information required for Disk Failures (Doc ID 1390058.1)


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback