Performance Tuning for Content Manager

Chapter 8. Tuning DB2 for Content Manager 195

"ATTR0000001047" VARCHAR(254) ,

"ATTR0000001048" INTEGER ,

"ATTR0000001049" INTEGER ,

"ATTR0000001050" INTEGER ,

"ATTR0000001051" INTEGER ,

"ATTR0000001052" INTEGER ,

"ATTR0000001053" INTEGER ,

"ATTR0000001054" INTEGER ,

"ATTR0000001055" INTEGER ,

"ATTR0000001056" INTEGER ,

"ATTR0000001057" INTEGER ,

"ATTR0000001058" VARCHAR(3975) )

IN "tsicmut16001" INDEX IN "tsicmut16001i";

The DDL for the other DB2 objects that relate to the table space (indexes, views)

do not change as part of the conversion to DMS.

If you want to use the same name for the new DMS table space as is being used

by the SMS table space, drop the old SMS table space before creating the new

one:

db2 drop tablespace tscmut16001

If you want to use a different name for the new DMS table space, drop any old

SMS tables that belong to the table spaces being converted to DMS before

creating the new tables because the table names are not changing:

db2 drop table ICMADMIN.ICMUT01016001

As discussed at the start of this section, we have assumed that all of the DDL

related to the conversion of a table space from SMS to DMS has been put into a

single file. For the purpose of this example, the dms-icmut16001.sql file contains

all of the DDL related to our table space. To run the DDLs for DMS table space

creation, issue the following command:

db2 -tvf dms-icmut16001.sql

8.4.5 Loading the data

After you have created the table space and all of the objects that relate to it, load

the data back into the tables. Example 8-12 on page 196 shows an example of

the load command.