Last updated on JUNE 13, 2017
Applies to:Oracle SuperCluster T5-8 Hardware - Version All Versions and later
Exadata X6-2 Hardware - Version All Versions and later
Exadata X6-8 Hardware - Version All Versions and later
Exadata X5-2 Hardware - Version All Versions and later
Oracle SuperCluster M6-32 Hardware - Version All Versions and later
Information in this document applies to any platform.
Exadata X5/X6 reports "Disk controller was hung. Cell was power cycled to stop the hang." on SW images prior to 22.214.171.124.3.161109
Note: Exadata X5-2L/X6-2L Extreme Flash Storage Servers do not have a SAS HBA and are not affected.
Note: Exadata systems older than X5-2 use a different SAS HBA and are not affected.
Note: Exadata X4-8 systems with X5-2L Storage Servers only applies to the Storage Servers; the X4-8 DB nodes use a different SAS HBA and is not affected.
Issue: The server will alert with this (cellcli or dbmcli - depending on server type that saw the event):
IMPORTANT NOTE: It is possible due to another image issue in 126.96.36.199.2 and earlier that the SAS HBA firmware logs do not contain any information due to a incorrect setting that clears the logs on the power cycle. If this is the case, please ensure also the procedure in Note 2135119.1 is completed to ensure persistent logging is enabled in addition to this solution. The additional steps are included below.
Workaround: None, the power cycle recovers the HBA back to an operational state, as designed by Exadata server monitoring service (MS).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms