Requirements and restrictions for BMC AMI Unload

This topic describes BMC AMI Unload requirements and restrictions:

Software requirements

BMC AMI Unload product requires a minimum of version 12.1.00 of the BMC Db2 Solution Common Code (SCC).

Authorization requirements

Using BMC AMI Unload requires the following authorizations:

• One of the following for the database:
  • SYSADM
  • DBADM
  • COPY
• One of the following for the tables:
  • Ownership
  • SELECT
  • SYSCTRL (catalog tables only)

  • (SPE2107

    ) UNLOAD (Only validated for DIRECT YES or DIRECT AUTO which resolves to DIRECT YES)

Status requirements

When running BMC AMI Unload, the objects must be in the following statuses:

• The database must be in either RW status or UT,RO status. In addition, it cannot be in any restricted status.
• The table space must be in RW status and cannot be in any restricted status.

Restrictions

The following restrictions apply to BMC AMI Unload:

• BMC AMI Unload does not support:
  
  • DECFLOAT INDEXES, released in Db2 V12 FL505
• BMC AMI Unload does not process the following objects:
  • Hash tables
  • Clone tables and base tables of clone tables
  • XML columns
    
• BMC AMI Unload does not unload temporal columns or write them to SYSPUNCH.

• (PTF BQU2620 not applied) BMC AMI Unload 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
  4 KB	128 GB
  	256 GB
  8 KB	256 GB

• BMC AMI Unload supports a maximum of 32,950 SYSIN statements.
• BMC AMI Unload DIRECT YES does not support SELECT statements greater than 64k and has other imposed limits as defined by the language interface.