Why was Schedule Job "Table Cleaner" disabled by system during our Xanadu to Yokohama upgrade?

[John Krueger]

Why was Schedule Job "Table Cleaner" disabled by system during our Xanadu to Yokohama upgrade?

We upgraded 4 instances staggered in July, August, September and all had the Table Cleaner job disabled by 'system' at 01:00:07 am during our upgrade.  It was not automatically activated after that, and we just happened to notice it was not running.

[John Krueger · Accepted solution]

→ From Yokohama, by DEFAULT the Legacy Table Cleaner job is no longer utilised and is replaced by the Multiple Threaded Table Cleaner functionality
→ As a part of the Multiple Threaded Table Cleaner functionality below jobs are now used for cleaning the records

☞ JOB : Scheduler For All DMJobs , is utilized for the scheduling the Data Management related jobs

☞ JOB : com.glide.dm_job.table_cleaner.TableCleanerProducer , will trigger and produce units of work (chunks) that will then be consumed / executed to delete/clean up records from tables according to rules defined in the instance (sys_auto_flush / sys_dm_job etc.). In simpler terms: it schedules and slices up the cleanup work.

☞ JOB : com.glide.dm_job.table_cleaner.TableCleanerConsumer , will trigger and pick the chunks created by the Producer and carry out the deletion of the records.