I recently had to resync a warm standby database for a customer. When I can’t stop the transactions on primary database I use the “dump marker” clause while recreating the connection to the warm standby database with replication server. Indeed, you can resync a warm standby database anytime with no downtime on the primary database side using the “dump marker” method. Let’s assume the following warm-standy architecture:
- SYBPARFRDEV01_DS as the primary dataserver
- SYBPARFRDEV02_DS as the target dataserver
- SYBPARFRDEV02_RS as the replication server
- projectdb as the primary and replicated database
