Sun StorageTek T10000B Tape Drive
 
StorageTek T10000C Tape Drive
 
Sun StorageTek 9840 Tape Drive
 
StorageTek T10000D Tape Drive
 
Sun StorageTek T10000A Tape Drive
 
Sun StorageTek 9940 Tape Drive
 
Sun StorageTek T10000 Tape Drive
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: STK T-Series Drive
 

In this Document

Symptoms

Cause

Solution

References

Applies to:

Symptoms

 Write perm errors. These are sometimes called Write Data Checks. For Fibre Channel tape drives they will create sense key = x3 (sense byte 2) , ASC = 0C (sense byte 12), ASCQ = 00 (sense byte 13)type sense data. They can be associated with application error messages that indicate a write permanent error has occurred. For FICON drives a write perm error is typically associated with error message IOS000I with WDC listed as the cause. (Write Data Check)

Cause

Write perm errors. Tape drive or media issue.

Solution

If the same tape(s) has failed with a write perm error on more than 1 drive.

• The failing tape (or tapes) should be taken out of service. 
• Copy the data off of the tape
• Certify the tape.
  • To certify the tape, simply re-write the tape (using any data) until the tape is full. If it passes this certification test then the tape is available to be re-used.
  • If the certification test fails and the tape is still under warranty, take the necessary steps to have the tape replaced.

If this is a one time failure on 1 tape and 1 drive:

• If the tape is new then it may have some debris on the physical media that will clean up after a couple of uses. Write the tape until it is full 1 or 2 times.
  • If the tape can be successfully written then it is ready for reuse as a scratch tape.
• If it is not a new tape then the tape or drive may be marginal or possibly both the tape and the drive are marginal. Collect the Tape Drive Event Log (refer to Doc ID 2166889.1) and attach the log to the MOS Service Request. Analysis of the log will determine if the drive is marginal based on statistics gathered across several tape mounts.
  • The Tape Drive Event Log needs to be processed by Oracle support. The tool available for processing Tape Drive Event Logs will indicate if the drive is marginal based on internal tape drive statistics gathered across several tape mounts.
• If the drive is not shown as marginal in the event log statistics then copy the data off of the tape and certify the tape. To certify the tape, simply re-write the tape (using any data) until the tape is full.
  • If it passes this certification test then the tape is available to be re-used.
  • If the certification test fails and the tape is still under warranty, take the necessary steps to have the tape replaced.
• If both the drive and tape appear to be fine then the next step is to load the tape into a drive, unload the tape, and force a dump on the drive. (refer to Doc ID 2099953.1 for instructions on how to force a drive dump).
  • Oracle support can look at the history of the tape that is available in the dump for further analysis of the problem.

This solution has no attachment