My Oracle Support Banner

How To Run Purge Obsolete ECX Data (FNDECXPR) (Doc ID 2198322.1)

Last updated on OCTOBER 02, 2020

Applies to:

Oracle XML Gateway - Version 12.1.3 to 12.2 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Goal

Current sizes of the ECX tables:

SQL> select segment_name "Table", round(bytes/1024/1024) "Size(MB)" from dba_segments where segment_name in (
'ECX_ERROR_MSGS'
,'ECX_MSG_LOGS'
,'ECX_OUTBOUND_LOGS'
,'ECX_EXTERNAL_RETRY'
,'ECX_INBOUND_LOGS'
,'ECX_EXTERNAL_LOGS'
,'ECX_OXTA_LOGMSG'
,'ECX_DOCLOGS'
) order by 2;

Table Size(MB)
-------------------------- ----------
ECX_EXTERNAL_LOGS 0
ECX_EXTERNAL_RETRY 0
ECX_OUTBOUND_LOGS 0
ECX_INBOUND_LOGS 474
ECX_MSG_LOGS 521
ECX_ERROR_MSGS 892
ECX_OXTA_LOGMSG 960
ECX_DOCLOGS 11071

Q1. What is the best approach to scheduling the purge program to purge data from mentioned tables?
Q2. What parameter should be used for "Purge Obsolete ECX Data (FNDECXPR)"?

The request has the following arguments to submit it:
~~
Transaction Type:
Transaction Subtype:
From date:
To date:
Commit_Frequency:

Solution

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
Goal
Solution


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