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

    ue_01: Update z98 from z980 ... INTERNAL LENGTH NOT CORRECT!!

    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct; Direct; Local;

    Problem Symptoms:
    The ./xxx01/scratch/run_e_01 log has this error:

        HANDLING DOC NO. - USM01.002143808 10:09:11
      Update z98 from z980 : 007000054464
      INTERNAL LENGTH NOT CORRECT!! 007000054464
      * Execution error : file '/exlibris/aleph/a18_1/aleph/exe/compress_data_ads.gnt'
      error code: 114, pc=0, call=1, seg=0
      114 Attempt to access item beyond bounds of memory (Signal 11)

    * If ue_01 is restarted, it may process a few records but soon stops with the error on the same or a different doc number.

    z98 data corrupt

    Contact Ex Libris Support to delete or correct the corrupted z98/z980 records.

    Additional Information

    Article ue_01: "INTERNAL LENGTH NOT CORRECT" ... compress_data_ads.gnt"  is also relevant.

    1. The ue_01 log had the same z98 / z980 number in every case:


    (The first three digits are the "W-nnn" number of the word index.) Checking the fcl01 tab00.eng, we saw that "W-007" is "WNO".

    2. Use util f/4 to determine that the problematic word, "21cm" in the example

      enter file name (or q to exit) z97
      new key = K, exit = Q, continue = RETURN
      > k
      key 1 = 1, key 3 = 3
      > 3
      enter start word position nnnnnnnnn
      > 000054464
      -21cm -000054464-000054464

    3. search for "wno = 21cm" in the GUI (4004 hits) and save the results on the server.

    4. Use the following sql to determine that there was 1 z980 and 7 Z98 records with this word number:
      SQL> select * from z980 where z980_rec_key = '007000054464';
      SQL> select * from z98 where z98_rec_key like '007000054464%';

    5. as an extra precaution back up the Z98 and Z980 using p_file_03

    6. Ask Ex Libris Support to use SQL to delete the problem records (-- see the article:  ue_01: "INTERNAL LENGTH NOT CORRECT" ... compress_data_ads.gnt"   in this regard).

    7. Restart ue_01 to process the accumulated Z07s

    8. Use the saved GUI search set as input to p_manage_40 (to re-index the records containing "21cm" in a note field).


    • Article last edited: 10/8/2013