BATCH REPORT GENERATION AG Services - 0 Queued 0 Skipped, Reports are not being auto-generated.
(Doc ID 2157489.1)
Last updated on MARCH 01, 2023
Applies to:
Oracle Argus Safety - Version 8.0.1 and laterInformation in this document applies to any platform.
Symptoms
On Applications Oracle Argus Safety : 8.0.1
Auto-Generation AG Service (Report Generation Worker process) is not automatically generating expedited reports for cases (e.g. E2B Reports)
In addition, also noted that there are no records created in PDP_QUEUE_E2b table or BATCH_GENERATION_QUEUE.
Cases are correctly locked and have reports scheduled, so expectation is that reports should be auto-generated as the AG Services for Batch Generation, and Batch Generation Worker are all running fine.
Steps to reproduce:
1. Book in a reportable case.
2. Auto-schedule a report.
3. Lock the case
4. Close the case
5. Verify after sometime, the report is not auto-generated.
In the AG logs via C:\Program Files (x86)\Oracle\Argus\Log\ on the Transaction server no errors are reported, however no reports are picked up e.g.
04-Jul-2016, 05:27:07 >> Batch Report Generation > "C:\Program Files (x86)\Oracle\Argus\Argus Safety\AGProc.exe Batch Report Generation Batch Report Generation" stopped.
Changes
New Environment
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |