Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1002897.1
Update Date:2017-08-07
Keywords:

Solution Type  Technical Instruction Sure

Solution  1002897.1 :   SL8500 - Handbot Fails to Enter Safety Area During Bot Replacement  


Related Items
  • Sun StorageTek SL8500 Modular Library System
  •  
  • Sun StorageTek SL8500 Modular Library System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
  •  

PreviouslyPublishedAs
203989


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Confidential for Partners and Oracle Support personnel

Applies to:

Sun StorageTek SL8500 Modular Library System - Version All Versions to All Versions [Release All Releases]
All Platforms

Goal

Oracle/StorageTek[TM] SL8500 Modular Library System, Replacing HandBot with Service Safety Door Feature Installed

All 8-Bot SL8500 libraries with the Service Safety Door installed via CB_102237 or FB_102235 should not perform a HandBot replacement without using the SSD. If a HandBot is replaced by opening the library front access doors without employing the SSD it will probably result in an initialization error.

Solution

Replacing HandBot with Service Safety Door Feature Installed.

All 8Bot SL8500 libraries with the Service Safety Door installed via CB_102237 or FB_102235 should not perform a HandBot replacement without using the SSD. If a HandBot is replaced by opening the library front access doors without employing the SSD it will probably result in an initialization error.

If a HandBot fails to position itself in the service safety area after a failure:

-Check the library event log and determine if the HandBot failed with a reach unsafe error.

Note: The system is architectured not to move on the rail in the advent of a reach unsafe error.

-If the error is associated with a reach unsafe error a soft reboot via the SLC diagnostic menu can be done as a last ditch effort.

Note: There is some risk of the HandBot dropping the tape during recovery and the initialization should be monitored.

-If there is not a reach unsafe error a soft reboot should be performed via SLC.
-If the soft reboot does not move the HandBot to the service area it will be necessary to vary the associated LSM's offline, open the library front access door and move the HandBot to the service area.
-Close the front door and replace the HandBot using the SSD.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback