Hi Chris,
It's very much doable.
We often do these types of exercise in order to reduce lag.
To begin with, stop the concerned Replicat gracefully.
GGSCI> stop replicat 'process name'
This process might take time depending on long running transactions.
Once replicat is stopped, carefully capture sequence number and rba .
Then edit replicat by commmenting the respective table you want to take away
from this replicat.
At this point you can start this replicat and you may check report file to find
that the commented table is no more used.
Next create another replicat(classic/integrated) using the old param file and
add it. Ensure this new param file contains the only table thats commented from
previous replicat. After adding this new replicat, we got to position it to the
correct sequence and rba.
GGSCI> alter replicat 'process name' extseq 87 extrba 75379
Now you may be able to start this new replicat. And it would start applying
changes from above mentioned sequence and rba.
HTH.
Thanks and Regards,
Sourav Biswas
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on behalf
of Chris Taylor <christopherdtaylor1994@xxxxxxxxx>
Sent: Saturday, January 27, 2018 11:12:02 PM
To: ORACLE-L
Subject: OGG - Can you move a table from an existing REPLICAT to a brand new
REPLICAT?
We've got a problematic table (1.6 TB) that OGG is processing a long running
update.
The current REPLICAT is 30hrs behind.
I'd like to move the table out of that REPLICAT and into a new REPLICAT by
itself.
I'm doing some searching but I'm not coming up with anything very useful.
Mainly because I'm an OGG newbie still.
Is moving a table from an existing replicat to a new replicat doable? If so,
I'd be very grateful for some tips/instructions.
This is OGG v. 12.1.2.1.170117
Thanks!
Chris
