Stable queue partitions fill up when a Replication Server is receiving more messages than it is sending. For example, if a network is down between a primary site and a replicate site, the Replication Server at the primary site queues up the undeliverable messages. When the network returns to service, the messages can be delivered, and then deleted from the primary Replication Server partitions.
If a partition becomes completely full, senders cannot deliver their messages to the Replication Server, and messages begin to back up in the partitions at previous sites and in the transaction logs for primary databases.
WARNING! If the situation is not corrected, RepAgent is unable to update the secondary truncation point in the database log, and the transaction log fills. Clients are then unable to execute transactions at the primary database.
You can configure Replication Server to warn when partitions become too full by setting three rows in the rs_config system table: sqm_warning_thr1, sqm_warning_thr2, and sqm_warning_thr_ind. These parameters are described in Chapter 3, “Replication Server Commands” in the Replication Server Reference Manual.
