Oracle Identity Governance (OIG): How to TroubleShoot Data Issues in the 'Issue Audit Messages' Job (Doc ID 2961930.1)

Last updated on JULY 26, 2023

Applies to:

Goal

The Issue Audit Messages job is sensitive to performance issues when a backlog of data collects in the AUD_JMS table.  One of the known issues for this job is when a specific user has an issue in the audit tables due to a missing row or incorrect sorting of the audit messages, all audit messages for that user will get flagged as failed.  Any future messages for that same user will also be failed unless (or until) the earlier messages are successfully processed.  When dozens of users have problems, the backlog can get quite substantial and cause the job to fail or, in worst case, the server to go into a WARNING state.

This note provides a way to organize the data in AUD_JMS so that the processing of a specific (smaller) number of users can occur.  Customers can use this technique to isolate 'bad' users and then use the existing audit snapshot script to re-align those users to their current and accurate audit state.

Solution

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