Siebel Database Upgrade Guide > Preparing an IBM DB2 Database for a Siebel Upgrade >
Analyzing IBM DB2 Custom Tablespace Requirements for a Siebel Upgrade
Upgrades from: All Supported Siebel releases.
Environments: Development, production test, production.
Databases: IBM DB2 only.
This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.
There are four standard database managed tablespaces (DMS) that hold Siebel tables and indexes—a 4-KB, 16-KB, 32-KB tablespace, for tables, and a tablespace to hold indexes. The upgrade process moves tables between these spaces as required.
If you have placed Siebel tables in other tablespaces, the upgrade process will not move these tables if they grow to exceed the tablespace size during the upgrade. If one of these tables has an estimated page size after upgrade greater than its current page size, it will not fit in its tablespace after the upgrade, and the upgrade will fail.
Oracle provides a sizing utility that determines whether tables will increase in size to the point that they must be moved to a larger tablespace.
Run the utility before upgrading the database. If the sizing utility reports any problems, you must resolve them before you proceed with the upgrade.
To analyze tablespace requirements for DB2
- Navigate to the following directory:
- Type the following command line:
= Tableowner password
= Data source of the database
= Absolute path to the DDL file (This file is called
ddl.ctl, and it is located in the
= Name of the 4-KB page standard Siebel tablespace
= Name of the standard Siebel index space
= Name of the 16-KB page standard Siebel tablespace
= Name of the 32-KB page standard Siebel tablespace
= Name of the report generated by the utility
= Name of the log file (The default name is
tblsize /U siebel /P siebel /C ssia /F d:/sea77/dbsrvr/db2udb/ddl.ctl /B siebel_4k /X siebel_idx /K siebel_16k /V siebel_32k /Q d:/sea77/dbsrvr/db2udb/report.txt /L $SIEBEL_ROOT/log/tblsize.log
- Review the report generated by the utility to determine if the estimated table pagesize postupgrade is larger than the size of the actual custom table pagesize.
An example of the report generated by this utility is displayed in the following example:
Table Name = S_EVT_ACT
Custom Tablespace Id = 5
Custom Tablespace Name = CUST_TBS_EVT_ACT
Custom Tablespace Pagesize = 4096
Estimated Table Pagesize (postupgrade) = 5067
Status = Does not fit in its custom tablespace
- For each table that has
Status: Does not fit in its custom tablespace, you must create a larger custom tablespace that is larger than the estimated table pagesize postupgrade.
- Move the tables from their old tablespaces to the new ones by running
ddlmove is a utility for moving tables from one tablespace to another tablespace. This utility is located in the following directory:
- To run
ddlmove, submit the following arguments:
= Tableowner of the database (Required)
= Password of the tableowner of the database (Required)
= Data source of the database (Default environment variable: SIEBEL_DATA_SOURCE)
= Stop on DDL Error (Default: Y)
= Grantee for tables
= Name of the tablespace that you are moving the table to
= Name of the index space that you are moving the table to
TABLE_NAME = Table Name Like Support (Default: N)
= Name of the log file (The default name is ddlmove.log.)
= (Default: N)