All report output is a static display of information at the time the report is generated. Click Update in the upper right corner to refresh the information.
Note:
Running multiple instances of SLC on the same workstation can cause inconsistent data on reports. It is recommended that only one user at a time produce SLC reports.In SLC, select Tools > Reports.
In the navigation tree, expand a report folder. Select a report.
You can access additional reports from the Partitions utility or the Active Capacity utility. You can view individual device information using the System Details utility.
| Folder | Report | Description |
|---|---|---|
|
Statistics |
Displays drive events and errors. The report can display up to 70 entries. |
|
|
Drive Media Events |
Displays cartridge error events that have occurred with a drive. The report can display up to 500 entries. |
|
|
Displays a summary of library operational events. |
||
|
Media Events |
Displays cartridge errors. The report can display up to 2000 entries. |
|
|
Log |
EventLog |
Displays a log of events based on severity (see "Severity"). |
|
Status Summary |
Lists cartridge location, media type, label, and status information. |
|
|
Device Reserve Table |
Lists elevator, robot, and PTP reservation information. |
|
|
Drive Table |
Lists drive location, type, and serial number information. |
|
|
CAP Summary |
Lists the location of the CAPs. |
|
|
Cartridge Summary |
Lists the location, media type, and label information for all cartridges in the library. |
|
|
Drive Summary |
Lists drive location, type, serial number, code information, and device details. |
|
|
Library Information |
Lists the library physical configuration, code version, and state of the library. |
|
|
Robot Summary |
Lists robot address and state. |
|
|
Status Detail |
CAP/Drive/Robot Details |
Lists identifying information, code version, and status of the devices. |
|
Library Details |
Lists the library physical configuration, code version, and state of the library. |
|
|
Versions |
Hardware Versions |
Lists the FRU serial number for controller cards, CAPs, robots, and PTPs. |
|
Software Versions |
Lists the code version for controller cards, CAPs, elevators, robots, and PTPs. |
|
|
Audit Log |
Lists all feature activation activity for the life of the library. To view only the current hardware activation files, see "Displaying Current Hardware Activation Files". |
|
|
CAP Usage Messages |
Messages |
Lists the CAP usage messages. To define the messages, see "Modifying Bulk CAP Messages" |
In SLC, select the Tools > Partitions > Reports tab.
Select a type of report from the menu:
Cartridge Cell and Media Summary — displays slot addresses and volume serial numbers (volsers) for the media in each partition
Orphaned Cartridge Report — displays slot addresses and volume serial numbers (volsers) for orphaned cartridges
Partition Summary — displays the resources allocated to each partition
Partition Details — displays details for a specific partition ID
Your Oracle support representative may request that you capture and transfer the Management Information Base (MIB) or Log Snapshot file.
In SLC, select Tools > Diagnostics.
Click the Library folder in the navigation tree.
Click the TransferFile tab.
Select SNMP MIB. Click Transfer File.
Save the file using a .txt suffix.
E-mail the file to your Oracle support representative.
You must save the log within 15 minutes of generation. The file is encrypted.
In SLC, select Tools > Diagnostics.
Click the Library folder in the navigation tree.
Click the Transfer File tab.
Select Log Snapshot.
Select either All Devices or Selected Device. If you choose Selected Device, select the device.
Click Generate Log Snapshot on Library.
Click Yes, and then OK.
Save the file using the automatically generated name.
E-mail the file to your Oracle support representative.
The library controller continually monitors library operations and logs all events. Using the Monitors utility of SLC, you can open an event monitor to display event data or spool it to a file. Event monitors are useful tools for root cause analysis.
In SLC, select Tools > Monitors.
Expand the Permanent Monitors folder in the navigation tree.
Click an event monitor type (see )"Event Monitor Types"). Click Open.
Use the Monitor menu to pause, resume, permanently stop, or clear the event monitor. Use the Spool File menu to save the event monitor to a file (see "Saving Event Monitor Data to a File").
Note:
To arrange multiple event monitors on one screen, use the Window menu in the upper right corner.You may need to send the file to your Oracle support representative to assist in diagnosing problems.
Open an event monitor (see "Starting an Event Monitor").
In the event monitor window, select Spool File > Start Spooling.
Browse to the desired directory, enter the file name, and click Save.
To stop spooling, select Monitor > Stop Spooling.
Result codes identify the library event type (result codes are the same as library EventIds).
In SLC, select Tools > Diagnostics. Select the Library in the device tree.
Click the Search tab.
In the Search Type list, select Result Code.
To search for a specific result code, enter the complete code (wildcards or partial codes are invalid).
To list all result codes, select List All.
Click Search.
There are four types of event monitors: All, Error Warn Info, Error and Warnings, and Errors. Each monitor type logs events based on the severity of the event. For example, the Errors monitor only logs error events (see "Severity" for a description of the event types).
Each event logged in the event monitor contains the following information:
Identifies when the event occurred.
Identifies the library address of the device corresponding to the event.
Identifies the user that originated the event. This is "root" for HLI or SCSI host activities.
Identifies the interface type of the requester. The interface can be hli, scsi, or default (for SLC or CLI requests).
Identifies the command that was issued, such as "load drive".
Identifies all host interface requests. Helps track the sequence of log activity resulting from each host request.
Identifies the significance of the event. Some event data is non-volatile, meaning it persists across system power cycles.
Error — non-volatile data indicating a fault that prevented a request (host or diagnostic) from completing successfully.
Warning — non-volatile data indicating a fault that has not stopped the library's ability to complete requests (host or diagnostic). A warning can identify a loss of performance or a condition that may indicate future irrecoverable errors.
Information — volatile data indicating general device or library information (such as the device state, device added, listener registered, tray serial number updated, and so on). This information may be important to establish a history of activity for the warning or error event.
Trace — volatile data indicating diagnostic activity tracing.
Identifies the library event type (result codes are the same as library EventIds). To search for the meaning of the Result Code using SLC, see "Displaying Result Code Definitions" or refer to the SL8500_FRSxxx_JavaErrorCodes.html file included in the library firmware code package.
Provides information about the results of the request or event.