Controlling Replication

From: Michael Kelly <wakeboard_at_mindspring.com>
Date: 5 Feb 2003 13:30:46 -0800
Message-ID: <f489430.0302051330.cd4b42c@posting.google.com>

We would like to setup replication to support an archive database. The archive database would be updated from the production database on a daily basis using Oracle replication. Then, on a monthly basis, we would like to delete the oldest month out of the master database - but we don't want these deletes to be replicated to the replica archive database (because we want the archive database to contain all history data since the beginning of the application).

Does anyone know how we can temporarily disable replication and discard these deleted transaction before they hit the replica database?

If anyone has any other best practices in setting up an archive database (contains all data since the beginning of the application) then please provide your 2 cents!

And one last tangent question - what is the largest number of tables that you have replicated using Oracle replication - we are looking at replicating over 1,000 tables.

Thanks in advance! Received on Wed Feb 05 2003 - 15:30:46 CST