Deployment Guide

If the DB2 archival logging is enabled, online data purge can be configured without any further steps.
Notice that data purge produces lots of database transactions, and transaction logs will be archived, so a
proper backup plan must be in place (backup process deletes old archived transaction logs automatically).
Database with circular logging
If the DB2 circular logging is enabled (the default), some additional steps are needed. The database
indexes required by the online data purge are not created automatically, because the database can run out
of transaction logs while creating the indexes. How to create the indexes is described in the next chapter.
If creating indexes does not succeed due to insufficient amount of transaction log space, you can change
database configuration parameters in order to get more space of the transactions. Before changing any
parameters, save the current values:
$ db2 get db cfg for meas7 > /tmp/meas7_db_config.txt
Change either maximum number of log files or log file size parameters, or both:
1. Increase number of transaction logs. The maximum number of files is 256
$ db2 connect to meas7
$ db2 update db cfg using logprimary 256
2. Increase size of the log files
$ db2 connect to meas7
$ db2 update db cfg using logfilsiz 32768
7signal Solutions Inc., 6155 Rockside Road, Suite 110, Independence, Ohio 44131, USA,
216-777-2900, [e-mail], www.7signal.com