Troubleshooting ARUPDATE Abended Job Staying in Queued Status Even After Restart
(Doc ID 865335.1)
Last updated on OCTOBER 02, 2023
Applies to:
PeopleSoft Enterprise FIN Receivables - Version 8.8 to 9.2 [Release 8.8 to 9]PeopleSoft Enterprise SCM Billing - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.
Purpose
When ARUPDATE abends with any error. In this specific instance, ARUPDATE abended because of deadlocks on the database, and the user resolved the database side of the issue. Now navigate back to the child process, AR_PGG1, and checked the radio button, restart request, and hit OK. The job instead of restarting went into QUEUED status.
How to restart ARUPDATE so that it will go past the abended step?
Troubleshooting Steps
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Troubleshooting Steps |
| References |