Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Resetting the instantiation SCN

Re: Resetting the instantiation SCN

From: Pedro Lopes <pedro.lopes_at_netvisao.pt>
Date: Sat, 05 May 2007 23:20:48 +0100
Message-ID: <newscache$x2alhj$lyd$1@newsfront4.netvisao.pt>


Tarby777 wrote:
> Hi all,
>
> I'm setting up a Streams environment; two 9iR2 databases are involved,
> with one-way DML replication on a subset of the tables in a single
> schema. DDL changes are not replicated. In addition to receiving DML
> changes via Streams, the destination database also has users entering
> data directly.
>
> I'm wondering how to handle application upgrades in this environment.
> Our upgrade process amounts to running a SQL script that applies a
> schema delta and manipulates data, and I don't want the data
> manipulation that took place in the source database replicated in the
> target database by Streams. I'm guessing the process should go
> something like this:
>
> 1) Stop the capture process in the source database
> 2) Wait for the apply process in the target database to catch up (if
> it hasn't), then stop it
> 3) Go through the upgrade on each database
> 4) Reset the instantiation SCNs in the target database
> 5) Start the apply process
> 6) Start the capture process
>
> ...and hopefully, we carry on as before. Is that going to work? Have I
> missed something?
>
> TIA
> Tarby
>

Hi Tarby,
that can be done in an easy way.

Look at the streams documentation for TAGS.

Basically you'll need to :

This will avoid any changes made with the new TAG to be applied on the target databases.

Hope it helps,
Pedro. Received on Sat May 05 2007 - 17:20:48 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US