- Article Type: General
- Product: Aleph
- Product Version: 20, 21, 22, 23
Desired Outcome Goal:
Diagnose messages such as the following in a server, daemon, or batch-job log:
Execution error : file '/exlibris/aleph/a22_1/aleph/exe/xxxxxxx.gnt'
error code: 114, pc=0, call=1, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)
The error can be caused by certain data being incorrectly processed by certain programs; by general program defects; or by lack of memory.
1. Search Salesforce for the specific "xxxx.gnt" name, such as: "expand_doc_bib_avail.gnt". If no luck, then:
2. Is the error reproducible:
* in the case of a GUI crash, does performing the same activity on the same record result in the same crash?
* in the case of a ue_nn gnt error, when ue_nn is restarted does it crash on the same record (as seen in the run_e_nn... log file)? (The record ue_nn was processing at the time the error occurred is the record number seen in the "HANDLING DOC NO" line preceding the .gnt error line.)
* in the case of a batch job, does a rerun of the job crash on the same record*?
If any of the above is true, compare the record to other records which do not result in the .gnt error.
Open a Salesforce Case describing the findings of your comparison.
* This may require the addition of diagnostics to the batch program in order to pinpoint which record it is stopping on. (This would need to be done by Ex Libris Support.)
3. Does the error always occur in the same "xxxx.gnt" program? If the gnt occurs in *different* programs, with different records, the problem may be a lack of memory. See Article 000045277 (" ue_21 crashes with "Execution error ... Attempt to access item beyond bounds of memory"") as an example of such a case. (Link below.)
Article link: ue_21 crashes with "Execution error ... Attempt to access item beyond bounds of memory"
Note: If the gnt error code is 115 ("Unexpected signal") rather than 114 "Attempt to access item beyond bounds of memory", that problem can be caused by a shutdown of the server or daemon by, for instance, a system shutdown. If that is not the cause in the particular case, then diagnose following the above Procedure.
See also, Article 000046915 (How to diagnose "Execution error: … Attempt to access item beyond bounds of memory" error)
Category: System Management (500)
- Article last edited: 7-Mar-2016