Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see Recovery Management for Db2 13.1.

High-speed Structure Change

Db2 Version 9 introduced universal table spaces (UTS) that provide better performance and easier space management. Converting to this new table space definition could require a large amount of down time for your production data. The High-speed Structure Change process allows you to convert your data base objects to the new definitions with minimal outage and reduced CPU requirements.

The High-speed Structure Change process allows you to perform the following transformations:

  • Simple table space to partition-by-growth (PBG) table space
  • Non-large partitioned table space to large partitioned table space
  • Range-partitioned table space to range-partitioned (PBR) universal table space
  • Range-partitioned table space to partition-by-growth universal table space
  • Multi-table table space to partition-by-growth universal table space

The High-speed Structure Change process also allows you to transform your indexes, avoiding costly sort CPU that would be required to rebuild the index.

At a more granular level, you can use the High-speed Structure Change process to:

  • Change the segment size (SEGSIZE) of a table space
  • Transform a non-segmented table space into a segmented one
  • Change the data set size (DSSIZE or PIECESIZE) of your table space or index
  • Change the compression attribute of your index
  • Add or remove the MEMBER CLUSTER attribute
  • Increase or decrease MAXPARTITIONS

The High-speed Structure Change process works at the page level. The process uses a VSAM image copy, such as an Online Consistent Copy or Instant Snapshot, as input, reads each page, and transforms the page to fit the new definition. The process then moves the page to the new object. During this transformation, applications can have read-only access or concurrent (update) access to the objects. Using concurrent access reduces the length of the outage. With either type of access, you will have a brief outage at the end of the process.

This section contains the following topics:

Related topic

Using-Online-Consistent-Copy-for-transforms-or-data-migration


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*