The dump subcommand is used at a primary site to initiate a coordinated dump. RepAgent retrieves the dump record from the transaction log and sends a dump subcommand to the Replication Server to distribute rs_dumptran or rs_dumpdb functions to all sites with subscriptions for data in the database.
distribute command_tags dump [database | {transaction | tran | _tr}
[standby | stdb | status]] database_name, dump_label id
database informs Replication Server to distribute rs_dumpdb.
transaction or tran or _tr informs Replication Server to distribute rs_dumptran.
standby or stdb an optional keyword that informs the Replication Server that the command is a dump transaction command that contains the parameter with standby_access.
status is an integer value that indicates dump status:
0 – the dump transaction command does not contain with standby_access.
1 – the dump transaction command contains the parameter with standby_access.
database_name is the name of the database that was dumped.
dump_label is a varchar(30) value that contains some information to identify the dump. RepAgent uses the date and time of the dump for this variable.
id is a varbinary(36) timestamp for the dump.
A dump command must be sent within a transaction.
This is an example of the dump transaction command that RepAgent sends to the Replication Server:
distribute @origin_time='Apr 15 1988 10:23:23.010PM', @origin_qid=0x000000000000000000000000000000000000000 0000000000000000000000377,@tran_id=0x0000000000000000 00000372 dump tran stdb devdb 'Apr 15 1988 10:23:23.011PM'0x000000000000000000000000000000000000 0000000000000000000000000377
