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

Description:
We see the following message (for various different libraries) thousands of times in the ./abc50/scratch/run_e_11 logs:

2011-03-01 11:25:59 Update : e 00 ETS60 ABC01:001228068
2011-03-01 11:25:59 Error: io_z105 - table doesn't exist in database or tab_io_remote for library: 'ETS60'.

<where ETS60 is a non-existent HOL library>

Resolution:
The following SQL shows that the vast majority of z105's are type 'e':

abc00@ALEPH20> select Z105_TYPE, count(*) from z105 group by Z105_TYPE;
**** Hit return to continue ****

Z COUNT(*)
- ----------
4 22
8 87
e 2045321

This error is occurring because of lines like this in the ./abc01/tab/tab_z105:

UPDATE-DOC e ETS50 ETS60 ETS30
INDEX-DOC e ETS50 ETS60 ETS30

All of the XXX60's in tab_z105 need to be corrected to ABC60.

The type 'e's are "update of Z13/Z13U(short doc) of ADM/HOL/CRS-libraries as a result of BIB-record update".

There are two choices for handling this:

1) using SQL to change the incorrect Z105_TARGET_LIBRARY's from "xxx60" to "ABC60"; or

2) deleting these z105 type "e"s and running p_manage_07 to rebuild the z13 in ABC60.

#2 is probably the better choice.

(Note: KB 16384-35395 is an associated problem at the same site with type '8' z105's.)

• Article last edited: 10/8/2013