Configuring and Running the Offline Data Purge Operation

To run the offline data purge operation:

Note:

Before beginning the configuration, ensure that all the prerequisites are met.

Configure the OIM_OFFLINE_DATAPURGE Oracle DBMS scheduled job.

Table -17 lists the configurable parameters of the OIM_OFFLINE_DATAPURGE Oracle DBMS scheduled job.

Table -17 Configuration Parameters for OIM_OFFLINE_DATAPURGE DBMS Scheduled Job

Parameter	Description	Default Value
OIG Entity	This takes the following values: 1 for orchestration 2 for provisioning task 3 for reconciliation	NULL
Recon Entity
Purge Criteria	This takes the following values: 1 for purging purgeable events 2 for purging non-purgeable events 3 for all data	NULL
Purge Retention period (in days)	This indicates the retention period in days for the purge. Based on the value `recon_events.re_create`.	NULL
Orchestration Entity
Purge Criteria	This takes the following values: 1 for purging purgeable events 2 for purging non-purgeable events 3 for all data	NULL
Purge Retention period (in days)	This indicates the retention period in days for the purge. Based on the value `orchprocess.modifiedon`.	NULL
Prov Task Entity
Purge Criteria	This takes the following values: 1 OR 2 OR 3 for purging purgeable/non-purgeable/All data events	NULL
Purge Retention period (in days)	This indicates the retention period in days for the purge. Based on the value `'sch.sch_create`.	NULL

Replace the following attributes of the Oracle DBMS scheduled job with desired values by using the following syntax:

<OIM_ENTITY>: OIG entity type (1,2, or 3)
<PURGE_CRITERIA>: Purge criteria (1,2, or 3)
<RETENTION_PERIOD>: Retention period (in days)

SQL> BEGIN dbms_scheduler.set_attribute( name => 'OIM_OFFLINE_DATAPURGE', attribute => 'job_action', value => '
BEGIN oim_pkg_offline_datapurge.oim_sp_offline_dataprg_wrapper(p_oim_entity => <OIM_ENTITY>, p_purge_criteria => <PURGE_CRITERIA>, p_retention_period => <RETENTION_PERIOD>); 
END;'
 );
 END;
/

For example, in the following scenario, all the non-purgeable data for orchestration entity type that is older than 365 days is purged from the database.

SQL> BEGIN 
	    dbms_scheduler.set_attribute
	    (
	        name => 'OIM_OFFLINE_DATAPURGE',
	        attribute => 'job_action',
	        value => 'BEGIN oim_pkg_offline_datapurge.oim_sp_offline_dataprg_wrapper(p_oim_entity => 1, p_purge_criteria => 1, p_retention_period => 365); END;'
	    );
	END;
	/

Run the following SQL command to run the Oracle DBMS scheduled job:
```
SQL> EXEC dbms_scheduler.run_job('OIM_OFFLINE_DATAPURGE');
```
Run the following SQL command to track the purge operation progress by using the existing PL/SQL diagnostic logging and debugging tables:
```
SQL> SELECT * FROM diag_log ORDER BY 1 DESC;
SQL> SELECT * FROM diag_log_dtls ORDER BY 2 DESC, 1;
```

After successful completion of the offline data purge operation:

The active database tables show only the data that needs to be retained after the purge operation.
The parameter value of the OIM_OFFLINE_DATAPURGE DBMS scheduled job is reset to NULL.