The options available depend on the send frequency options selected for the remote users. Sending frequency options are described in “Selecting a send frequency” on page 206 .

To run the Message Agent in continuous mode

1.Ensure that every user has a sending frequency specified. The sending frequency is specified by a SEND AT or SEND EVERY option in the GRANT REMOTE statement (Adaptive Server Anywhere) or sp_grant_remote procedure (Adaptive Server Enterprise).

2.Start the Message Agent without using the -boption.

To run the Message Agent in batch mode

1.Either:

Have at least one remote user who has neither a SEND AT nor a SEND EVERY option in their remote properties, or

Start the Message Agent using the -boption.

Connections used by the Message Agent

The Message Agent uses a number of connections to the database server.

These are:

One global connection, alive all the time the Message Agent is running.

One connection for scanning the log. This connection is alive during the scan phase only.

One connection for executing commands from the log-scanning thread. This connection is alive during the scan phase only.

One connection for the stable queue (Adaptive Server Enterprise only). This connection is alive during the scan and send phases.

One connection for processing synchronize subscription requests. This connection is alive during the send phase only.

One connection for each worker thread. These connections are alive during the receive phase only.

Replication system recovery procedures

SQL Remote replication places new requirements on data recovery practices at consolidated database sites. Standard backup and recovery procedures

224

Page 242
Image 242
Sybase DC38133-01-0902-01 manual Connections used by the Message Agent, Replication system recovery procedures