FILTERPART


This option allows BMC AMI Unload to filter out partitions that do not meet the WHERE clause criteria when you use the first column of the partitioning key in your WHERE clause.

GUID-73DB8D0A-65D2-4C80-BA0C-5A932859028F-low.png

Specifying PART within a SELECT OPTIONS statement overrides the FILTERPART command option for the corresponding SELECT statement.

Warning

Restriction

BMC AMI Unload ignores this option when DIRECT NO is in effect.

NO

FILTERPART NO is the default. When you specify FILTERPART NO, BMC AMI Unload reads all partitions of the partitioned table space.

YES

When you specify FILTERPART YES, BMC AMI Unload filters out partitions that do not meet the selection criteria. BMC AMI Unload uses only the SYSREC data sets that are related to the unloaded partitions.

Information
Example

In this example, COL1 is the column that causes the break of partitions. If you use COL1 in the WHERE clause, BMC AMI Unload filters out partitions that do not meet the criteria of the WHERE clause. If you specify FILTERPART YES, BMC AMI Unload reads only partitions 2 and 3.

Three-column partitioning key

Partition number

COL1

COL2

COL3

Partition 1

199

xxx

005

Partition 2

299

xxx

010

Partition 3

399

xxx

020

Partition 4

499

xxx

030

SELECT statement:

SELECT * FROM <your.tablename>
     WHERE COL1 > '200'
       AND COL1 < '399'

Considerations

The following restrictions and other considerations apply to FILTERPART YES:

  • BMC AMI Unload ignores this option when unloading image copies or partition-by-growth table spaces.
  • For the predicate on your WHERE clause, if you specify a value that equals the limit key, BMC AMI Unload might read an additional partition.



 

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

BMC AMI Unload for Db2 13.1