Oracle
Important:
To run massive_data_purge in Oracle, you must be logged in as the schema owner, not as SYSTEM or SYS.
Optimize purges data from database components in Oracle by calling a stored procedure from an Oracle database client. The procedure purges data by re-creating the database component and re-inserting the data you want to keep. With this approach, the purge operation always takes about the same length of time, regardless of the length of time between purges, so you can purge data infrequently (for example, about every three months). However, while frequent database purging will not speed up the time duration of the purge, you can improve the performance of the data purge operation by keeping fewer days of data.
To run Data Purge in Oracle
1. The stored procedure call is:
execute massive_data_purge;
2. Avoid aborting a data purge procedure because doing so can affect foreign key constraints. However, if the massive_data_purge procedure for Oracle fails or is aborted, call this stored procedure to restore all Foreign Key constraints:
declare l_execution_count integer;
begin
metadatapkg.execute_pending_sql (l_execution_count,
'MASSIVE_DATA_PURGE',
'Add Foreign Keys',
metadatapkg.cyes
);
end;
Important:
If the Analysis and Process Tracker database components are in separate schemas, the Data Purge must be executed in each schema separately.