p_manage_18 / pc_server / ue_01 error: unable to extend table ABC01.Znn

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

Description:
When loading a file of bib records with p_manage_18, the following errors displayed:

Oracle error: io_z11_write
ORA-01653: unable to extend table ABC01.Z11 by 245760 in tablespace TS

Oracle error: io_z11_write
ORA-01653: unable to extend table ABC01.Z11 by 245760 in tablespace TS
...
...
Oracle error: io_z11_write
ORA-01653: unable to extend table ABC01.Z11 by 245760 in tablespace TS

Oracle error: io_z11_write
ORA-01653: unable to extend table ABC01.Z11 by 245760 in tablespace TS
0 END READING AT 17:42:17
end

The error also appears in the pc_server and ue_01 logs.

I expect that our DBA will be able to increase the space needed.

However, how do we determine when the problem began and what impact it has had
on our database. What recovery steps do we need to take?

Resolution:
The following SQL shows that the abc01 z11 table resides in the TS4D tablespace:

SQL-ABC01> select TABLESPACE_NAME from all_tables where table_name = 'Z11' and OWNER = 'ABC01';

which also agrees with the abc01 file_list.

util o/14/1 shows this:

TABLESPACE_WITHOUT_FREE_SPACE
------------------------------
TS4D

(or, alternatively, it may show that the "largest free extent" in TS4D is relatively small).

This grep:

>>grep -c 'unable to extend table ABC01.Z11' *e_01.*

shows that all the errors are in the current abc01 $data_scratch/run_e_01.1254.

Looking run_e_01.1254 with "view" we see that the first error was at 08:17:

HANDLING DOC NO. - ABC01.003120586 08:17:48
Update z98 from z980 : 004001461368
Update z98 from z980 : 001001574189

Oracle error: io_z11_write
ORA-00001: unique constraint (ABC01.Z11_ID) violated

I have determined, by studying the run_e_01.1254 log, that this was 08:17:48 on Saturday, Jan.24.


You need to do the following:

1. add space to the TS4D tablespace

2. run p_ret_01 in abc01 retrieving the keys of all records with a Last update date greater than Jan. 23.

3. use the output from step 2 as input to p_manage_40 which will create a z07 indexing request for each of them; each z07 will be processed by the ue_01 indexing daemon (to create a correct z11 index entry).

(Note: If this tablespace is "autoextend", then Oracle should automatically create a datafile and the cause of the message may be something else ...)

• Article last edited: 10/8/2013