Filter
Top Products
76 DB2 Manager User Guide
StorageTek Proprietary
Restrictions
DB2 tables which are to be eligible for processing by DB2 Manager must
adhere to the following restrictions:
• Each row in the table must be indexed by a unique key. The indexing key
can consist of one or multiple columns in the table.
• The table must not contain large objects (LOBs), ROWID or identity
columns or “distinct types”.
A table which does not satisfy all the above criteria will not be processed by
the DB2 Manager table migration utility.
Enabling activities
In order to enable a DB2 table for row migration by DB2 Manager, the
following actions must be performed:
• A new partitioned tablespace must be created to hold a copy of the table
being enabled for migration processing. This should have one more
partition than the number of partitions in the tablespace containing the
table to be enabled for migration. The last partition in this tablespace will
be used for storage of all archive row stubs. Each stub will be 18 bytes in
length, and there will be one stub for each row in the table which has
been migrated to Archive Manager. This partition should be large
enough to hold archive stubs for the maximum number of migrated rows
present in the database.
• A new table must be created in this tablespace. This should be an exact
copy of the original table, with the following modifications:
o The statement ‘EDITPROC OTDBP300’ is added to the SQL
CREATE TABLE command.
o An additional column ‘OTDBIND’ is added to the SQL CREATE
TABLE command, with the following specification:
OTDBIND CHAR(1) DEFAULT ‘0’
Example
:
CREATE TABLE OTDBSYST.TAB1A
(
FIELD1 CHAR(1) ,
FIELD2 CHAR(255) ,
FIELD3 VARCHAR(255) ,
FIELD4 GRAPHIC(1) ,
FIELD5 VARGRAPHIC(127) ,
FIELD6 SMALLINT NOT NULL,
FIELD7 INTEGER NOT NULL,
FIELD8 DECIMAL(7,0) NOT NULL,
FIELD9 REAL ,
FIELD10 DOUBLE ,
FIELD11 TIME ,
FIELD12 DATE NOT NULL,