Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. p_file_20 creates duplicate patron records; barcode as match-point

    p_file_20 creates duplicate patron records; barcode as match-point

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers

     

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

     

    Description:
    With the most recent p_file_20 we find that already-existing patrons have been duplicated in our database. Is there a way to remove the PLIF applied yesterday and resubmit it?

     

    Resolution:
    The PLIF records were specifying the barcode (ID type 01) as the match-point. This campus was in the process of changing their barcode system and all of these users had received new barcodes. Since there was no match, p_file_20 created a new patron record.

    Since this consortium's z303, z308 and z353 contain records for 22 different ADM's, restoring these shared tables from 8 hours ago did not seem like a good idea.

    The SQLs used in diagnosing are shown below. The SQL delete's were generated by changing the "select count(*)" of each query to "delete". Note: the delete of the z305 needs to be last!

    The z111 also needed to be corrected. Since the z111 is at the ADM level, it is easier to regenerate it via p_manage_111 in the xxx50 than to try to correct it with SQL.

    abc50@ALEPH20> select count(*) from z305 where Z305_UPDATE_DATE = '20120731' and Z305_OPEN_DATE = '20120731';
    **** Hit return to continue ****

    COUNT(*)
    ----------
    855


    abc50@ALEPH20> select count(*) from sys50.z303 where z303_rec_key in (select substr (z305_rec_key,1,12) from z305 where Z305_UPDATE_DATE = '20120731' and Z305_OPEN_DATE = '20120731');
    **** Hit return to continue ****

    COUNT(*)
    ----------
    855


    abc50@ALEPH20> select count(*) from sys50.z308 where z308_id in (select substr (z305_rec_key,1,12) from z305 where Z305_UPDATE_DATE = '20120731' and Z305_OPEN_DATE = '20120731');
    **** Hit return to continue ****

    COUNT(*)
    ----------
    2392

    abc50@ALEPH20> select count(*) from sys50.z353 where substr (z353_rec_key,11,2) = 'ID' and substr (z353_rec_key,16,12) in (select substr (z305_rec_key,1,12) from z305 where Z305_UPDATE_DATE = '20120731' and Z305_OPEN_DATE = '20120731');
    **** Hit return to continue ****

    COUNT(*)
    ----------
    1710

     

    Note: In your set-up, you may have ALEPH z305's in the $usr_library addition to (or instead of) the xxx50 z305's in the xxx50 library. Those would also need to be deleted.

     

     


    • Article last edited: 12-Mar-2016
    View article in the Exlibris Knowledge Center
    1. Back to top
      • p_file_20 creates duplicate patron records; Aleph patron# as match-point
      • p_file_20 doesn't update Pincode / Barcode Verification
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      This page has no tags.
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved