- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2025 04:10 PM
In yokohama how to destroy sys_rollback_sequence We are no longer able to delete records from the sys_rollback_sequence table using the Data Management Delete job. Based on the database footprint, this table currently occupies approximately 350.53 GB. For database compliance purposes, we need to remove these records. We would appreciate your assistance in facilitating the deletion of entries from the sys_rollback_sequence table.
Please help.
Solved! Go to Solution.
- Labels:
-
Full-Time
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2025 05:13 PM
Delete ACL on 'sys_rollback_sequence' table requires 'maint' role meaning you cannot delete any of the records and need to log a ServiceNow support case for deletion of records from this table.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0753001
If this helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2025 04:12 PM
Additionally i am getting error "The user does not have the necessary permissions to delete records from table sys_rollback_sequence"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2025 05:13 PM
Delete ACL on 'sys_rollback_sequence' table requires 'maint' role meaning you cannot delete any of the records and need to log a ServiceNow support case for deletion of records from this table.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0753001
If this helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
The sys_rollback_* tables will grow in size when you are running multiple delete jobs. This is expected behaviour and the sys_rollback_* tables are use for recovery when a item was deleted accidentally and needs to be recovered.
There is no way to target the sys_rollback_sequence table directly for a delete or cleanup action. There is a job "Clean Expired Rollback Contexts" that runs every hour and marks contexts as expired. The process calls a rollback reaper function that clears out 10k of those records at a time and cascade deletes the sys_rollback_sequence that are attached to the expired contexts.
Please make sure the job "Clean Expired Rollback Contexts" is running regularly.
Here are the other properties to configure the rollback cleanup.
https://www.servicenow.com/docs/r/yokohama/platform-administration/table-administration-and-data-man...

