• Article Type: General
• Product: Aleph
• Product Version: 20

Problem Symptoms:
1. On the ARC server, the /exlibris/app/oracle/diag/rdbms/arc2/arc2/trace/alert_arc2.log has the following message: "ORA-1653: unable to extend table SYS.WARNING_SETTINGS$ by 128 in tablespace SYSTEM".

2. On the Aleph server, the arc-01 (ETL) job doesn't complete; the ./xxx50/scratch/p_arc_01_c.log has:

a. numerous "Syntax error at line 1" messages and/or
b. "ORA-04043: object L3_MRR_BIB_INFO does not exist" error messages

and the "top" command shows that the "compress_seq_file" process (generated by the arc-01 job) has been running for many hours and is using 99-100% of the processors it is running on.

Cause:
1. SYSTEM tablespace in the arc2 or arc3 database on ARC server is full

2. On the Aleph server, because the previous night's run of p_arc_01 never finished, tonight's p_arc_01 started while the previous was still running.

Resolution:
1. Double the size of the SYSTEM tablespace in the arc2 (or arc3) database on the ARC server, for instance, increasing it from 1.5 Gig to 3 Gig.
a. log on to ARC server as user crn
b. Do "util o/13/3/3" to add a datafile. (Note: there is no "dlib" on the ARC server; the "util" command can be entered in directly at the unix prom;pt.)

2. Use the following commands to locate running arc-01 processes on the Aleph server:
> ps -eaf |grep csh |grep arc
> ps -ef |grep compress_seq_fi

3. Kill the processes found in step 2

4. Resubmit the p_arc_01 job on the Aleph server (or wait until it's released from the job_list again).