Core Concurrent Processing - EBS (MOSC)

MOSC Banner

Purging Concurrent Requests and associated tables manually

edited Nov 15, 2011 3:02PM in Core Concurrent Processing - EBS (MOSC) 25 commentsAnswered ✓
Hi,
I have a situation where the FND_CONC% and associates table have not been purged for a long time. See records counts below:

FND_CONCURRENT_PROCESSES     20,654
FND_CONCURRENT_REQUESTS     961,274
FND_CONC_REQUEST_ARGUMENTS     36,857
FND_CONC_STAT_LIST         0
FND_CONC_STAT_SUMMARY         0
FND_DUAL             4,870
FND_ENV_CONTEXT         3,522,509
FND_RUN_REQUESTS         27,474

In looking to trim small bites at a time, the FNDCPPUR process seems to want to take up to nine days to knock off the first  few records, where "few" can by any number from 1 to whatever I choose. As such, it does not seem like a viable way to purge these tables given their current neglected states.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center