BMC AMI LOBMaster requirements and restrictions

Required authorizations

BMC AMI LOBMaster requires one of the following authorizations:

• REORG authority on the database
• SYSADM or DBADM authority

Status requirements

When you are running BMC AMI LOBMaster, the table space can be in read/write (RW) status.

In addition, the table space can be in one of the following restricted statuses:

• Auxiliary CHECK pending (ACHKP)
• Auxiliary warning (AUXW)

Restrictions

The following restrictions apply to BMC AMI LOBMaster:

• BMC AMI LOBMaster does not support:
  
  • DECFLOAT INDEXES, released in Db2 12 FL505
  • RBALRSN_CONVERSION and sends to DSNUTILB (job fails if DSNUTILB (NO) is set for BMC AMI Utilities)

• If a table has both LOB columns and XML columns, BMC AMI LOBMaster will call DSNUTILB for processing.
• If the table space was altered to define an inline LOB column, BMC AMI LOBMaster does not move data to the inline portion of the LOB.
• If the table space was altered to change limit keys, BMC AMI LOBMaster does not materialize the altered limit keys during the reorganization.
• If the LOB AUX table spaces DSSIZE was altered, BMC AMI LOBMaster does not materialize the pending DDL.

• BMC AMI LOBMaster supports partition-by-range (PBR) and partition-by-growth (PBG) table spaces with partition sizes (DSSIZE) greater than 64 GB except for the following PAGESIZE and DSSIZE combinations:

  PAGESIZE	DSSIZE
  4KB	128GB
  	256GB
  8KB	256GB

• BMC AMI LOBMaster supports PBG table spaces with any PAGESIZE and DSSIZE combination considering each partition is not greater than 16 million pages.