Before you run diagnostic tests or contact Oracle support, review the following troubleshooting tips.
Use SLC to check the health of the library and the devices (see Chapter 14, "Viewing Library and Device Information").
To perform a health check:
Log in to SLC.
Access the System Detail module, Tools > System Detail.
Check the device in the device tree for the following indicators: Device Healthy or Device Error
Additional checks:
Check the Status (for example, online/offline) and Statistics (for example, uptime, downtime, errors and warnings) tabs for more information on the health of the library and devices.
Make sure the cartridges are fully seated and properly oriented in their storage slots.
Inspect for any foreign objects or debris and remove them if found.
Check that the library power switch is in the ON position.
Check all power cord connections.
Make sure that there is power to the outlet.
Replace the power cord.
Open the CAP and make sure the cartridges in the CAP slots are properly seated. Close the CAP.
Check the SLC Heartbeat icon.
Check SLC for any displayed error messages.
Open the front door. Observe the state of the cartridges, robot hand, and tape drives.
Make sure cartridges are fully seated and properly oriented in their storage slots.
Make sure packing materials have been removed.
Remove any objects or debris from the library floor.
Check the status of the tape drives.
Close the front door.
Make sure the tape drives are fully seated and locked forward by pushing and pulling on the rear of the drive tray. Any motion of the tray indicates that it requires re-seating and locking down.
Make sure cables are securely attached to their connectors on the rear of the library, the tape drives, and the client computer.
Make sure cables are securely attached to their connectors on the rear of the library, the drives, and the client computer.
Replace the cleaning cartridge with a new one.
Run the Library Self-Test and note if errors are reported for the drive.
Run any client computer-based drive diagnostic tests.
Use library self-tests to help diagnose issues. Library self tests can be non-disruptive (cartridges are returned to their original locations) or disruptive (cartridges may be placed in new locations).
Note:
Before performing a disruptive test, the library must be taken offline (see "Taking the Library Offline").Make sure the proper drive diagnostic cartridges are in the library (see "Importing/Exporting Diagnostic and Cleaning Cartridges").
In SLC, select Tools > Diagnostics, and click the Library folder.
Click the SelfTest tab.
In the Mode list, select the type of self-test:
Non-Disruptive — all cartridges used in the test are returned to their original locations
Disruptive — cartridges may be returned to new locations. The library must be taken offline to all hosts before running this test.
Click Run. Test results display when the test completes.
For disruptive tests, bring the library online to resume normal operations.
What the library checks during a self-test:
Verifies the communication path between the library controller, drives, elevators, and robots.
Performs get and put operations to check the health of the robots, elevators, and CAPs. This includes get and put operations from a reserved system slot to a random empty storage slot or CAP slot.
Audits the entire library.
Performs mounts and dismounts of diagnostic cartridges for all the drives installed in the library. The self-test does not begin unless a diagnostic cartridge is found in the system slots. If the system finds a compatible diagnostic cartridge, the self-test repeats for each drive type. If the system does not find a diagnostic cartridge for a drive type, the system skips the mount/dismount operation for the drive.
Use device self-tests to help diagnose issues. A self-test can be performed on a CAP, robot, or drive.
Note:
To perform a drive or robot self-test, diagnostic cartridges must be available in the library ("Importing/Exporting Diagnostic and Cleaning Cartridges").In SLC, select Tools > Diagnostics.
Expand the device folder (CAP, Robot, or Drive). Select the device to test.
Click the SelfTest tab.
In the Mode list, select Non-Disruptive.
Click Run. A message appears when the test finishes.
Diagnostic moves can help monitor or diagnose robotic problems by issuing a series of "get" and "put" operations. The system chooses a robot for the diagnostic move based on the minimum and maximum ranges set for the target and pool addresses. Multiple robots may be selected if the address range requires it.
Successful diagnostic moves do not rearrange the cartridges in the library — the system returns cartridges to their original locations. However, some diagnostic move failures can cause cartridges to be left in new locations.
Note:
Diagnostic moves require sharing of robot resources. You should not run a diagnostic move during peak activity periods.You can set up and run multiple diagnostic move routines simultaneously if the target and pool ranges for each diagnostic move do not overlap.
Select Tools > Diagnostics. Select the Library in the device tree.
Click the DiagMove tab, and then the Manage tab.
In the Defined Sequence section, click Add.
Define the target address range (the area used for "get" operations).
Select a slot type.
Select the starting and ending locations for the range.
Click Next.
Define the source address range (the area used to supply cartridges or empty slots if a target address does not contain a cartridge or no empty slots are available.)
Select a slot type.
Select the starting and ending locations.
Click Next.
Name the move and specify a move count (between 1 and 5000).
Select an access order., move type, and enable/disable the pre-move compatibility check (see below for details).
Click Finish. The new diagnostic sequence is listed in the Defined Sequences section. See "Starting a Diagnostic Move".
A diagnostic move is defined by:
Target Address Range — defines the area used to perform the "get" operation in a diagnostic move. Valid target address types are storage slots, CAP, drive and storage slots, system slots, or all.
Note:
All resources within the target address range are reserved. However, only the location currently being accessed by the robot for a get/put operation is unavailable to the host.Pool Address Range — defines the area used to supply cartridges or empty slots if a target address does not contain a cartridge or no empty slots are available. The pool and target address can overlap.
Access Order — determines how the robot performs get operations within the target address range. There are two options:
Sequential — robot performs a get operation starting with the first location in the target address range. The robot continues visiting the locations sequentially through the range until it completes the requested number of moves.
Random — robot randomly picks a location in the target address range to get a cartridge. The robot can also visit the same location in the target address range multiple times to get a cartridge; however, if you specify enough move requests, the robot is guaranteed to visit all slots. The random access routine ends after the requested number of moves is complete.
Note:
You can run multiple moves simultaneously if the target and pool address ranges for the moves do not overlap.Before starting a diagnostic move, you must define the move (see "Defining a Diagnostic Move").
Select Tools > Diagnostics. Select the Library in the device tree.
Click the DiagMove tab, and then the Manage tab.
In the Defined Sequences section, select a diagnostic move. Click Open.
Select File > Start Sequence.
You can save a defined diagnostic move to a file and use it to restore a move that has been deleted from the library or copy it to a different library.
Select Tools > Diagnostics. Select the Library in the device tree.
Click the DiagMove tab, and then the Manage tab.
In the Defined Sequence section, select a diagnostic move, and then click Save at the top of the SLC screen.
To start a diagnostic move, see "Starting a Diagnostic Move".
Select Tools > Diagnostics. Select the Library in the device tree.
Click the DiagMove tab, and then the Monitor tab.
Each monitor window indicates the status of the move:
| Status Indicators | Valid Values |
|---|---|
| Spooling Status — whether the move output is being saved to a file | True, False |
| State — execution state of the move | Running, pausing, paused, stopping, stopped |
| Health — health state of the move | OK, warning, error |
| Completed moves — number of moves completed | Count |
Use the File menu in each Monitor window to start/stop/pause the sequence, clear the output window, or start/stop spooling.
Controller card status is indicated by LEDs on the card and displayed in SLC (see "Viewing Device Status and Properties"). You can use the status of the card to troubleshoot issues with the library.
The LEDs and meanings are the same on both card types (HBC and HBT).
| Controller Card LED | Definition |
|---|---|
| ACTIVE - Green | Card is functioning as the active and is running active code. |
| STANDBY - Amber | Card is functioning as the standby and is running standby code. |
| FAULT - Red | Card has experienced a serious error. |
| EJECT OK - Blue | Support representative can safely initiate a card eject. |
You can also initiate a switching using host software or CLI (see "Ways to Initiate a Manual Failover").
This procedure is not available at the local operator panel.
Verify the device state of the card indicates "switch is possible" (see "Viewing Device Status and Properties").
In SLC, select Tools > Diagnostics.
Select the Redundant Electronics folder.
Click Apply to begin the switch process. If there is a problem with the standby library and drive controller cards, you are not allowed to continue with the switch.
If there are no errors, click Yes.
Click OK to log off the SLC.
Wait until the switch is complete before logging back into the library. You must specify the IP address or DNS alias of the new active controller.
You can only clear alerts marked as "Clearable" and only if service is active on the library.
Clearing an alert only removes it from the Status Module display; it does not resolve the underlying cause. The library health indicator returns to "Normal" if there are no other device or status alerts. If the alert is subject to periodic updates, it will reappear at the next update cycle.
Select Tools > System Detail, and click the Library folder.
Click the Status tab, and then the Status Module tab.
On the Clear Alert Number list, select the alert number to clear, and then click Apply.
Alignment of the touch screen is calibrated at the factory. If the touch screen becomes mis-aligned, you can re-calibrate or reset it. The method of calibration depends on the operator panel type (see "Viewing the Local Operator Panel Type").
If you have a Linux-based local operator panel (DL or OL), you can re-calibrate it yourself or reset it to the factory setting with the procedures below.
If you have a Windows-based local operator panel (W), contact your Oracle support representative.
For an accurate calibration, make sure there is no debris on the touch screen.
Log in to the local operator panel.
Select Tools > Calibrate.
Tap Calibrate.
A series of targets will display. Gently tap in the center of each target with your finger or a pointing stylus.
To save the new settings:
Tap the Click Me buttons within the indicated time period.
If the buttons do not depress, the touch screen is not properly aligned. Discard the new settings and see Step 6.
Click OK to save the new settings.
To discard the new settings:
Let the timer run out without tapping the Click Me button.
Return to Step 4 and re-calibrate.
The local operator panel reboots automatically after an unsuccessful second calibration and restores the previously saved alignment.
Use a sniffer (a device or program that traces the network traffic for the library).
Display the port statistics on the switch or router to which the library is connected. Search for any errors that were encountered.
Run a trace with the library management software that displays host-to-library packets and transmissions.
Make sure that two separate hosts are not competing to manage one library or one partition.