Command batching allows Replication Server to send multiple commands to the data server as a single command batch.
You can put multiple commands in a language function-string output template, separating them with semicolons (;). If the database is configured to allow command batches, which is the default, Replication Server replaces the semicolons with that connection’s DSI command separator character before sending the function string in a single batch to the data server.
The separator character is defined in the dsi_cmd_separator option of the alter connection command. If the connection to the database is not configured to allow batches, Replication Server sends the commands in the function string to the data server one at a time. To enable or disable batching for a database, use the alter connection command.
batch = on batch_begin = off
dsi_cmd_separator set = ;
As a result of a placeholder command that is used in the rs_begin function string, setting batch_begin to “on” may cause problems with starting DSI. Set batch_begin to “off” to allow the rs_begin and the rs_commit commands to be sent independently of the batches of commands, and ensures correct SQL in all transferred commands:
use_batch_markers = on
Oracle requires BEGIN and END markers for batches of commands. By configuring use_batch_markers to “on,” the markers are automatically added from the rs_batch_start and rs_batch_end function strings. See the Replication Server Administration Guide Volume 2 > Command Batching for Non-ASE Servers.