Re: STAND-BY Database with different DB_NAME ?

Hello,

You right. Stand by database is not the answer of your problem. It's not because the standby db must be excactly the same as you active db. It must be because the updates include in the archivelog are replayed in the standby db using the row id. Then you need to keep exactly the same db structure. Moreover, your standby db still in a mount mode then you can't change anything in this one.

To sort your issue out, it could be better to use repliction activity (not easy to set up) or to manage your standby db with the "log minner". It allow you to keep your standby db up and running and to rerun your archivelog query by query. Unfortunatly this option is not available yet. It will probably be with the release 9.0.2.

Yann

marwansamara_at_msn.com (Marwan Samra) wrote in message news:<70d9d132.0201061808.52d90d74_at_posting.google.com>...
> I have 2 databases with the following characteristics:
> 1. The DB_NAME is different (A & B).
> 2. The TableSpaces are NOT exactly the same. (B has less tablespaces,
> they are not needed in in database B)
> 3. I want to keep the rest of the tables in sync.
> The question I have:
> What is the best and simple way to accomplish the above (#3)?
> I Thought of the STAND-BY option, but the more I read about it, the
> less I think it would benefit me in this case !
>
> Thanks for your help in advance.
>
> Marwan Samara.
Received on Mon Jan 07 2002 - 08:05:36 CST