ACSLS - Configuration Utility Fails When the SL500 Base Module CAP is Configured for Storage
(Doc ID 1020177.1)
Last updated on JULY 11, 2022
Applies to:
Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 7.3 and laterSun StorageTek SL500 Modular Library System - Version Not Applicable and later
All Platforms
Goal
Description
The ACSLS configuration utility will fail with a timeout error if the SL500 base module CAP is configured for use as storage cells.
The SL500 base module CAP should always be configured for use as I/O cells to enable Enter and Eject operations. SL500 expansion modules may be configured for use as storage or I/O cells.
There may also be errors in the postgres logs relating to the size of the cap, for example:
LOG: statement: insert into captable (acs, lsm, cap, cap_status, cap_state, cap_mode, cap_priority, cap_size, cap_condition, cap_availability, cap_desired_state) values (4, 0, 0, 10, 7, 1, 0, 0, 3, 2, 7)
ERROR: new row for relation "captable" violates check constraint "captable_cap_size_check"
To confirm cap size values the following command can be issued:
$ psql -d acsdb
Welcome to psql 8.1.11, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
acsdb=> \d captable
Table "acsss.captable"
Column | Type | Modifiers
-------------------+---------+--------------------
acs | integer | not null default 0
lsm | integer | not null default 0
cap | integer | not null default 0
cap_status | integer | not null default 0
cap_priority | integer | not null default 0
cap_state | integer | not null default 0
cap_mode | integer | not null default 0
cap_size | integer | not null default 0
cap_condition | integer | not null default 0
cap_availability | integer | not null default 0
cap_desired_state | integer | not null default 7
Indexes:
"captable_pkey" PRIMARY KEY, btree (acs, lsm, cap)
Check constraints:
"captable_acs_check" CHECK (acs >= 0 AND acs <= 31)
"captable_cap_availability_check" CHECK (cap_availability > -1 AND cap_availability < 5)
"captable_cap_check" CHECK (cap >= 0 AND cap <= 11)
"captable_cap_condition_check" CHECK (cap_condition > 0 AND cap_condition < 4)
"captable_cap_desired_state_check" CHECK (cap_desired_state = 7 OR cap_desired_state = 5 OR cap_desired_state = 2)
"captable_cap_mode_check" CHECK (cap_mode = 1 OR cap_mode = 2)
"captable_cap_priority_check" CHECK (cap_priority >= 0 AND cap_priority <= 16)
"captable_cap_size_check" CHECK (cap_size > 0)
"captable_cap_state_check" CHECK (cap_state = 7 OR cap_state = 5 OR cap_state = 6 OR cap_state = 8 OR cap_state = 2)
"captable_cap_status_check" CHECK (cap_status = 7 OR cap_status = 10 OR cap_status = 34 OR cap_status = 35 OR cap_status = 151)
"captable_lsm_check" CHECK (lsm >= 0 AND lsm <= 126)
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |