Reorganizing LOB table spaces

BMC AMI Reorg processes LOB table spaces and their base table spaces separately and puts LOB table spaces in UT status.

The BMC AMI LOBMaster product checks and reorganizes base and LOB auxiliary table spaces at the same time. For more information about BMC AMI LOBMaster, see the BMC AMI LOBMaster documentation.

When you specify a wildcard list of table spaces to process, you can omit LOB table spaces by specifying the +LOB(NO) parameter. +LOB(NO) is the default. With +LOB(YES), BMC AMI Reorg processes all base and LOB table spaces included by the wildcard specified.

The following restrictions apply when reorganizing LOB table spaces or their base table spaces:

• BMC AMI Reorg does not rebalance partitions in table spaces that contain LOB columns or in LOB table spaces.
• BMC AMI Reorg does not natively reorganize PBG table spaces that contain LOB columns, but you can reorganize such table spaces using one of the following methods:
  • Invoke DSNUTILB. For more information, see Invoking-DSNUTILB.

  • If you have a license for BMC AMI LOBMaster, add the AUX keyword to your BMC AMI Reorg syntax. BMC AMI LOBMaster reorganizes both the LOB table space and the base table space. For more information, see the BMC AMI LOBMaster documentation.

• BMC AMI Reorg does not process a base table space with LOB columns when that table space is in REORP status.

  A reorganization to remove the REORP status might require moving rows between partitions, including the LOB rows in the associated LOB table spaces.

  This restriction applies to any ALTER statement that puts a table space in REORP status, such as ALTER ADD PARTITION or ALTER ROTATE.

• During a reorganization with discards from the base table, BMC AMI Reorg puts the LOB auxiliary table in ACHKP status. After the reorganization, you can run IBM CHECK utilities to find and delete orphaned LOB rows.

  If you use BMC AMI LOBMaster instead of BMC AMI Reorg, this restriction does not apply.