Auditing
Auditing is set to the second highest OIM level, Resource Form.
Archiving and Purging
Yale will purge old recon data that is older than 90 days. Yale will not archive any of this data.
Purging of old recon data is accomplished via a custom PL/SQL routine that streamlines the OIM process. The coding was derived from the OIM procedure to ensure that we were deleting the data in the correct order and with the correct conditions applied. We took this step because we did not want to incur costs of moving the data to an archive table, then deleting that table. We also found that we had problems archiving sometimes because the system could not get an exclusive lock on a table in order to drop indexes.
 | This routine must be re-evaluated after every upgrade to ensure it's accuracy. The code is based on code found in OIM_SP_ReconArchival. |
The procedure deletes all data from a recon table if the corresponding rce record (linked via rce_key) was created more than 90 days ago:
DELETE /*+ PARALLEL NOLOGGING */
FROM rca
WHERE rce_key IN (SELECT rce.rce_key
FROM rce
WHERE rce_status IN ('Event Close', 'Event Linked')
AND rce_create <= TRUNC(SYSDATE) - days /* days defined earlier */
AND rce.rce_key = rca.rce_key);
The procedure deletes from these tables, in order:
- rca
- rcb
- rcd
- rch
- rcp
- rcu
- rpc
- rcm
- rce
A commit is done after all data has been deleted successfully.
The procedure is scheduled using Oracle's Scheduler and is executed at 2:05am everyday. All resources are quiesced between 2am and 2:30am to minimize updates on the recon tables during the purge.