FND_LOG_Messages

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

FND_LOG_Messages

syed raza
Hi Imran,
I want to know that if we purge the following tables is there any effect in my EBS 12.2.4
FND_EXCEPTION_NOTES;
FND_OAM_BIZEX_SENT_NOTIF;
FND_LOG_METRICS;
FND_LOG_UNIQUE_EXCEPTIONS;
FND_LOG_EXCEPTIONS;
FND_LOG_MESSAGES;
FND_LOG_TRANSACTION_CONTEXT;
FND_LOG_ATTACHMENTS
 As in the above tables FND_LOG_MESSAGES have 300Gb data and so can we remove these table without taking the backup
Reply | Threaded
Open this post in threaded view
|

Re: FND_LOG_Messages

ErmanArslansOracleBlog
Administrator
Normally purging activity purges all messages up to the specified date,except messages for active transactions (new or open alerts, active ICX sessions, concurrent requests, and so on).

Basically, your logs and alerts wişll be purged.

The messages and logs related with the active transactions will not be purged.. (still you should take a backup of these tables before purging)

I suggest you to read and follow -> Purging Strategy for E-Business Suite (Doc ID 732713.1)

This note is applicable for EBS 12.2, too.

To purge these tables, you will run "Purge Logs and Closed System Alerts" concurrent program.. (both for fnd_log_messages and other tables in the list)

If the following tables are very big, you can even truncate them in the given order:

FND_EXCEPTION_NOTES;
FND_OAM_BIZEX_SENT_NOTIF;
FND_LOG_METRICS;
FND_LOG_UNIQUE_EXCEPTIONS;
FND_LOG_EXCEPTIONS;
FND_LOG_MESSAGES;
FND_LOG_TRANSACTION_CONTEXT;
FND_LOG_ATTACHMENTS

Note that: Truncating will lower the High Water Mark (HWM) on the tables allowing for more efficient execution against the tables.