Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see High-speed Apply Engine 13.1.

Partition key length

The High-speed Apply Engine can create partition keys from the columns and values that you specify within a partition definition.

High-speed Apply Engine derives partition keys as follows:

  • For Oracle and Db2 LUW targets, High-speed Apply Engine defines the partition key as the first 256 bytes of the values that are specified for the associated Column and Value parameters. Each partition key must resolve to a unique value.
  • For Db2 mainframe targets, High-speed Apply Engine defines the partition key as either the first 255 bytes of the values that are specified for the associated Column and Value parameters or the LimitKey parameter. Each partition key must resolve to a unique value.

Related topic

ObjectPartition-parameters

 

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