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. ue_01 generates numerous archive log entries, which fill up disk

    ue_01 generates numerous archive log entries, which fill up disk

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

    Description:
    Our exlibris1/aleph1 directory suddenly filled up to 96% in the last few hours.

    The archive logs were being generated every two minutes. After some troubleshooting, I saw that our ue-01 queue was very large and records were being processed every few seconds. I stopped ue-01 to make sure that was the problem, and indeed, the log generation stopped.

    We have run no major jobs in the last 24 hours, no loading of records, no deletions, etc.

    It appears that the ue-01 is indexing our entire database, since the records are sequential - it appears to be halfway through (we have about 350,000 records, and it's on #103434). I have no idea what instigated this.

    Resolution:
    Looking at the $data_scratch/run_e_01.21291 log, I see that ue_01 is *not* processing every record:

    HANDLING DOC NO. - 000103662 21:37:34
    HANDLING DOC NO. - 000103663 21:38:06
    HANDLING DOC NO. - 000103668 21:38:36
    HANDLING DOC NO. - 000103693 21:39:05
    HANDLING DOC NO. - 000103773 21:39:37
    HANDLING DOC NO. - 000103830 21:40:06
    HANDLING DOC NO. - 000103879 21:40:38
    HANDLING DOC NO. - 000103892 21:41:10
    HANDLING DOC NO. - 000103925 21:41:42


    The records it's processing are updates sent to it by ue_08:

    sun01-M505=ABC01>>grep 000103668 *e_08*
    run_e_08.21291:Update doc - 000103668
    run_e_08.21291:Update doc - 000103668


    This grep of the Aug. 20 run_e_08.5595 log shows that ue_08 produced 17,355 indexing requests (z07's):

    sun01-M505=ABC01>>grep -c Update run_e_08.5595
    17355


    And the Aug. 28 run_e_08.21291 log shows 6,525:

    sun01-M505=ABC01>>grep -c 'Update doc' run_e_08.21291
    6525


    I also see that all the z07's have been processed:

    SQL-ABC01> select count(*) from z07;
    **** Hit return to continue ****

    COUNT(*)
    ----------
    0


    I see that /exlibris1 now haS 1.6 gig (15%) available.


    Looking at the run_e_08 logs, this ue_08 activity was the result of the update of authority records whose headings occur in many bib records, such as these:

    BIB Z01 : ABC01 - SUL LJEWISH ETHICS
    AUT DOC : ABC12 - 000021825

    BIB Z01 : ABC01 - SUB LUNITED STATES BIOGRAPHY DATABASES
    AUT DOC : ABC12 - 000008033


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • UE_01 failing: Update z98 ; "INTERNAL LENGTH NOT CORRECT"
      • ue_01 gets "end-of-file on communication channel" errors
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 15.2
      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