User's Manual

Chapter 14. Utilities and Options Reference
dbremote -rd 30s
polls every thirty seconds.
☞ For more information on polling, see “Tuning incoming message
polling” on page 230.
–ro This option is for use at consolidated sites. When remote databases are
configured to send output log information to the consolidated database, this
option writes the information to a file. The option is provided to help
administrators troubleshoot errors at remote sites.
☞ For more information, see “Troubleshooting errors at remote sites” on
page 226.
–rp When running in continuous mode, the Message Agent polls at certain
intervals for messages. After polling a set number of times (by default, one),
if a message is missing, the Message Agent assumes it has got lost and
requests that it be resent. On slow message systems, this can result in many
unnecessary resend requests. You can set the number of polls before a
resend request is issued using this option, to cut down on the number of
resend requests.
☞ For more information on configuring this option, see “Tuning incoming
message polling” on page 230.
–rt This option is for use at consolidated sites. It is identical to the -ro
option except that the file is truncated on startup.
–ru Control the resend urgency. This is the time between detection of a
resend request and when the Message Agent starts fulfilling the request. Use
this option to help the Message Agent collect resend requests from multiple
users before rescanning the log. The time unit can be any of {s = seconds; m
= minutes; h = hours; d = days}
–s Send messages. If none of -r, -I, or -s is specified, the Message Agent
executes all three phases. Otherwise, only the indicated phases are executed.
–sd time Control the send delay which is the time to wait between polls
for more transaction log data to send.
–t All trigger actions are replicated. If you do use this option, you must
ensure that the trigger actions are not carried out twice at remote databases,
once by the trigger being fired at the remote site, and once by the explicit
application of the replicated actions from the consolidated database.
To ensure that trigger actions are not carried out twice, you can wrap an IF
CURRENT REMOTE USER IS NULL . . . END IF statement around the
body of the triggers. This option is available for Adaptive Server Anywhere
299