RAR5.3 - Alert Generation background job repeatedly errors out

Question

Hello,
We have an Alert Generation job that we've set up to run daily on
PR2/150 strictly for the Transaction Usage Report. We do not
use Alerts so the only parameter we set for this job is "Generate
Action Log." The job will run anywhere from 2 to 4 hours before it
errors out. Every time this job, this process overflows its allotment
on the backend of 4GB and consequently creates a system dump. The job
is just too big.
We've reviewed the powerpoint "Risk Analysis and Remediation Alerts,
Jayne Gibbon, Director of GRC Support, August 15 2008"
This powerpoint basically says Alert Generation jobs should run every 1-
4 hours, otherwise they can get very large. We applied note 1015921 to
change the Last Run Date in order to decrease the size of the job. The
farthest we were able to set the Last Run Date back and have the alert
generation job run successfully was 2 minutes. This is unacceptable for
us as we need the jobs to at least run for 1 hour time periods.
What can we do to ensure our alert generation jobs complete
successfully in a manageable time period?
Any info or guidance would be greatly appreciated!
Jes Behrens
Edited by: Jes Behrens on Jan 20, 2009 10:47 AM

Answer 1

there seems to be a problem with the SID table of your master data. test it with RSRV and repair any errors.
if this doesn't help return to the forum