Purging and archiving instance data
To increase dashboard efficiency and performance, purge instance data from the IBM® Business Monitor database and archive it to a directory on your IBM Business Monitor server. Only terminated instances can be purged and archived.
About this task
When instances are purged, you can optionally archive
those instances to a .csv file on the IBM Business Monitor server
file system. The purging and archiving are based on the timestamp
in the TERMINATION_TIME column of the top-level monitoring context
instance table. Any top-level instances that are terminated before
the specified purge timestamp are purged, along with all of their
child monitoring context instances.
Note: Generally, you can purge
and archive only terminated instances. If you must purge and archive
any active instances, you can run a SQL statement to update the TERMINATION_TIME
timestamp on those top-level instances so that they and all of the
corresponding child instances can be purged.
For example, suppose
you want to archive and purge instances from before the year 2000.
You would use the following SQL syntax (which, in this example, is
for DB2) to mark the active instances as terminated:
update modelid.mct_top-level-mc_version
set termination_time = '1999-01-01 00:00:00',
ab_termination_time = '1999-01-01',
ready_for_delete = 1
where ready_for_delete = 0
and your_deletion_criteria
If data
movement service is enabled, you would also need to update the data
movement service target table:update modelid.tgt_top-level-mc_version
set termination_time = '1999-01-01 00:00:00',
ab_termination_time = '1999-01-01',
completed = 1
where completed = 0
and your_deletion_criteria
You could
then archive and purge these instances.You can purge and archive instance data for a particular model version on a one-time basis, as described in the following procedure, or you can purge and archive instance data periodically using Monitor Scheduled Services.