- Article Type: General
- Product: Aleph
- Product Version: 18.01
We are seeing the following errors following our 32- to 64-bit Oracle upgrade:
'Failed to find ADM-BIB relation' in the cataloging module.
When the Tech Services staff try to work in Acq they get "Remote Service Error (c0502 13) Record is not of FMT "AD"
A Remote Service Error (c0901 bind 12) "Record is not of FMT "AD" when we tried to collapse issue boxes for binding and when we clicked on the bind/change button.
The ADM z00 records were loaded with a null between each character. They appear in util f/4 as "double-spaced".
We reloaded the ADM z00 records in the correct form (using p_file_04), that corrected the "Record is not of FMT "AD" message, which was due to the fact that the FMT was " A D" rather than "AD", but the "Failed to find ADM-BIB relation" message continued with certain records due to work which was done when the bad ADM records were in place, resulting in bad links; bib records with no ADM link, etc.
If your bib and ADM numbers are mostly in synch, the first thing to do is to look at the ADM record with the same number as the bib. If it has an LKR field, with the problem bib number in it, for example, abc50 doc 000123456 has an
field, then you can resend ADM doc record 000123456 to the server (via util 1/13) or generate a z07 (via p_manage_40) -- either will create the correct z103 bib-ADM link.
The same procedure can be used for *any* LKR field which does not have a proper z103 existing for it.
If there is no ADM record with the same number as the bib record and if there is still an HOL link but the ADM link is gone, the following SQL will show you the item (and ADM) record key of the linked ADM:
abc50@ALEPH0> select z30_rec_key from z30 where Z30_HOL_DOC_NUMBER_X = '001074976';
**** Hit return to continue ****
You can resend ADM doc record 000654321 to the server (via util 1/13) or generate a z07 (via p_manage_40) -- either will create the correct z103 bib-ADM link.
- Article last edited: 10/8/2013