Wait for Updates to Complete

Use this form of ttRepAdmin to assure that all the updates in the log are replicated to all subscribers before call returns.

ttRepAdmin -wait [-name receiverName] [-host receiverHostName]
[-timeout seconds] {DSN | -connStr connection_string}

Options

ttRepAdmin -wait has the options:

Option	Description
`DSN`	Indicates the data source name of the master database.
`-connStr` `connection_string`	Specifies the connection string of the master database, an ODBC connection string that specifies a database location, driver, and optionally other connection attribute settings.
`-wait`	Waits for replication to become current before continuing.
`-name` `receiverName`	Identifies the database. The database name is the last component in the database path name.
`-host` `receiverHostName`	Defines the host name or TCP/IP address of the subscriber host.
`-timeout` `seconds`	Specifies timeout value in seconds. `ttRepAdmin` returns within this amount of time, even if all updates to subscribers have not been completed.

Examples

% ttRepAdmin -wait -name receiverName -host receiverHostName
-timeout seconds -dsn DSN

The above syntax provides a way to ensure that all updates, committed at the time this program was invoked, have been transmitted to the subscriber, receiverName, and the subscriber has acknowledged that all those updates have been durably committed at the subscriber database. The timeout in seconds limits the wait.

Note:

If ttRepAdmin -wait is invoked after all write transaction activity is quiesced at a store (there are no active transactions and no transactions have started), it may take 60 seconds or more before the subscriber sends the acknowledgment that all updates have been durably committed at the subscriber.

% ttRepAdmin -wait -dsn DSN

In the above syntax, if no timeout and no subscriber name are specified, ttRepAdmin does not return until all updates committed at the time this program was invoked have been transmitted to all subscribers and all subscribers have acknowledged that all those updates have been durably committed at the subscriber database.