Siebel Database Upgrade Guide for DB2 for z/OS > Basic Database Preparations for a Siebel Upgrade >

Verifying Database Configuration

Upgrades: All upgrades.

Environments: All environments.

Verify that your development Siebel database configuration meets or exceeds Siebel requirements as described in Implementing Siebel Business Applications on DB2 for z/OS. Be aware of the following:

• The upgrade sets the TRACKMOD parameter to YES, which is the IBM default value for table space objects. Oracle recommends that you set the TRACKMOD parameter to NO, to reduce data sharing overhead.
• Set the DSNZPARM CMTSTAT to INACTIVE to prevent timeout errors from occurring. If you do not set this DSNZPARM parameter to INACTIVE, then set IDTHTOIN to 0 (Inactive).
• Ensure the z/OS Unicode Conversion Services are correctly installed and configured. For further information on z/OS Unicode Conversion Services, see Implementing Siebel Business Applications on DB2 for z/OS.

Before you begin your upgrade, verify your database configuration. The consequence of exceeding available resources is a halted upgrade that requires you to allocate time to adjust the environment and then resume the upgrade.

When you upgrade from a previous version of Siebel Business Applications to version 8.1, the size of your database is likely to increase. The amount by which your database grows might vary widely, depending on your database configuration, row size of tables, and data content. For information on estimating the growth, see About Estimating Database Size.

The growth percentage will also increase depending on how you size your database and configure default storage for database table spaces. For example, if you set the default storage for your initial or next extent in a given DB2 table space to 10 KB, that table space will grow by a smaller percentage than if you set it to 100 KB.