- Article Type: General
- Product: Aleph
- Product Version: 17.01
When we run p_manage_35, we see this at the end of the batch job log:
Exiting due to job suspension.
The $data_scratch/p_manage_35.err file has this:
FAILURE Mon Dec 19 20:28:44 EST 2005 ==================
b_manage_35_a: Retrieve Failure
Job Suspended !!!
To identify this error in your log files use the command:
grep "FAILURE Mon Dec 19 20:28:44 EST 2005" $data_scratch/*.log
And in $data_scratch/p_manage_35_a_3.log we see:
34035 READING DOC 000634034 AT 20:23:41
35036 READING DOC 000635035 AT 20:26:21
How can we solve this?
Looking into the p_manage_35 log, we can see that the segmentation fault has occurred both times in processing a specific record.
We enabled diagnostics to show the key of each record it processes. This showed that it was bombing on a record with lengthy garbage in the 245 field.
When that record was edited to remove the garbage, the job ran OK.
- Article last edited: 10/8/2013