Re: Interesting Oracle Data Load Scenario

mccmx_at_hotmail.com (Matt) wrote in message news:<cfee5bcf.0405190713.a7dec31_at_posting.google.com>...
> Hello all,
>
> I have a requirement for building an environment which will allow me
> to maintain 2 synchronised copies of our production database. This is
> not for High Availability purposes or Reporting purposes but for
> segregating online users from data loading users.
>
> Here is the scenario:
>
> The online users will update the primary copy of the database and
> these changes will be copied to the second database (doesn't have to
> be realtime). A data conversion process will be loading a large amount
> of data into the secondary database at the same time.
>
> At the end of the loading process, the secondary database (which will
> be a consolidated copy of the 2 sets of changes) will be copied over
> the primary database. The reason for this is twofold....
>
> 1. We want to minimise the performance overhead of the data load
> process on the main/primary database.
>
> 2. If there is a failure/problem with the data load we want to avoid
> a point in time recovery on the primary database. Instead we can
> rebuild the secondary database from the primary and restart the
> database conversion procedure.
>
> Physical Standby is not an option since the standy DB can't be
> updated. Advanced replication is a candidate but we don't have any
> primary key constraints at the back end (Ref integrity is driven by
> the application).
>
> Can Logical Standby be used for this purpose.....?
>
> Thanks in advance..
>
> Matt

I'm not sure I quite follow all that, but it sounds like a job for transportable tablespaces with some trick table renaming and moving.

jg

--
@home.com is bogus.
I've had really good luck lately with Oracle support and their ODC. 
But I do a double-take when I look down on my menu bar and one of the
IE icons says "GotoAss".