![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1623915.1 : Failed to load library error for SAS IT/IR controller is seen while sundiag script is running
In this Document
Created from <SR 3-8460480899> Applies to:Exadata Database Machine V2 - Version All Versions and laterInformation in this document applies to any platform. SymptomsThe following is an example of the error: # /opt/oracle.SupportTools/sundiag.sh
Oracle Exadata Database Machine - Diagnostics Collection Tool Gathering Linux information Skipping ILOM collection. Use the ilom or snapshot options, or login to ILOM
driveTool Version 1.30 Library loaded for MegaRAID SAS Controller. Storelib Version : 3.90-0
Log w/ Device Id 8 will be store in file Logpgs_for_devid_8 Log w/ Device Id 9 will be store in file Logpgs_for_devid_9 Log w/ Device Id 10 will be store in file Logpgs_for_devid_10 Log w/ Device Id 11 will be store in file Logpgs_for_devid_11
==============================================================================
ChangesThis error is seen in the Exadata 11.2.3.3.0 release. Subject to future image changes, this error may disappear. CauseRunning "drivetool" is newly implemented by the sundiag script in Exadata 11.2.3.3.0 or later release. See <Bug: 18157164> for more details. See Internal <Bug 17307319> for internal information. SolutionPlease ignore the error message. The sundiag script collects necessary data even with the error message. References<BUG:18157164> - SUNDIAG.SH IS THROWING THE ERROR LIBRARY FOR MEGARAID SAS CONTROLLER DLERROR<BUG:17307319> - WHEN A HDD GOES INTO NON-NORMAL STATE COLLECT HDD DRIVE LOGS; PACKAGE IN SUNDIAG Attachments This solution has no attachment |
||||||||||||||||||||
|