Recovering Nondurable Databases
If your database is configured with the TRANSMIT NONDURABLE option in a bidirectional configuration, you do not need to take any action to recover a failed master database.
See Automatic Catch-Up of a Failed Master Database.
For other types of configurations, if the master database configured with the
TRANSMIT NONDURABLE
option fails, you must use
ttRepAdmin
-duplicate
or
ttRepDuplicateEx
to re-create the master database from the most
current subscriber database. If the application attempts to reconnect to the master
database without first performing the duplicate operation, the replication agent
recovers the database, but any attempt to connect results in an error that advises you
to perform the duplicate operation. To avoid this error, the application must reconnect
with the ForceConnect
first connection attribute set to 1.