sys_archive_log dependency with Archived tables ar_*SummaryThe Symptoms could be any or combination of these sys_archive_log continues to grow atleast a few GB every week and a Table cleaner is setup or scripts are executed to control the growth of sys_archive_logvery old Archive table ar_* records are not being destroyed eventhough the ar_* table records satisfy the Archive Destroy Rule conditions. These records dont have corresponding sys_archive_log entryReleaseSan Diego and Higher ReleasesInstructionsSince San Diego all archive destroy logic is directly dependent on every ar_ table record having a matching sys_archive_log record, so by deleting the sys_archive_log records, there is "orphaning" of the corresponding ar_* records. Hence such orphaned ar_* will never be destroyed. If the focus is on keeping sys_archive_log table growth under control, there is no need to setup table cleaner or any sort of deletion of sys_archive_log records. sys_archive_log records are automatically cleared out when the destroy rule is runIf old records from ar_* are not being destroyed because of the unavailability of corresponding sys_archive_log, then setup a table cleaner on such ar_* tables to delete those old records