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. ALEPH 20: patron record created with a blank record key

    ALEPH 20: patron record created with a blank record key

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Description:
    We recently found in our z303 table a record with a blank in the z303_rec_key. There are no other characters in the rec_key.

    It was created on 3/21/2010 which is the Sunday of the weekend that we converted from Aleph version 19 to 20.
    I am unable to call the record up in the GUI by patron name, keyword, barcode, or patron ID.
    The z303 record has "Law ILL Unit" as the Z303-NAME.
    There are twelve z304 rows associated with this record and these have an e-mail address of yifatl@exlibris.co.il.
    I also find 2 rows in z308.

    I can't call it up in the GUI and can't figure out how to determine if I have all the pieces to delete it with SQL.
    I'm afraid it will come back to haunt us during future upgrades.

    Resolution:
    I find in the v20 demo library tables that there is a USR00 patron record with:
    "Law ILL Unit" as the z303_name,
    "yifatl@exlibris.co.il" as the z304_email_address, and
    "USM50-ILL_LA" as the z303_rec_key.

    It seems that this record has somehow become connected to your ABC patron file. You may want to check in the ABC40 ILL library for z410 records with a blank z410_id and z416 records with a blank z416_requester_id.

    I think you should use SQL to delete the z303, z304's, and z308's you have found. In addition, you should check for z305's and z353's:

    SQL> select z305_rec_key from z305 where z305_rec_key like ' %';

    SQL> select z353_rec_key from z353 where z353_id = ' ';

    and delete any of those as well.

    You should back up the affected tables, using p_file_03, before doing any such deletions.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Aleph 20 System Administration Guide has obsolete reference to aleph_conf_create
      • Aleph 20: rep_change 3437 & Circulation Logger Clean Up (cir-78)
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 20
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    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