I don't think we have anything official that would state the rows that we touch per blcli cleanup command. Probably better approach would be to either:
1. run the command and watch sql activity (either on the database or in the appserver.log by setting database class to debug)
2. file a ticket with support and if this is a valid request, then have them identify al the tables with the help of engineering.
Yes, you are right - debug mode on appserver-log would do the trick. Thank you.
1 of 1 people found this helpful
JobRunEvent -> DEPLOY_JOB_RUN_EVENT, JOB_RUN_EVENT
AuditTrail -> AUDIT_TRAIL
*Result -> JOB_RESULT
JobSchedule -> SCHEDULE
there are some more dependent tables that get touched there.
typically if you want to monitor progress you can look in DELETE_TASKS and you will get a status of where the cleanup is and how many rows it has deleted.
Thank you Bill. Some more insight...
I found out that there are some more "DELETE..."-tables two of which I could see some interesting data in - so if anybody is interested in...
DELETE_TASK_TYPES: contains a list of "all" six task types as they are described in the blcli-help for "Delete cleanupHistoricalData <objectName>"
DELETE_TASKS_STATISTICS: seems to contain some more details about the different cleanup tasks including table names (at least if there's something to clean up).
Additionally I opened a ticket with support and they openend an RFE to include information about tables being cleand into the log.