Purging Data from Financial Technical Tables
Introduction
The purging of financial technical tables is implemented in the database as a PL/SQL package. This purging job is also included in the Auto Purge (disabled by default).
|
Package OHI_FIN_PURGE_PKG
ohi_fin_purge_pkg.purge_all
( p_keep_days in integer (1)
, p_commit_size (2)
);
Parameters
1 | 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 other records are purged.
This means records which are between created_Date < = (sysdate - p_keep_days) are purged. |
2 | p_commit_size
A large undo tablespace will have to be available for the duration of the run to purge a large amount of data.
For cases where this is impossible or impracticable, (for example, in managed cloud-based configurations where there is no direct access to the database) it is possible to limit the number of records that are deleted before a commit.
Setting the commit size parameter, however, comes at the cost of performance.
A smaller commit size generates more overhead.
Higher commit sizes make the process faster, but needs more undo space in the database. |