Peoplesoft Error: All Processing Suspended: Restart OPRID=PS, RUNID=RUN01, PI=5000(108,503)
All Processing Suspended: Restart OPRID=PS, RUNID=RUN01, PI=5000(108,503)
What is this about and what should be done?
This error can occur when Application Engine programs are restartable and run via the Process Scheduler, and the last run was No Success - And an attempt re-run, rather than re-start will produce error as well
The cause of this message is that previously this same AE program was run using the same OPRID=PS & RUNID=RUN01. It was not Successful on initial run, and now an attempt to RUN the same program has occurred, instead of an attempt to RESTART the original that failed.
Whether this error Happened in Development???
This message happened while the Customer was in Development phase of this AE program. It could have happened when this AE was in Production as well. However, what to do would have completely different emphasis depending on if this happens in Development or Productions.
During the development cycle, we would expect that this AE would have to run many times before it runs to Successful completion as we expect. So there could be a good number of times this would need to run, and most likely not all will be Successful.
Have two choices here,
1) Use a different run control each time, ie, RUN02, RUN03, RUN04 etc. or
2) Remove the row from PS_AERUNCONTROL like this;
DELETE FROM PS_AERUNCONTROL WHERE PROCESS_INSTANCE=5000
This will free up the RUN01 run control to be used again, with same OPRID & AE program.
Whether this error Happened in PRD???
If this program were in Production - we would NOT want to just clear out the run control! With No Success AE programs, the recommended behavior is to look at logs and/or trace files, figure out what the problem was and fix the problem. Then do a Restart of the same Process Instance. This should be done via the Process Monitor, if the program ran through a Process Scheduler, and if the AE program was run outside the Process Scheduler, be sure the psae command parameters include the same OPRID RUNID & -I PROCESS_INSTANCE as was the original run - This will cause the program to start where it left off, and once the program goes to Success, the row is removed from PS_AERUNCONTROL automatically.
What is this about and what should be done?
This error can occur when Application Engine programs are restartable and run via the Process Scheduler, and the last run was No Success - And an attempt re-run, rather than re-start will produce error as well
The cause of this message is that previously this same AE program was run using the same OPRID=PS & RUNID=RUN01. It was not Successful on initial run, and now an attempt to RUN the same program has occurred, instead of an attempt to RESTART the original that failed.
Whether this error Happened in Development???
This message happened while the Customer was in Development phase of this AE program. It could have happened when this AE was in Production as well. However, what to do would have completely different emphasis depending on if this happens in Development or Productions.
During the development cycle, we would expect that this AE would have to run many times before it runs to Successful completion as we expect. So there could be a good number of times this would need to run, and most likely not all will be Successful.
Have two choices here,
1) Use a different run control each time, ie, RUN02, RUN03, RUN04 etc. or
2) Remove the row from PS_AERUNCONTROL like this;
DELETE FROM PS_AERUNCONTROL WHERE PROCESS_INSTANCE=5000
This will free up the RUN01 run control to be used again, with same OPRID & AE program.
Whether this error Happened in PRD???
If this program were in Production - we would NOT want to just clear out the run control! With No Success AE programs, the recommended behavior is to look at logs and/or trace files, figure out what the problem was and fix the problem. Then do a Restart of the same Process Instance. This should be done via the Process Monitor, if the program ran through a Process Scheduler, and if the AE program was run outside the Process Scheduler, be sure the psae command parameters include the same OPRID RUNID & -I PROCESS_INSTANCE as was the original run - This will cause the program to start where it left off, and once the program goes to Success, the row is removed from PS_AERUNCONTROL automatically.
What should you do if the offending Process Instance (that had the error occur) can not be restarted in Process Monitor (the Restart button is greyed out)?
ReplyDeleteCan I delete the appropriate row from PS_AERUNCONTROL and then restart the subsequent process that attempeted running afterwards?