@soodn   I can see that our GCS team has provided the below information in ticket SR-B7925:

Please find response from product team 

Q1.. Is there an OOTB Job scheduler available for the cleanup of the two tables- pr_data_corr_email and pr_history? If not, kindly guide us how to configure purging on these tables as we see these tables occupying large size. A1. please refer the below doc to setup archival and purge activity for the ootb tables https://pegaks.com/how-to-archive-purge-old-work-items-pega-8/

Q2. Can you please provide the list of tables that pyClusterAndDBCleaner job scheduler is responsible for the cleanup. A.2 Please refer below doc to know the responsible tables for pyClusterAndDBCleaner https://docs-previous.pega.com/system-administration/87/node-and-cluster-default-job-schedulers?

Please find the list of tables the job is responsible for cleaning up, for any specific details please check the job activity.

• Remove provisional nodes table data.pr_data_admin in PegaDATA.
• Remove old entries from below tables
• data.pr_log in PegaDATA.
• data.pr_log_systemstate in PegaDATA.
• data.pr_log_batchid_generation in PegaDATA.
• Purge old System-Locks in table data.pr_sys_locks and data.pc_pegatask in PegaDATA.
• Purge old events in pc_events
• Purge old items in pc_pegatask
• Purge old items from pr_sys_statusdetails
• Purge old items from pr_log_systemstate
• Purge old items from table rules.pr_selectquerylog in PegaRULES.
• Remove old entries from table data.pr_log_jobs_scheduler in PegaDATA.
• Remove old entries from table data.pr_log in PegaDATA.
• Purge old test cases data from pr_data_testcaseresults and old test suite data from pr_data_testsuiteresults
• Purge health check data instances from pr_data_healthcheck
• Purge old rule coverage data from pr_data-rulecoverage_results
• Purge old broken items data from pr_sys_msg_qp_brokenitems

Update provided by GCS 30 September:

 we do not have any OOTB activity for DB table cleanup for the two tables but you could create a Job scheduler to clean up the tables based on the load the you are getting.

• pr_data_corr_email
• pr_history

*** Update 16 October ****

 Answer: 

We do not have any OOTB activity for  pr_data_corr_email and pr_history tables, but you could create a Job scheduler to clean up the tables based on the load the you are getting.

Full reply in support ticket: 

Please find the list of tables the job is responsible for cleaning up, for any specific details please check the job activity. Remove provisional nodes table data.pr_data_admin in PegaDATA. Remove old entries from below tables pr_perf_stats data.pr_log in PegaDATA. data.pr_log_systemstate in PegaDATA. data.pr_log_batchid_generation in PegaDATA. Purge old System-Locks in table data.pr_sys_locks and data.pc_pegatask in PegaDATA. Purge old events in pc_events Purge old items in pc_pegatask Purge old items from pr_sys_statusdetails Purge old items from pr_log_systemstate Purge old items from table rules.pr_selectquerylog in PegaRULES. Remove old entries from table data.pr_log_jobs_scheduler in PegaDATA. Remove old entries from table data.pr_log in PegaDATA. Purge old test cases data from pr_data_testcaseresults and old test suite data from pr_data_testsuiteresults Purge health check data instances from pr_data_healthcheck Purge old rule coverage data from pr_data-rulecoverage_results Purge old broken items data from pr_sys_msg_qp_brokenitems

**************

If all questions are answered please update this forum question  and mark with Accepted solution.