Archive Log Table Records Not being Destroyed - Known Error

Archive Log Table Records Not being Destroyed Description This issue is caused due to an invalid null check when adding sys_ids to the tableMap for destroying. This is fixed in Utah Patch 2.

Steps to Reproduce

1. Create an archive rule for any table.

2. Run the archive rule and make sure the records are moved from the base table to the ar_ table.

3. Create a destroy rule for this ar_ table.

4. Run the destroy rule.

Notice that destroy completes just fine, has the count of the number of records destroyed, and sys_archive_log records are moved to sys_archive_destroy logs. But the records are not deleted from the ar_ table.

Workaround The work around for this is to run the below script for the affected ar_ table which will destroy/delete records for that table. The script also makes sure that there is a destroy rule for the ar_ table and the archive_duration is considered in the query while destroying records.

Things to change/update as needed:

We can update AR_TABLE const to the ar_ table which needs records to be destroyed. The ADD_DAYS const is do a deletion in range based on the sys_created_on and can be changed/updated as seen fit.