- Article Type: General
- Product: Aleph
- Product Version: 19.01
When I run Service p_ret_01 on records retrieved by the following Multi-base CCL Search:
(wow = ab not wauth = authority) AND (wow= ab not wauth= returned?) AND (wow= ab not wauth= bslw) AND (wow=ab not wcl= main) AND (wow= mh not wcl=abcd) AND (wow=ab not wcl=de?)
to retrieve records
From Last Updated Date: 09/01/2010
To Last Updated Date: 09/30/2010
I always get the following error msg:
Oracle error: update_cursor z30
ORA-00942: table or view does not exist
For other to/from dates, p-ret-01 runs fine on the same data (e.g., 08/01/2010-08/31/2010).
What's wrong with the Sept records?
Looking at KB 8192-1880, I get this for the first SQL:
sys01@ALEPH0> select substr (Z103_REC_KEY,1,5), count(*) from z103 where z103_lkr_type = 'ADM' group by substr (Z103_REC_KEY,1,5);
SYS01 2 <---
What stands out is "SYS01" -- even though the LKR-TYPE is "ADM" and SYS01 is a bib library.
And this for the second SQL:
sys01@ALEPH0> select Z103_REC_KEY from z103 where z103_lkr_type = 'ADM' and substr (Z103_REC_KEY,1,5) = 'SYS01';
util f/3/12 shows this:
ENTER HOME LIBRARY : sys01
ENTER DOC-NUMBER : 011089710
sys01 000000000 ADM <------------
ABC50 011089710 ADM
SYS60 006059707 HOL
We see that bib record 011089710 was last updated on Sept. 2, 2010:
CAT L $$aBATCH-UPD$$b40$$c20100902 ...
Thus, p_ret_01 is finding bib record 011089710, for Sept 2010, and looking for ADM records which are linked to it.
It finds "ADM library" sys01, looks for z30 record 000000000 in library sys01, and finds that sys01 has no z30 table.
I deleted this incorrect z103 as follows:
sys01@ALEPH0> delete from z103 where z103_lkr_type = 'ADM' and z103_lkr_library = 'sys01' and Z103_LKR_DOC_NUMBER = '000000000';
This corrected the problem and permitted p_ret_01 to run.
If there is actually a sys01 doc record with the key of 000000000:
sys01@ALEPH0> select * from z00 where z00_doc_number = '000000000';
that record is also incorrect and invalid and should be deleted. (You will find that you can not bring this record up in the GUI Cataloging or in util f/4. It needs to be deleted via SQL.)
- Article last edited: 10/8/2013