ACSLS - ACSLS terminated and Postgres database server is not starting up (Doc ID 1358359.1)

Last updated on JULY 13, 2017

Applies to:

Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 7.2 to 8.0 [Release 7.0 to 8.0]
Information in this document applies to any platform.
***Checked for relevance on 13-Aug-2013***

Symptoms

ACSLS terminated with these errors (in the acsss_event.log):


2011-09-09 11:54:53 SET_SCRATCH[6873]:
1328 N di_pri_get_status_code.c Unknown 212
di_pri_get_status_code:
DBMS error. Return code (58P01) and message ("[unixODBC]ERROR: could not
open relation 1663/16384/16568: No such file or directory;
Error while executing the query"). DI_STATUS = DI_S_FAILURE

2011-09-09 11:54:53 ACSSA[6873]:
1423 N sa_demux.c 1 296
Data base failure.

2011-09-09 11:54:53 SET_SCRATCH[6873]:
608 N cl_range_re.c 1 302
read_volume_range_normal:
EXEC SQL open vol_cursor
[DI_S_FAILURE]:

2011-09-09 12:00:09 EJECT[7816]:
1328 N di_pri_get_status_code.c Unknown 212
di_pri_get_status_code:
DBMS error. Return code (58P01) and message ("[unixODBC]ERROR: could not
open relation 1663/16384/16568: No such file or directory;
Error while executing the query"). DI_STATUS = DI_S_FAILURE

2011-09-09 12:00:09 ACSSA[7816]:
1423 N sa_demux.c 1 296
Data base failure.

2011-09-09 12:00:09 EJECT[7816]:
715 N cl_vol_read.c 1 395
cl_vol_read:
EXEC SQL select * from volumetable where volume = BW3743
[DI_S_FAILURE]:

2011-09-09 12:00:11 ACSLM[0]:
32 N lm_wait_proc.c 1 444
lm_wait_proc: Unexpected error STATUS_DATABASE_ERROR, exiting to ACSSS

2011-09-09 12:00:12 storage server[0]:
354 N ss_main.c 4 878
ss_main: exit status (23), STATUS_DATABASE_ERROR, received from acslm
 


The most current Postgres transaction log in $PGDATA/pg_log shows these start up error messages:
"could not locate a valid checkpoint record"
"could not open relation 1663/16384/16569: No such file or directory"
LOG: startup process (PID 4550) was terminated by signal 6
LOG: aborting startup due to startup process
failure

Also, if an attempt is made to restore the ACSLS database with rdb.acsss, it may fail with the following:

psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5436"

Changes

The /export/home filesystem filled up to 90% usage level.   To mitigate a disk full situation, the system administrator deleted some log files.
He inadvertently deleted the Postgres transaction logs in $PGDATA/pg_log directory.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms