We are having an issue with Q-replication. We brought down our Q-replication standby database for couple of hours for an OS upgrade. Meanwhile the capture was running on the primary database and was building up the Queue on MQ server. But unfortunately due to disaster we lost all the Queues. Now the replication needs to re-syncehd from primary. It would be grateful if someone could tell me the procedure how to accomplish this without causing an outage to the primary.
you will have to connect to primary and execute export
on target a load to refresh all data
in replication center force a manual full refresh to reset the synchpoint
Best Regards, Guy Przytula
Database Software Consultant
Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
Information Server Datastage Certified http://www.infocura.be
Thanks. The problem is that we cannot reset the synchpoint as we have another applier running for the same capture.
We had a staging database in between. We had to take a 10 mins of outage on primary to reset the synchpoint. We restored the production database to the staging database to point in time when outage was started and then kicked of a full refresh to the replicate copy from the staging database. After the refresh was done, we started the applier on replicate. The applier obviously starts applying from the redefined synchpoint which was defined during the outage.