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

    Execution error of get_buf_docx.gnt in ue_01

    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23

    Description


    1. The ue_01 is failing
    2. The log file $data_scratch/run_e_01.xxx contains

     

    Execution error : file '/exlibris/aleph/a20_x/aleph/exe/get_buf_docx.gnt'

    Resolution


    Cause is a bad formatted bibliographic record in the Z00 table.

    The priority order in Z07 is not defined from the system number but from the Z07-SEQUENCE; the lowest one is the next record that will be managed from ue_01.

     

     

    To find the first system number that will be processed (that one that is corrupted) you could do this:
    1. Export in sequential format the Z07 records using the service Export Database Tables (file-03) service with Table to export= z07
    2. Login in to the server with ssh user aleph
    3. dlib XXXXX
    4. df1
    5. cut -b10-26 z07.seqaa | sort | more -1
    The line that is displayed is the Z07-SEQUENCE of the record that is crashing UE_01
    6. Search for the line in the z07.seqaa file with:
    grep line z07.seqaa|cut -b1-9 (line is a 15 characters length number )
    7. The number that is displayed is the system number that should be removed from z00 table.
    8. Contact Ex Libris support to delete the record from the database.

     

     

    • Additional Information

      Alternate solution

     

    1. connect with sqlplus to xxx01

     

    s+ xxx01

     

    2. identify the lowest z07_sequence

     

    select min(z07_SEQUENCE) from z07;
     

    MIN(Z07_SEQUENC
    ---------------
    199004080914253

     

    3. Search for the record number with that sequence:

     

    select z07_rec_key from z07
      2  where Z07_SEQUENCE = 199004080914253

     

    Z07_REC_K
    ---------
    000583276

     

     

    4. Ask Ex Libris to delete the corresponding z07 record and also the z00 record causing the problem

     

    5. Restart ue_01 process (util e/1)

     

    Note: you might need to stop the 'hanging' sub processes run_e_01_z0102.xxxxx and run_e_01_word.xxxxx first by executing util e/2 Stop Update Doc Index before your are able to restart the indexing background process (ue_01)

     

     

     

     

     

    • Article last edited: 12-Apr-2016