on 07-07-2009 7:14 PM
Hello Experts...
Recently we had a small crisis in XI that generated LOTS of alerts.
Now the RSALERTPROC report is failing with a SHORT-DUMP with a NO-ROLL or SYSTEM_NO_MEMORY exception. That is, it doesn't have enough memory available to run after a certain point.
I have tried to run it using very short delete periods like one day but it still short dumps.
Is there a way to tell it to commit every certain number of processed alerts like in other reorganizing reports?
Otherwise, what would be the best strategy short of asking the BASIS guys for humongous ABAP memory allocation?
Please help!!!!
-Sam.
up!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok We fixed this.
I had to use a binary search type of job scheduling (scheduling the jobs to cover different date ranges seeking the date ranges that made the jobs dump) until found the conflictive dates, then cleaned up outside those dates in bulk and used a finer scheduling (per day) in the conflictive date ranges until all the alerts were gone.
-Sam.
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.