Skip to main content
Ex Libris Knowledge Center

ue_01: Execution error : file '.../exe/compress_data_ads.gnt'

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


Since a large load of records last night ue_01 seems to be hanging. If we stop/start it, it will process a few (sometimes 100+) records, then stop again.

We see that each of the run_e_01 logs ends with a compress_data_ads.gnt error:

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)

Resolution:

NOTE:
KB 8192-2045 (see SmartLink below) discusses the case where the compress_data_ads.gnt has occurred in conjunction with the "INTERNAL LENGTH NOT CORRECT!!" message. Though we do not see that message in these current run_e_01 logs, we *do* see that in each case the error is preceded by the following message:

Update z98 from z980 : 001000760959


And we see that word 000760959 is "behaviour":

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
000760959
-behaviour -000760959-000760959


enter file name (or q to exit) z97

new key = K, exit = Q, continue = RETURN
k
key 1 = 1, key 3 = 3
1
enter start word position TTTTTTTT
behaviour
-behaviour -000760959-000760959
-behaviour' -003229342-003229342
-behaviour-related -018182007-018182007
-behaviour/ -000760960-000760960
-behaviour/robert -012393468-012393468


A search for wrd=behaviour in the OPAC shows *no* hits on "behaviour" itself:

1 behaviory
1 behavioryouth
behaviour <-----------
2 behaviour'
1 behaviour-related
2 behaviour/
1 behaviour/robert
11096 behavioural


This is wrong.

We would need the numbers of the bib records containing the word "behaviour" in order to reindex them later. We were able to get these by doing a search for "behaviour" on the Test server, saving that result-set to the server, and ftp-ing it to Prod.

The site had been in the process of setting up the z970 synonyms and there was a z970 record for "behaviour" --> "behavior". Since it seemed that this could somehow be involved in the problem, we deleted the z970 records by doing util a/17/1.


As in KB 8192-2045, we needed to delete the z980 and z97 records:

(Note: fcl03 is a parallel library containing the Word indexes for fcl01, via LS.)

fcl03@ALEPH0> delete from z980 where z980_rec_key = '001000760959';

1 row deleted.

fcl03@ALEPH0> delete from z97 where Z97_WORD = 'behaviour';

1 row deleted.

[Do not do the preceding without consulting Ex Libris Support.]


This SQL showed that no z98's were involved:

fcl03@ALEPH0> select count(*) from z98 where z98_rec_key like '001000760959%';

no rows found

I then ran p_manage_40 for fcl01, using the ($aleph_scratch/)behaviour file from the Test server as input.

The job created z07s, which ue_01 successfully reindexed.

In the case of a Test server (or if the above doesn't work on a Production server) running manage-01 to rebuild the Words tables (and reinitialize the z980) will always work.

Additional Information


In the case of a Test server (or if the above doesn't work on a Production server)  running manage-01 to rebuild the Words tables (and reinitialize the z980) will always work.  

See also Article  ue_01: "INTERNAL LENGTH NOT CORRECT" ... compress_data_ads.gnt"  and 
 KB 8192-2045 / Article  ue_01: Update z98 from z980 ... INTERNAL LENGTH NOT CORRECT!!  .

Category: Background processing


  • Article last edited: 8/10/2015