Refreshing a Primary Database of a Replication setup into DEV/QA.
When we load a replicated database into another ASE server, it will not jump online due to the secondary truncation point that was set in the source database. In other words after the load is completed, when you issue the online database command it will fail due to the secondary truncation point that was used by the replication agent.
Error Message: Database 'DBName' cannot be brought online because it has replicated tables that may not be completely transferred. After making sure that your replication is in sync, use dbcc dbrepair to remove the secondary truncpt. |
Solution
using dbcc we can quicky remove the secondary truncation point.
dbcc dbrepair(DBName,ltmignore) go online database DBName go |