Missing rows in replication after adding new tables
edited Feb 19, 2014 12:00PM in GoldenGate, Streams and Distributed Database (MOSC) 6 commentsAnswered
Hello,
I am testing adding new tables to a already running replication with Streams. The source database is 10.2.0.5 and the target database is 11.2.0.4
I am only replicating 2 tables. table1 was already replicating fine and I was adding table2
When I add the rules for the new table I do the following.
- Stop capture
-Stop apply
- Add rules to capture process with DBMS_STREAMS_ADM.ADD_TABLE_RULES.
- Add rules to propagation with DBMS_STREAMS_ADM.ADD_TABLE_RULES.
- Set instantiation in target for new table
- exp with flashback_scn, import new table
- give table privs to streams adm.
- add apply rules for new table with DBMS_STREAMS_ADM.ADD_TABLE_RULES.
I am testing adding new tables to a already running replication with Streams. The source database is 10.2.0.5 and the target database is 11.2.0.4
I am only replicating 2 tables. table1 was already replicating fine and I was adding table2
When I add the rules for the new table I do the following.
- Stop capture
-Stop apply
- Add rules to capture process with DBMS_STREAMS_ADM.ADD_TABLE_RULES.
- Add rules to propagation with DBMS_STREAMS_ADM.ADD_TABLE_RULES.
- Set instantiation in target for new table
- exp with flashback_scn, import new table
- give table privs to streams adm.
- add apply rules for new table with DBMS_STREAMS_ADM.ADD_TABLE_RULES.
0