drop event trigger

Removes a trigger that the RMS is monitoring. A trigger identifies a process or script that is executed by the RMS. Set triggers up using the add trigger command.

Syntax

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}

Parameters

status, latency, size – Specifies the type of trigger.
connection, logical connection, route, queue, rep agent, partition – Specifies the type of component.
component_name – Specifies the name of the component. Components are monitored objects within a server. Replication Server components are connections, logical connections, routes, queues, and partitions; Adaptive Server Enterprise components are RepAgent threads.
with primary primary_connection – Identifies the primary connection of the latency connection trigger to drop. This parameter is required when dropping a latency connection.
server_name – Specifies the name of the server for which the trigger is defined that is being dropped.
state – Specifies the state of the event trigger that is being dropped. See RMS Server and Component States for state information.
size exceeds, falls below size_threshold – Indicates the size trigger to drop.
latency exceeds, falls below latency_threshold – Indicates the latency trigger to drop.

Examples

Example 1 – Removes the “DOWN” status trigger for the server INVENTORY_RS:
```
drop status trigger for INVENTORY_RS
    status changes to DOWN
```
Example 2 – Removes the “SUSPENDED” status trigger for the connection “inventory_pds.pdb1” of server INVENTORY_RS:
```
drop status trigger connection inventory_pds.pdb1
    for inventory_rs
    status changes to SUSPENDED
```

Example 3 – Drops a partition size trigger:

drop size trigger partition p1
   for INVENTORY_RS
   size exceeds 80

Example 4 – Drops a latency connection trigger:

drop latency trigger
   connection inventory_rds.vendor
   with primary inventory_pds.ventory
   for INVENTORY_RS
   latency exceeds 300

Usage

drop trigger returns the following result set:

Column Descriptions for drop event trigger
Column	Description
`Action`	The name of the action
`Result`	The result of the execution