New bib records not being Word-indexed
- Article Type: General
- Product: Aleph
- Product Version: 20
Problem Symptoms:
Though newly-loaded bib records are retrievable in the Browse index and have "HANDLING DOC NO" entries in the $data_scratch run_e_01 log, even after several hours they are not retrievable in the Word indexes.
Cause:
Delay in processing of z07a records by the ue_01_word_parallel process.
Resolution:
1. Do the following to see how many records are in the queues:
> s+ xxx01
SQL> select count(*) from z07;
SQL> select count(*) from z07a;
2. If the z07 count is low but the z07a count is high, that means that there are records which have been otherwise indexed -- but are still awaiting Word-indexing.
3. To see if a particular record is in the z07 queue, awaiting indexing:
SQL> select z07_sequence from z07 where z07_rec_key = '001234567';
And, for the z07a queue:
SQL> select z07a_rec_key from z07a where z07a_rec_key like '%001234567';
[Note: the last 9 bytes of the z07a_rec_key are the bib doc number.]
Additional Information
Article 000003448 ("ue_01 continuously processing same records") describes why a particular bib record may have multiple z07a records.
- Article last edited: 12/5/2013