Space announcement This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Transformation without the High-speed Structure Change process

Assume, for example, that you have several non-large partitioned table spaces. You would like to improve your space management by taking advantage of range-partitioned UTSs. You can increase the data set size and convert these table spaces to large partitioned table spaces or range-partitioned UTS table spaces. These changes require that you drop and re-create objects, resulting in an outage.

Related topic

High-speed-Structure-Change

Without the High-speed Structure Change process, the following steps are required to perform these transformations:

  1. Start your table space in read-only access.
  2. Unload the data.
  3. Drop the old table space.
  4. Create the new table space and indexes with the new definitions.
  5. Stop your table space.
  6. Load the data into the newly defined table space and rebuild all the indexes.
  7. Perform RUNSTATS.
  8. Re-create any auxiliary objects that were lost due to dropping the table space, such as views or triggers.
  9. Rebind the programs that access this table.

  10. Start the table space in read-write access.The data is unavailable for update during Step 1 through Step 4. In Step 5 through Step 9, the data is unavailable for reading and updating. Additionally, this process requires a large amount of CPU time. The UNLOAD and LOAD must process each row in the table space and rebuild each index.

    The following figure provides a hypothetical timeline that refers back to these steps for a conversion that requires you to drop and re-create objects:

    GUID-C639B0A0-82AA-411F-8335-9444C6721332-low.png

 

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