P
Pieterm
Guest
We have a customer that stops replication for a short period every day for a point in time data warehouse report to run on the target, but on quite a few instances we had to restart the replication server to complete partial transaction which was 'locked' and could not be read. So stopping the replciation server online of offline will result in this scenario whereby a target database could have in-completed transactions. Both an online and offline enhancement would thus be very useful. Offline: The database shutdown utility should allow for a new parameter that does the normal shutdown steps but first ensures the AI is 100% in sync (similar to what is done during the online transitioning) before shutting the replication server and archiver processes, and then the database. Thus a shutdown on the source will first ensure all the targets are sync, and all database are in a usable state. Online: The dsrutil utility should allow for an option to do a graceful terminate server, which ensure all AI notes for a transaction is completely send to all targets but any new transaction started, it's AI notes are send to the AI logs only. And once these busy AI notes are all send, can the replication server terminate. This will ensure a target database will never have partial transactions due to the replication server being terminated part way during a transactions being send across.
Continue reading...
Continue reading...