SL8500 - After ACSLS Audit A Non-existing Tape Is Reactivated For A Cartridge That Had Been Removed From Tape Drive

Asset ID:	1-72-2297993.1
Update Date:	2018-05-17
Keywords:

Solution Type Problem Resolution Sure

Solution 2297993.1 : SL8500 - After ACSLS Audit A Non-existing Tape Is Reactivated For A Cartridge That Had Been Removed From Tape Drive

Applies to:

Sun StorageTek SL8500 Modular Library System - Version All Versions and later
Information in this document applies to any platform.

Symptoms

Tape T06642T1 which is physically out of the library is consistently found in HLI slot 0, 6,33,17, 1 and reactivated after an ACSLS audit.
Cartridge summary report shows HLI slot 0, 6,33,17, 1 (LRCSR 2,3,34,2,5) does contain tape T13412T1

Library rail col side row address_type prev_library prev_rail prev_col prev_side prev_row status label partitionId hli_lsm hli_panel hli_row hli_col
2 3 34 2 5 cell 2 3 34 2 5 readable T13412T1 0 6 33 1 7 1

Changes

Cause

This looks to be related to a Media Validation Table issue.
Found a reference to tape T06642T1 in slot 2,3,34,2,5 in the nvram.db

SL8500_516000300045_Thu_Jul_06_2017_UTC_07_31_13_logs/hbc/nvram/nvram.db

INSERT INTO "media_validation_record" VALUES('1,1,1,1,1','2,3,34,2,5','06','T06642T1');
CREATE TABLE media_validation_reservation (
  drive_address VARCHAR NOT NULL,
  reservation_id VARCHAR,
  label VARCHAR,
  PRIMARY KEY(drive_address)

Solution

Via SL8500 CLI,command, do a CLEAR DATABASE

SL8500> clear database
clear database Clears the cartridge database and REBOOTs the library controller.
WARNING: This command will delete the database and reboot the controller.
COMPLETED

Created Bug 26401942 - A tape outside the library is reactivated in cell 0, 6,33,17, 1 by ACSLS audit.

Importing T06642T1 into slot 2,3,34,2,5 worked. Tape is now listed in this slot in the cartridge summary and also listed in a slot location in the nvram.db. However the MV record was not removed.

SPLAT Link:
https://tapesupport.us.oracle.com/Splat/Frontend/log_view.php?report_id=372690

Will a clear database clean up the nvram.db from the MV record?
Yes, it will.
It will then cause a full audit of the library.

Attachments

This solution has no attachment