IEX: Score History Purge Concurrent Program Parameters

(Doc ID 302164.1)

Last updated on AUGUST 18, 2016

Applies to:

Oracle Advanced Collections - Version 11.5.10.2 to 12.1 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.

Goal


1. The IEX_SCORE_HISTORIES table is extremely large and grows quickly. Would using the IEX: Score History Purge request under responsibility = Collections Forms Administrator concurrent program increase tablespace?  What information needs to entered for the four parameters:

a) Score Object ID
b) Score object Code
c) Request ID
d) Save Last Run

In Release 12, there are additional parameters:

Truncate all Data
Score Object ID
Score object Code
From Date
To Date
Request ID
Save Last Run
Batch Size

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms