My Oracle Support Banner

Concurrent Program "Purge Logs and Closed System Alerts" is not Purging Records from FND_LOG_MESSAGES (Doc ID 1276421.1)

Last updated on SEPTEMBER 08, 2020

Applies to:

Oracle Concurrent Processing - Version 11.5.10.2 to 12.1.3 [Release 11.5 to 12.1]
Information in this document applies to any platform.

Symptoms

Problem Statement:
On Oracle Application Release 11i/R12/R12.1

Concurrent request "Purge Logs and Closed System Alerts" does not purge records from FND_LOG_MESSAGES table, If FND_LOG_MESSAGES table does not having corresponding rows for transaction_context_id in table FND_LOG_TRANSACTION_CONTEXT.

Expected Behavior:
Expected to see that concurrent program "Purge Logs and Closed System Alerts" is purging records.

Steps to Reproduce:
The issue can be reproduced at will with the following steps:

1. Below SQL will confirm if FND_LOG_MESSAGES table is not having corresponding rows for transaction_context_id in table FND_LOG_TRANSACTION_CONTEXT.

SQL> select module, transaction_context_id from fnd_log_messages where transaction_context_id not in (select distinct TRANSACTION_CONTEXT_ID from FND_LOG_TRANSACTION_CONTEXT);

2. If Step 1 returns rows then run concurrent program "Purge Logs and Closed System Alerts". After successful run of concurrent program, above SQL should not return any rows and it should able to purge those records from FND_LOG_MESSAGES table which does not have corresponding rows for transaction_context_id in table FND_LOG_TRANSACTION_CONTEXT.

Changes

 

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
References


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