The enhanced drop event trigger command supports the four new triggers. For more information on drop event trigger, see Chapter 9, “Replication Monitoring Services API,” in the Replication Server Reference Manual.
The modified drop event trigger syntax is:
drop {status | latency | size} trigger
[{connection | logical connection | route | queue | rep agent |
partition} [component_name]]
[with primary primary_connection]
for server_name
{status changes to state |
size {exceeds | falls below} size_threshold |
latency {exceeds | falls below} latency_threshold}
The new parameters are:
with primary primary_connection – identifies the primary connection of the latency connection trigger to drop. This parameter is required when dropping a latency connection trigger.
size exceeds, falls below size_threshold – indicates the size trigger to drop.
latency exceeds, falls below latency_threshold – indicates latency trigger to drop.
Drop a partition size trigger:
drop size trigger partition p1 for INVENTORY_RS size exceeds 80
Drop a latency connection trigger:
drop latency trigger connection inventory_rds.vendor with primary inventory_pds.ventory for INVENTORY_RS latency exceeds 300
