Hello,
I have encountered a situation where I have to create replicate database while there is activity on primary. I have been using scenario 3 described in document ASE-to-ASE Replication Quick Start Guide for 15.7.1. in chapter Materialization and Resynchronization.
In that scenario it is said that "It is assumed that activity cannot be stopped at the primary database while the database dump is in progress."
But in my current situation, replicate database is on different platform, and I have to obey the procedure for cross platform migration which said:
"Adaptive Server cannot load this database because the database that was dumped was not quiescent when the dump was performed. Run sp_flushstats before DUMP DATABASE and ensure that the database is not updated during the dump."
So, from one point I can not stop the activity on primary, but for creating cross platform dump I have to stop this activity, or if I do not do this, I will encounter a problem during loading that database into replicate database.
So, my question is - how to reconcile these two opposites?
Best regards,
Vojislav Depalov