resume component

Syntax

resume {dsi | queue | rep agent | route} component_name 
for {server_name | group_name} [skip transaction | execute transaction]

Parameters

• dsi, queue, rep agent, route – Specifies the component type to resume. The component is a database name, if resuming a RepAgent thread in an Adaptive Server Enterprise. Otherwise, the component is a connection, queue, or route name.
• component_name – Specifies the name of the component to resume.
• group_name – Specifies the name of a group. Each component in the group is resumed.
• server_name – Specifies the name of either a Replication Server or an Adaptive Server Enterprise that contains the component.
• skip transaction – If the option is provided for a DSI connection, instructs the Replication Server to resume execution with the second transaction in the connection’s queue. The first transaction is written to the database exceptions log.

  If the option is provided for a queue, specifies that the SQM should skip the first large message encountered after restarting.

  If this option is provided for a route, ignore the first transaction encountered with a wide message greater than 16K bytes.

• execute transaction – Overrides the Replication Server restriction against the application of system transactions after a DSI start-up if the system transaction is the first transaction in the DSI queue.

Examples

• Example 1 – Resumes the DSI thread for the connection “inventory_pds.vendor” in the Replication Server INVENTORY_RS. Does not wait for the current operation to complete:

  resume dsi inventory_pds.vendor for INVENTORY_RS with
         nowait

• Example 2 – Resumes the Replication Agent thread for the connection “inventory_pds.vendor” in the Replication Server INVENTORY_RS:

  resume rep agent inventory_pds.vendor for INVENTORY_RS

• Example 3 – Starts the RepAgent thread for the database vendor in the Adaptive Server Enterprise INVENTORY_PDS:

  resume rep agent vendor for INVENTORY_PDS

Usage