Re: standby database and nolog unrecoverable issue

"ff" <cfs3526_at_ureach.com> wrote in message news:WoWI6.17047$Aj1.6639370_at_typhoon2.ba-dsg.net...
> After we failover to our standby database, I found some data are not
> available, oracle complains that datafile are corrupted because nologging
> was used for some index created at production database.
>
> Does it mean that when you are using standby database, you can not use
> nologging for DDL at all? Otherwise, how can you send the redo to the
> standby site?
>

No, it means that if you use nologging operations on your primary, you need to think carefully how to propagate those things over to the standby. The standard advice is to take a copy of the datafiles for that tablespace, offline the affected datafiles on the standby and drop the tablespace, transfer the data file copies and current archived logs to the standby and perform recovery at the standby.

Having never operated a standby myself, however, I can't vouch for whether the standard advice actually works or not...

Because the datafiles are freshly copied across, the unlogged data is in them, and the standby is receiving 100% of what it needs.

The non-standard advice might well be that after performing a nologged operation, you should seriously consider re-creating the standby from scratch. If you're doing a lot of those sorts of operations, though, that probably is a little unrealistic.

Anyway: the summary version of all this is that nologging operations do pose a significant problem for standby databases, and need to be handled with care.

Regards
HJR
> You input is highly appreciated.
>
>
Received on Sat May 05 2001 - 18:28:12 CDT