Partitioned table spaces with nonpartitioned indexes

The following considerations apply to nonpartitioned index (NPI) changes during the load:

  • When you specify LOAD REPLACE at the table space level with either SHRLEVEL CHANGE or SHRLEVEL REFERENCE, BMC AMI Load:
    • Discards any NPI changes for the partitions that you are loading
    • Collects changes for the remaining partitions and applies them after the load

Related topics

BMC-AMI-Load-operational-considerations

RESUME-INTO-TABLE-option 

  • You can keep the NPI in read/write status throughout the load process by specifying REPLACE or RESUME YES at the partition level only (on the INTO TABLE clause). BMC AMI Load collects changes to the NPI and applies them later.Using this method, partitions that are specified as REPLACE or RESUME YES change status before processing starts; other partitions do not change status and the NPI remains in read/write status.



 

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