p_file_20: variety of errors
- Article Type: General
- Product: Aleph
- Product Version: 20
Description:
We are getting a variety of errors in running p_file_20. In the $alephe_scratch p_file_20 log we see:
Load: /tmp/utf_files/exlibris/aleph/a20_1/aleph/error_eng/p_file_20
Error (b_file_20_chk_edit_record) : Errors in Z304. Record No 000633
Unsupported action
Error (b_file_20_chk_edit_record) : Errors in Z305. Record No 000633
Unsupported action
Error (b_file_20_chk_edit_record) :
Record No 000729
z308-rec-key belongs to other user (012807003239 ABC50)
Error (b_file_20_chk_edit_record) : Duplicates in Z308 Record 000826
Number of Errors = 01
Info: Empty table /tmp/utf_files/exlibris/aleph/u20_1/alephe/error_eng/check_z308
Load: /tmp/utf_files/exlibris/aleph/a20_1/aleph/error_eng/check_z308
Error 0400 : key conflict
System is adding z308 type 00.
System is adding z308 type 01.
1002 READING REC AT 13:01:37
2003 READING REC AT 13:02:46
Error (b_file_20_chk_edit_record) :
Record No 002119
z308-rec-key belongs to other user (012807003269 ABC50)
Error (b_file_20_chk_edit_record) :
Record No 002240
z308-rec-key belongs to other user (012806007312 ABC50)
<etc.>
Resolution:
Looking at the abc50 $data_scratch/p_file_20_report file, the first problem we see is the "Unable to process record due to problems in other records" in record 633:
+ <line-number>000633</line-number>
+ <table-name>z303</table-name>
+ <action>REWRITE</action>
+ <match-id>02810000999</match-id>
+ <user-name>ST. LOUIS,CLEMATIS MIRABELLA</user-name>
+ <patron-id>ID181776</patron-id>
+ <msg-code>5003</msg-code>
+ <msg-desc>Unable to process record due to problems in other records.</msg-desc>
+ </section-02>
See KB 5770 in regard to this "Unable to process ..." message, but, in short, it means that a problem has occurred in processing some *other* segment of this PLIF record. In this case that is the ADDR (z304) and BOR (z305) segments:
...
+ <section-02>
+ <line-number>000633</line-number>
+ <table-name>z304</table-name>
+ <action></action>
+ <match-id>02810000999</match-id>
+ <user-name>ST. LOUIS,CLEMATIS MIRABELLA</user-name>
+ <patron-id>ID181776</patron-id>
+ <msg-code>5012</msg-code>
+ <msg-desc>Unsupported action ""</msg-desc>
+ </section-02>
+ <section-02>
+ <line-number>000633</line-number>
+ <table-name>z305</table-name>
+ <action></action>
+ <match-id>02810000999</match-id>
+ <user-name>ST. LOUIS,CLEMATIS MIRABELLA</user-name>
+ <patron-id>ID181776</patron-id>
+ <msg-code>5012</msg-code>
+ <msg-desc>Unsupported action ""</msg-desc>
+ </section-02>
KB 16384-36001 describes the cause of "Unsupported action".
In record 729 we see:
+ <section-02>
+ <line-number>000729</line-number>
+ <table-name>z308</table-name>
+ <action>REWRITE</action>
+ <match-id>02807009999</match-id>
+ <user-name>HILLAIRE,JIMMY LASALLE</user-name>
+ <patron-id>ID255468</patron-id>
+ <msg-code>5037</msg-code>
+ <msg-desc>Cannot update/delete record. Login record belongs to other patron</msg-desc>
+ </section-02>
As noted in KB 5716, "This message means that the LOGIN data in one of the ID records matches the Z308-KEY-DATA of an existing Z308. And this existing Z308 is for a different patron (that is, it is not the patron matched on based on the USER-REC MATCH-TYPE and MATCH-ID)." Four other KB records discuss specific instances of this "Login record belongs to other patron" error.
The next problem is "check_z308_duplicate routine failed" in record 826:
+ <section-02>
+ <line-number>000826</line-number>
+ <table-name>z308</table-name>
+ <action>WRITE</action>
+ <match-id>0293710999</match-id>
+ <user-name>Matthews,Natasha</user-name>
+ <patron-id>ID255498</patron-id>
+ <msg-code>5022</msg-code>
+ <msg-desc>check_z308_duplicate routine failed. Can not ins/upd record.</msg-desc>
+ </section-02>
This error is discussed in KB 5767.
Records 2119, 2240, 2413, 3849, 4412, 4426, 4513, 5339, 5586, 5843, 6056, etc., have the same "Cannot update/delete record. Login record belongs to other patron" discussed above.
The following grep shows that the majority of the input records *were* processed successfully:
aleph@alapp20(a20_1) ABC50> grep -c Successed p_file_20_report
99133
aleph@alapp20(a20_1) ABC50> grep -c 'Unable to process' p_file_20_report
157
(Since "Successed" and "Unable" occur about 5 times for each input record, this indicates about 19,000 records loaded successfully and 30 not loaded.)
Additional Information
PLIF
- Article last edited: 10/8/2013