![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||
Solution Type Technical Instruction Sure Solution 2226173.1 : How To Collect Diagpack Diagnostic Package In Exadata
In this Document
Applies to:Exadata X6-2 Hardware - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform. GoalThe DIAGPACK diagnostic package, contains logs and traces that are useful for troubleshooting all type of disks problems (Eg. F320 Flash cards or nvme disks in a system). SolutionIn case of the failure of Accelerator F320 PCIe Card or nvme disk, Collect the Diagpack bundle from the system and upload to SR for further troubleshooting Diagpack feature is in image 12.1.2.3.0 and later. The location of the diagnostic packages is $LOG_HOME. You can find diagpack location in alerthistory as below Example:
alerthistory-detail.out name: 1_1 alertDescription: "Flash disk of size 2981GB in PCI slot 2 FDOM slot 1 failed" alertMessage: "Flash disk failed. Status : FAILED Manufacturer : Oracle Model Number : Flash Accelerator F320 PCIe Card Size : 2981GB Serial Number : S2T7NAAH402087 Firmware : KPYA8R3Q Slot Number : PCI Slot: 2; FDOM: 1 Cell Disk : FD_01_ex05cl02 Grid Disk : Not configured" alertSequenceID: 1 alertShortName: Hardware alertType: Stateful beginTime: 2016-07-24T08:26:26+09:00 examinedBy: metricObjectName: FLASH_2_1 notificationState: 1 sequenceBeginTime: 2016-07-24T08:26:26+09:00 severity: critical alertAction: "The flash disk has failed. A white cell locator LED has been lit to help locate the affected cell. Please replace the flash disk. If the flash disk is used for flash cache, then flash cache will be disabled on this disk thus reducing the effective flash cache size. If the flash disk is used for flash log, then flash log will be disabled on this disk thus reducing the effective flash log size. If the flash disk is used for grid disks, then Oracle ASM rebalance will automatically restore the data redundancy. Detailed information on this problem can be found at ttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1113023.1 Automatic Service Request has been notified with Unique Identifier: af386c6b-c9b9-4763-a1d9-ce7351af81aa. Diagnostic package is attached. It is also accessible at https://hostname_xxx/diagpack/download?name=hostname_xxx_2016_07_24T08_26_26_1_1.tar.bz2 It will be retained on the storage server for 7 days. If the diagnostic package has expired, then it can be re-created at https://hostname_xxx/diagpack". If the diagnostic package has not expired yet, the sundiag.sh will also collect diagpack under asr directory. You can also find the alert in ./cell/ms-odl.trc [2017-01-19T22:43:18.297-05:00] [ossmgmt] [TRACE] [] [oracle.ossmgmt.ms.core.MSAlertHistory] [tid: 66] [SRC_CLASS: oracle.ossmgmt.ms.core.MSAlertHistory$AutoDiagPackTask] [SRC_METHOD: diagPackage] Auto diagnostic packaging has completed
[2017-01-19T22:43:18.297-05:00] [ossmgmt] [TRACE] [] [oracle.ossmgmt.ms.core.MSAlertHistory] [tid: 66] [SRC_CLASS: oracle.ossmgmt.ms.core.MSAlertHistory$AutoDiagPackTask] [SRC_METHOD: diagPackage] tarPath : /opt/oracle/cell/cellsrv/deploy/log/hostname_xxx_2017_01_19T22_42_32_1_1.tar.bz2
To download the diagnostic package by name, use the following URL:
To download the diagnostic package by alert name, use the following URL:
https will only be on the customer's local network. You can also find the diagpack with below command CellCLI> LIST DIAGPACK DETAIL
name: hostname_xxx_2016_11_20T07_48_35_1_1.tar.bz2 For more information refer below link:
Attachments This solution has no attachment |
||||||||||||||
|