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.

ObjectCluster parameters

[ObjectCluster] parameters let you specify a group of target tables to be processed by the same apply agent. You can use the parameters in this section to define groups of related tables or to optimize workload distribution.

Parameter

Reference

Cluster

Table

When you define a group of target tables, the High-speed Apply Engine uses the same agent to process all updates to that group. However High-speed Apply Engine does not guarantee that the agent processesonly that group. If the number of groups you define is greater than the number of agents you permit, High-speed Apply Engine can use one agent to process more than one group. For more information, see MaxAgents.

The position of the [ObjectCluster] parameters is significant. The Cluster parameter must appear first in the section, and it must be followed by at least one table name. For an example of [ObjectCluster] parameters, see the following figure.

Warning

If you include the [ObjectCluster] section in the configuration, the RIClustering parameter is set to No when you run the apply request, regardless of the value specified in the configuration. If you define an object cluster, High-speed Apply Engine ignores any referential integrity constraints on the members of the cluster.

 [ObjectCluster]
  Cluster=HUMANRES
  Table=HR.*
  Cluster=ACC1Q
  Table=ACC.JAN
  Table=ACC.FEB
  Table=ACC.MAR
  Cluster=ACC2Q
  Table=ACC.APR
  Table=ACC.MAY
  Table=ACC.JUN


Related topics

Command-and-syntax-reference

Format-of-configuration-parameters


 

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