When converting a segmented Tablespace to a UTS PBG, the original SEGSIZE is not honored.

Document ID:  TEC1142613
Last Modified Date:  07/04/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA RC/Migrator for DB2 for z/OS

Components

  • CA RC/Migrator for DB2 for z/OS:RCM
Symptoms:

When altering a segmented Tablespace from a segmented Tablespace to a Partition-by-Growth (PBG) Universal Tablespace (UTS), RC/Compare generates the following DDL to make the change:

ALTER TABLESPACE dbname.tsname MAXPARTITIONS 1

A Reorg utility is also generated to materialize the Tablespace to PBG UTS. Once the Reorg has been executed the SEGSIZE of the altered object is now 32G.

 

Cause:

As per the DB2 SQL Reference Guide, if MAXPARTITIONS is specified on a simple or segmented table space, the table space is converted to a partition-by-growth universal table space that can grow to a maximum number of integer partitions. The SEGSIZE is set to the default of 32 if the SEGSIZE prior to conversion is less than 32.

Workaround:

If it is a requirement to retain the original SEGSIZE, then currently you must avoid using DB2 Alter. This can be done by performing a DROP/CREATE in the Analysis. To do this set the following Analysis Option to 'Y':

DROP & RE-CREATE ==> Y

Additional Information:

Please refer to the alteration considerations section in the RC/Migrator documentation.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >