Re: standby database with RAC cluster?

Wijbrand,

This works just fine, and is actually the typical implementation for most databases.
The multiple primary instances simply send all archivelogs to the single standby
instance, where the Managed Recovery is running. This is fairly straight-forward.
A standby database is not really considered a RAC or non-RAC database, since recovery can only run on a single instance, anyways.

The "gotcha" to watch out for is, after a switchover or failover, you have a single-instance "new" primary that has multiple *enabled* threads. Since the new primary is not a RAC database, you will need to disable unused threads; otherwise, they will be archived just like the active threads, but with a slight
lag that might delay the recovery of the "new" standby database.

Hope this helps.

Rick

Wijbrand Pauw wrote:

> Hi,
>
> We are going to implement RAC and also want a standby database on a other
> location.
> We were wondering if this is possible because "normally" the databases
> should be the same, in this case my standby won't be RAC of course (costs).
> The RAC cluster will create archivelog files for each cluster, a "normal"
> standby database won't understand this.
>
> Has anyone tried this before?
>
> Regards,
>
> Wijbrand Pauw
Received on Fri Oct 25 2002 - 04:56:11 CDT