Purging Data from Activity Processing Technical Tables

Introduction

The purging of activity processing (ACT) technical tables is implemented in the database as a PL/SQL package.

Package OHI_ACT_PURGE_PKG

This procedure purges tables related to activities.

procedure purge_act
( p_keep_days   in integer
, p_commit_size in integer := ohi_data_purge_pkg.g_con_commit_size
, p_purge_all   in boolean := true
);

Parameters

p_keep_days

This mandatory parameter specifies the number of days of history that is retained. Records created within the last p_keep_days are not purged, but the other records are purged. This means records between created_Date < = (sysdate - p_keep_days) are purged. `p_keep_days`cannot be less than 30.

p_commit_size

A large undo tablespace must be available to purge large data during the run. In a few cases where this is impossible or impracticable (for example, in managed cloud-based configurations with no direct access to the database), it is possible to limit the number of deleted records before a commit. However, setting the commit size parameter comes at the cost of performance. A smaller commit size generates more overhead. Higher commit sizes make the process faster but need more undo space in the database. Use of this parameter is optional.
The default value is 1000.

p_purge_all

If this optional parameter value is true, all data will be deleted except for records with the status IN, IP, and QD. If the parameter value is' false', only records with the status CO will be deleted. The default value for this parameter is true.

This purging job is included in the Auto Purge job and is used in its default state.