Filter
Top Products
DB2 Manager User Guide 75
StorageTek Proprietary
Table migration processing
Introduction
DB2 Manager provides functions to perform the migration of rows from DB2
to Archive Manager storage. These functions are provided by the DB2
Manager table migration utility, OTDBP100.
The table migration utility is executed as a batch process, and should be
scheduled to run at regular intervals in order to migrate rows from DB2 to an
Archive Manager database. The frequency of execution of this procedure will
be controlled by operational factors, such as the overall amount of DB2 disk
storage available, the rate of insertion of new rows, the frequency of update
of migrated rows, the rate of retrieval of migrated rows etc.
Careful planning is required when implementing a table migration strategy, in
order to optimize system performance by migrating rows at the appropriate
stage of their existence. Migration should be performed so that DB2 disk
storage requirements may be minimized without introducing performance
problems through the creation of an Archive Manager tape recall activity rate
which exceeds the performance capacity of the installed tape library
configuration.
DB2 Manager requires that a table from which rows are to be migrated is
enabled for this type of processing. “Enabling a DB2 table for migration
processing” on page 75 describes the activities required to enable a table for
migration processing.
Following successful completion of migration processing, some DB2
database management is needed if it is required to reclaim disk space
released through the migration of rows to Archive Manager storage. “DB2
database reorganization” on page 88 explains the issues relating to this
requirement and describes how to do this.
Enabling a DB2 table for migration processing
Before initiating DB2 Manager row migration processing for a DB2 table, the
table must be enabled for this type of processing. This consists of a number
of activities as described in this section. These activities must be
successfully completed for each DB2 table which is to be processed by DB2
Manager.
5