Default language.

Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

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 BMC AMI Reorg for Db2 13.1.

Reorganizing objects in REORG-pending (REORP) status

BMC AMI Reorg uses RELOAD REORG to process objects that are in REORG-pending (REORP) status.

When processing objects that are in REORP status, BMC AMI Reorg uses the BMC AMI Load parameters that are specified in the LODPARMS DD, including common parameters that also exist in the RRGPARMS DD, such as ALLO-for-BMC-AMI-Reorg.

Important

Some restrictions apply when a partitioned table space in REORP status has associated LOB table spaces. For more information, see Reorganizing-LOB-table-spaces.

Minimizing downtime due to REORP

To minimize downtime due to REORP and maximize an object's availability, BMC recommends that you perform one of the following actions:

  • Reorganize the object that will be placed in REORP state because of an alter.
  • Perform the alter, placing the object in REORP state and making it unavailable.
  • Reorganize the object with the +SORT(NO) load parameter to eliminate the REORP status, making the object available again.

If downtime is not an issue, you can alter the object and run the reorganization with the +SORT(YES) load parameter to clear the REORP status and organize the data. The regularly scheduled reorganization job processes any other parts that meet the criteria for reorganization.

DDL that causes REORP status

The following list contains some of the SQL statements that put a table space in REORP status, making it unavailable. 

Tip

BMC recommends that you always test the DDL you plan to run to check for REORP status. 

  • ALTER TABLE ... ALTER COLUMN (of partitioning index, increase character length)

  • ALTER TABLE ... ADD COLUMN (where the column is an identity column)

    Adding a column causes BMC AMI Reorg to assign the reorganization process timestamp value for rows in that column that have not been modified by SQL statements after ALTER.

  • (Db2 Version 10) ALTER TABLE ... ALTER PARTITION (to alter the limit key)

    Altering the last partition does not put the table space in REORP status.

  • ALTER TABLE ... ADD PARTITION (if boundary for last partition not enforced)
  • ALTER TABLE ... ROTATE PARTITION (if boundary for last partition not enforced)


Related topics

Using-BMC-AMI-Reorg

Reorganizing-table-spaces

Reorganizing-indexes

Reorganizing-LOB-table-spaces



 

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