![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Problem Resolution Sure Solution 2325985.1 : T10000C/D - NOSNO Errors
In this Document
Oracle Confidential PARTNER - Available to partners (SUN). Applies to:StorageTek T10000D Tape Drive - Version All Versions and laterStorageTek T10000C Tape Drive - Version All Versions and later Information in this document applies to any platform. SymptomsASRs coming in with FSC: NOSNO. This started when SDP2 was upgraded to version 2.4. T10000C and T10000D tape drives are sending back trap type 24 with no FSC in the trap. SDP2 at version 2.4 inserts NOSNO as the FSC and attempts to pull the drive log. CauseTape drive is sending back trap type 24 with no FSC. SDP2 puts NOSNO in for the FSC and attempts to pull the drive log. SDP2 does not currently wait long enough for the drive to come back from a SNO and therefore does not collect the drive log. A later SDP2 version will wait longer before it attempts to collect the logs from the drive. SolutionAction Plan for these errors: If the customer has not mounted any more tapes on the drive then have them view the drive display using SLC. It might have something like DMP1 followed by a 4 digit FSC in the display that you can reference. Issue a remote retrieval of another set of logs for this drive from the SDP2 server to verify if the drive took a SNO at the time of the error. Zip together and process the event logs in SPLAT separately from the other log file types. Process (in SPLAT) each dump in the log bundle separately. Review all logs and troubleshoot the SNO (if one is found) in the drive event logs or if there is a dump that matches the time stamp of the error.
Attachments This solution has no attachment |
||||||||||||||||
|