Switching Goldengate to new colone db
We are planning to shift/switch goldengate to a new database , In our current configuration we have db which we planning to clone on server acts as both source and target (not bi directional) but we have data which moves out and incomming data from other server ,hence the db acts as both source and target.
The current plan to is to stop all the batch jobs/txns on the db and then goldengate on the server. Along with the pumps the on the remote(source) server , then clone db to a new server.
But prob is remote(source) db from where the txns are comming will be up and running . During the clonning process which we expect to take about 8 hrs the txns will pile up on the remote(source) db , under normal circumstance starting the pump will replicat all the data .