StorageTek Lifecycle Director DB2 Manager 312564001 User Manual
16
DB2 Manager User Guide
StorageTek
Proprietary
exclusive storage of migrated row stubs, and one or more partitions for
storage of non-migrated rows.
storage of non-migrated rows.
Database reorganization processing should not be performed on the partition
containing the migrated row stubs, unless absolutely necessary.
Reorganization of this partition will cause all migrated rows to be retrieved
from Archive Manager. If Archive Manager objects are held on tape storage
only, this is likely to generate a substantial amount of tape activity and could
take an excessive length of time to complete. However, all rows stored in
this partition will be a fixed 18 bytes in length. In this case, deletion of rows is
not likely to cause fragmentation in the tablespace, as deleted space can be
re-used as required. The requirement for reorganization of this partition is
thus not mandatory.
containing the migrated row stubs, unless absolutely necessary.
Reorganization of this partition will cause all migrated rows to be retrieved
from Archive Manager. If Archive Manager objects are held on tape storage
only, this is likely to generate a substantial amount of tape activity and could
take an excessive length of time to complete. However, all rows stored in
this partition will be a fixed 18 bytes in length. In this case, deletion of rows is
not likely to cause fragmentation in the tablespace, as deleted space can be
re-used as required. The requirement for reorganization of this partition is
thus not mandatory.
Reorganization of other (non-migrated) partitions in the tablespace should be
performed as normal. Regular reorganization will, in particular, be required
for a period of time after implementation of DB2 Manager migration, in order
to reclaim disk space occupied by rows which have been migrated to Archive
Manager. This will allow these tablespace partitions to be reduced in size,
eventually down to the size needed for the “working-set” of unmigrated rows
(ie) rows which have yet to be migrated to Archive Manager.
performed as normal. Regular reorganization will, in particular, be required
for a period of time after implementation of DB2 Manager migration, in order
to reclaim disk space occupied by rows which have been migrated to Archive
Manager. This will allow these tablespace partitions to be reduced in size,
eventually down to the size needed for the “working-set” of unmigrated rows
(ie) rows which have yet to be migrated to Archive Manager.
Pre-requisites for DB2 Manager implementation
In order to use DB2 Manager version 1.1 on a system for implementation of
Archive Manager support for storage and retrieval of DB2 table rows, the
following software pre-requisites are required:
Archive Manager support for storage and retrieval of DB2 table rows, the
following software pre-requisites are required:
- OS/390 V1.1 or higher
- DB2 V4 or higher
- Archive Manager V2.5 or higher
- Support for 3480/3490/3590 device types.
The following hardware pre-requisites will be required:
- 3480/3490/3590-compatible cartridge tape devices.
- A correctly sized STK 4400 ACS library configuration.
Sizing of the hardware requirements is dependent on a number of factors
relating to the volume and usage of DB2 tables which are to be eligible for
row migration. This may be a complex task, and should be performed in
conjunction with the StorageTek customer support representative for your
installation.
relating to the volume and usage of DB2 tables which are to be eligible for
row migration. This may be a complex task, and should be performed in
conjunction with the StorageTek customer support representative for your
installation.