My Oracle Support Banner

ACSLS: Can't Communicate With SL4000 After Clearing ACSLS Database (Doc ID 2591666.1)

Last updated on NOVEMBER 27, 2019

Applies to:

Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 8.5 to 8.5 [Release 8.0]
StorageTek SL4000 Modular Library System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

After using the SL4000 BUI to “Restart Library” with the “Clear Database” option, the Partition IDs can change and ACSLS will not come online.
While it is recommended the Library Configuration be exported before clearing the database, unfortunately the import of the same configuration
does not result in the original Partition IDs being assigned to the targeted partition.

When ACSLS is first brought up against an imported library db, all ports and such are offline.

The logs will show communication errors that ACSLS can not connect to the library.

These errors were seen in the acsss event log file:

ACSLS gui was never run against this to see what/how it would be displayed.

Varying the ports online repeated the errors in the log of ACSLS after timeout.

ACSLS can no longer communicate with the SL4000 library.

Changes

The SL4000 library export/import processes can result in new partition identifiers on the library.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References

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