After migration, restore the replication information on the database. These steps can be generated by the repl report.
Restoring primary databases
If the original primary database had warm standby on, enter:
sp_reptostandby database_name, standbystatus
The standby status of the source database is saved by sybmigrate in the migration log. Use the above command to restore the standby status.
Reset the generation ID by entering:
dbcc settrunc ("ltm", "gen_id", gen_id)
The generation ID of the source database is saved by sybmigrate in the migration log. Use the above command to restore the generation ID.
Reset the secondary truncation point:
dbcc settrunc ("ltm", "valid")
Zero the Replication Server location for this database in the RSSD of the Replication Server that this database belongs to, using:
rs_zeroltm server, database_name
If this database is an active connection of a warm standby configuration, rematerialize the standby database by dumping the primary and loading the dumps into the standby. See the Replication Server documentation for instructions.
Start the RepAgent on the primary database, using:
sp_start_rep_agent database_name
Log in to the Replication Server and restart the log transfer:
resume log transfer from server.database
