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

Description:
We recently created an abc04 library be used for AV equipment. The system allows us to create the holding record, but it does not "stay connected" to the bib.

The HOL record has an LKR field pointing to the bib record, but resending this HOL record to the server does not help.

When we call the bib record up, it does not show any connection to the HOL record. util f/3/12 shows no link between the bib and the HOL.

Resolution:
The abc60 ue_01 log has the error message, "Error in linked library: ABC04 ..."

I solved this problem by restarting the ABC60 ue_01. The ABC60 $data_scratch/run_e_01.19276 log shows that this proc had been running since June 7 at 5:00 AM and, thus, was not recognizing the addition of abc04 to the $alephe_root/aleph_start.private, $alephe_tab/library_relation, etc., which occurred in July and August.

The following grep in the abc60 $data_scratch shows the record numbers of the abc60 records which the system tried to link to abc04 bib records but failed:

lib-aleph1.tosm.ABC.edu-17(1) ABC60-ALEPH>>grep 'linked library' *e_01.*

run_e_01.19276:Error in linked library : ABC04 002416237
run_e_01.19276:Error in linked library : ABC04 002416237
run_e_01.19276:Error in linked library : ABC04 002416243
run_e_01.19276:Error in linked library : ABC04 002416244
<etc.>

You will need to check each record in this list and send it to the server to make the link to the abc04 record take effect.
Since there are only six abc04 bib records, many of these abc60 HOL records are duplicates (that is, they are pointing to the same abc04 record). The duplicates should be deleted.

Note: As discussed in KB 4107, ue_01 does not *have* to run in the xxx60 library, but, if it is running, it needs to be restarted when such changes are made to aleph_start, library_relation, etc.