Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    v21/v22 cir-78 runs longer than previously, not removing z309 records it should

     

    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

     

    Symptoms    
    After upgrading to Aleph version 21 or 22, the cir-78 Service (Circulation Logger Clean Up) runs for longer than it did previously and is not removing all the z309 records which it should.

     

    Defect Status    
    Modification made to step 1033 in upgrade_express_2001_2101 kit. 
    v20 customers should get the new kit (version, 1..06), made available on ftp server Sep 7, 2015; 
    v21/v22 customers should follow steps below. 

    The Aleph 20 to 21 conversion added Z309_REQUEST_NUMBER and Z309_PHOTO_REQUEST_NUMBER fields to the z309 record, initializing them to a value of NULL. But the cir-78 Service, in selecting candidates for deletion, checks for a value of 0. Thus, after going to version 21/22, cir-78 will not delete z309 records created under version 20 (and converted to 21/22 by Upgrade Express). 

    If a "To Date" several weeks/months in the past was specified in the cir-78 runs under version 20, the number of z309s carried over may have been quite large and the effect upon cir-78 may have been correspondingly great. If not, there will not have been much of an effect, and it may not even be noticed. Use the SQL in Additional Information below to count the number of affected records. 

    Solution for sites who have already upgraded to version 21/22: 

    * Back up the z309 table with the file-03 Service (in case it needs to be recovered) 
    * Outside library’s business hours run the following SQL command**: 
    > s+ xxx50 
    SQL> update z309 set Z309_REQUEST_NUMBER = 0 where Z309_REQUEST_NUMBER is NULL; 
    SQL> update z309 set Z309_PHOTO_REQUEST_NUMBER = 0 where Z309_PHOTO_REQUEST_NUMBER is NULL; 
    SQL> commit; 

    ** Note: If the SQL query in Additional Information shows that there are many (> 100,000) z309 records to be updated, then do the following SQL updates instead of the above: 

    SQL> update z309 set Z309_REQUEST_NUMBER = 0 where Z309_REQUEST_NUMBER is NULL and rownum < 100000 ; 
    SQL> update z309 set Z309_PHOTO_REQUEST_NUMBER = 0 where Z309_PHOTO_REQUEST_NUMBER is NULL and rownum < 100000 ; 
    SQL> commit; 

    This SQL can be activated several times until the whole table is updated.

     

    Replication Steps    
    Run cir-78.

     

     


    • Article last edited: 28-Feb-2016
    • Was this article helpful?