Re: standby databases?

Not really enough information to go on, but it isn't enough simply to clone a database: the control file has to be a special 'standby database' control file that alllows continual application of archived redo logs.

You do this with:

ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'filename';

The fact that it's a standby controlfile allows the cloned database to sit in a permanent mount state, awaiting the continual application of redo logs (you can do more adventurous things from 8.1.5 onwards).

I have to day that having one day's-worth of archived redo lagging in the standby database rather defeats the idea of having a standby database: the whole point of a standby is that it can be switched over in a manner of minutes (at most) rather than half-hours (or worse).

Regards
HJR "Carlo Di Mascio" <carlod_at_visioneeringpartners.com> wrote in message news:JKx15.1043$Mc3.1757_at_client...
> Help anyone please,
>
> Has anyone tried to clone a database and apply the archive logs to it. so
> you have a standby database? I know how to clone the database. But I tried
> unsuccessfuly to apply the archive logs from the production db so I can
 roll
> forward. What am I doing wrong?
>
> All I'm looking todo apply archive logs to a production copy so that I
 can
> have the copy remain 1 day behind.
>
>
>
> Carlo Di Mascio
> dimasc_at_sprint.ca
>
>
Received on Wed Jun 14 2000 - 00:00:00 CDT