MaxExecuteImmediateDML


The MaxExecuteImmediateDML parameter defines a limit on how many data manipulation language (DML) statements the High-speed Apply Engine can process as EXECUTE IMMEDIATE.

Attributes

This parameter has the following attributes:

Attribute

Value

Section

[DistributionTuning]

Abbreviation

None

Required?

No

Valid values

An integer greater than or equal to zero

Default value

None

(By default, High-speed Apply Engine does not limit the number of DML statements processed with EXECUTE IMMEDIATE.)

Usage

Normally, High-speed Apply Engine processes data definition language (DDL) statements by issuing an EXECUTE IMMEDIATE command. High-speed Apply Engine also processes a few types of complex DML statements this way (for example, an INSERT statement with an embedded SELECT clause). However, when High-speed Apply Engine experiences problems processing statements with static or dynamic SQL, it attempts to continue processing by using EXECUTE IMMEDIATE as a last resort.

Specify the number of statements to impose a limit. By default, High-speed Apply Engine does not impose a limit.

  • Use this parameter to stop High-speed Apply Engine from executing an unusually large number of DML statements in a less than optimal manner. When the High-speed Apply Engine exceeds the limit set by this parameter, it issues message BMCAPT0196 and terminates the processing.
  • Depending on the MaxExecuteImmediateDML value you specify, message BMCAPT0196 can indicate that High-speed Apply Engine is not using static or dynamic SQL processing as much as it should be.
  • The message can also indicate that you should adjust the values of the [BindTuning] parameters, particularly MaxPackages. For more information, see Using-BindTuning-parameters-for-performance and MaxPackages.

 

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