Auto Accept Process Related - How to Manage 'Stuck' Reports ? (Doc ID 3063302.1)

Last updated on DECEMBER 23, 2024

Applies to:

Goal

Currently, when auto-accept E2B records are stuck, it is prudent to check 3 things in the safety report table to verify:

1. The SAFETY_REPORT. STATUS column should = 101 (Receive Message/ACK)
2. Locked_user_id= should be that of the Auto-Accept AG Service user (Auto Accept User).
3. Autoacceptprocess = null

Once confirmed on all three columns, the recommendation is to run the below update query as the Argus Schema owner after setting context (per Note 1320159.1: Oracle Argus Safety - How to Set Context For Back-end Activities)

This way the file is cleared from the Auto-Acccept queue. After the queue is cleared, these files are sent for manual entry.

But some instances occur when the Auto accept service again picks up the same file and accepts it which creates duplicate records.

Questions:

Q1) What causes the auto-accept service to pick the issue file and process it again?

Q2) What are the different scenarios or parameters to check if any file is stuck in auto accept queue?

Q3) Is there any specific time limit needed to wait for auto-accept service to pick up the files stuck there and piling up?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.