Manually purging summary table data

You cannot automatically purge the summary table data for IBM® Sterling Control Center Monitor release prior to v6.1.1. This section provides instructions to manually purge summary table data.

TIP to manually purge summary table data

Even if your IBM Sterling Control Center Monitor version does support purging of summary table data and you’ve allowed more summary table data to accumulate than you now want to keep, it’s recommended to perform a manual purge, once, before turning this ability in IBM Sterling Control Center Monitor.

Database tables with summary data are as follows:
  • ROLL_UP
  • CC_PROCESS
  • CC_PROCESS_DVG
  • CC_FILE_TRANSFER
  • CC_FILE_TRANSFER_DVG
Note: If you're not using DVGs (Data Visibility Groups), no data will be written to CC_PROCESS_DVG orCC_FILE_TRANSFER_DVG, which leaves only three tables to maintain.

If you are using DVGs, pick a date that represents the oldest summarization data you want to keep, for example May 19th, 2017.

ROLL_UP is straight forward to truncate because DATE_TIME, the column you need to reference in SQL could be example:

DELETE FROM ROLL_UP WHERE DATE_TIME < '2017-05-20'
For other SQL you need to convert a string to a date in either Oracle, DB2, or MSSQL SQL. Perform this SQL in the following order:
DELETE FROM CC_PROCESS_DVG WHERE PROCESS_ID IN (SELECT PROCESS_ID FROM CC_PROCESS WHERE 
STARTED < your date)
DELETE FROM CC_PROCESS WHERE STARTED < your date)
DELETE FROM CC_FILE_TRANSFER_DVG WHERE FILE_TRANSFER_ID IN (SELECT FILE_TRANSFER_ID FROM
CC_FILE_TRANSFER WHERE STARTED < your date)
DELETE FROM CC_FILE_TRANSFER WHERE STARTED < your date)