SL4000 - Tape Mounted in Drive With Unknown Volser and ACSLS Reports Drive as "In Use" With No Volser (Doc ID 2858245.1)

Last updated on MARCH 28, 2022

Applies to:

Symptoms

It is possible for the SL4000 library to have a drive that is mounted and loaded, for which the volser is unknown. This is possible if the library database is cleared with loaded drives, or if a load or unload failure occurs and the library front door is subsequently opened.

When the library does not know the volser loaded in a drive, ACSLS is unable to carry out a dismount force operation, and manual intervention will be required.

When this situation occurs, ACSLS will end up with a drive that is marked as in use, but without a known volser. The typical solution would be an ACSLS dismount force command, but in an SL4000 library this results is a dismount failure, and the drive is left in use.

In cmd_proc, for example, a "dismount X 1,0,30,7 force" operation results in:

In some cases, ACSLS may not know that the drive is in use yet, although the library BUI does show the drive as mounted with an unknown volser. If the drive is shown as available in ACSLS, the true status (occupied) would be detected if a mount operation were attempted, and the drive would now be marked as in use. The mount itself would have failed. The drive status is also updated if the drive (or the library) is varied offline and online again in ACSLS.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.