KEEPDICTIONARY

KEEPDICTIONARY determines whether to keep the existing compression dictionary and is available for compatibility with the IBM Db2 LOAD utility command. BMC AMI Load honors the option.

The KEEPDICTIONARY options determines whether to keep the existing Lempel-Ziv compression dictionary in a table space or table space partition after running the REPLACE option. BMC recommends that you use the KEEPDICTIONARY option if you are using a data replication product to replicate identical data objects across partitions ("mirroring").

BMC AMI Load honors the KEEPDICTIONARY option provided that:

  • The table space is readable and is not in a restricted state.
  • The table space has a valid compression dictionary.
  • A ROWFORMAT conversion from BRF to RRF (or vice versa) is in effect and the value of the IBM Db2 subsystem parameter HONOR_KEEPDICTIONARY is YES.
  • Sufficient virtual memory is available to keep the existing compression dictionary and to perform the load across all of the partitions that have different dictionaries.

Related topics

Basic-options

Syntax diagrams

Compression-dictionaries

If one or more of these conditions is not satisfied, BMC AMI Load ignores the KEEPDICTIONARY option and issues warning message NGTL947.

The PART specification in the syntax diagrams must show RESUME NO REPLACE as a valid option. KEEPDICTIONARY may be specified anywhere after the PART specification and before table specific keywords, such as IGNOREFILDS.


KEEPDICTIONARY.png

Important

If you specify KEEPDICTIONARY without a value, BMC AMI Load assumes KEEPDICTIONARY YES. 

You can specify the KEEPDICTIONARY option in any of the following positions: 

  • At the INTO TABLE level after the PART option, as follows:INTO_TABLE_PART_KEEPDICTIONARY.png

    If you specify KEEPDICTIONARY YES without specifying REPLACE or RESUME in the INTO TABLE level, the LOAD-level REPLACE or RESUME specification operates.

  • At the global LOAD statement level after the REPLACE option, as follows:REPLACE_KEEPDICTIONARY.png

    In this case, the KEEPDICTIONARY option applies to the whole statement.

    If you specify KEEPDICTIONARY YES at the LOAD statement level, BMC AMI Load honors any KEEPDICTIONARY NO specification at the INTO TABLE PART level for the specified partition. The KEEPDICTIONARY specification at the INTO TABLE level takes precedence over KEEPDICTIONARY specification at the LOAD statement level. 

    Example
    LOAD RESUME YES KEEPDICTIONARY YES
         INTO TABLE my.table PART 1 KEEPDICTIONARY NO REPLACE
         INTO TABLE my.table PART 5:50 REPLACE
         INTO TABLE my.table PART 2:4

    This syntax causes the following behavior:

    • BMC AMI Load keeps the compression dictionaries for partitions 5 through 50, but not for the first partition.
    • BMC AMI Load ignores the KEEPDICTIONARY specification for partitions 2 through 4 because you selected RESUME.

YES

(default) If you specify KEEPDICTIONARY YES, BMC AMI Load keeps the existing compression dictionary. If a compression dictionary does not exist, BMC AMI Load builds a compression dictionary and compresses the data.

NO

If you specify KEEPDICTIONARY NO, the KEEPDICTIONARY option has no effect. BMC AMI Load builds a new compression dictionary and compresses the data.


 

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