About Index Creation During the Additive Upgrade Process

Although additive schema changes are generally nondisruptive, index creation during the additive upgrade process can impact Siebel application usage if both of the following conditions exist:

• Indexes are specified with the DEFINE parameter set to YES

• The DEFER YES parameter is not specified for the index

If data exists in a table for which an index is being created, DB2 changes the DEFINE parameter value from NO to YES, and issues a warning message. If the DEFER YES parameter is not also specified for the index, the index is populated while it is being created, and locks are placed on the associated table until the process is completed, preventing updates being made to the table.

In these cases, change the index definition to DEFINE YES, DEFER YES; this ensures the index is not populated while it is being created, so the associated table is not locked. You can run the IBM DB2 REBUILD INDEX utility (DSNUTILB) to populate the index at a later time when performing regularly scheduled maintenance. For additional information on applying additive index changes to the target database, see Applying the Additive Changes in One Job.