Re: dataguard protection mode...

From: Volker Hetzer <volker.hetzer_at_ieee.org>
Date: Thu, 28 Oct 2004 10:06:11 +0200
Message-ID: <clq99k$8s5$1@nntp.fujitsu-siemens.com>

"Joel Garry" <joel-garry_at_home.com> schrieb im Newsbeitrag news:91884734.0410271615.6c000f88_at_posting.google.com...
> "Volker Hetzer" <volker.hetzer_at_ieee.org> wrote in message news:<cloj2f$ntp$1_at_nntp.fujitsu-siemens.com>...
> > "Yong Huang" <yong321_at_gmail.com> schrieb im Newsbeitrag news:a8d66634.0410270805.7cc8c3d6_at_posting.google.com...
>
> >
> > >
> > > Just for a record. If I also omit LGWR, alter system set
> > > log_archive_dest_2 throws "ORA-16159: Cannot change protected standby
> > > destination attributes" when the database is in maximum availability
> > > mode. If I change it to max performance mode, startup mount and set to
> > > max availability mode, then alter database open throws ORA-3113.
> > Took me and the dataguard course guy a day to figure out the interplay between
> > dataguard properties and database properties but in the end we found out that
> > - dataguard (DMON) finds out if somebody has tampered with the initialisation
> > parameters and undoes the changes, giving you a lot of headaches until you figure
> > that out.
>
> Just FYI, here's some, er, Bufferin:
> http://metalink.oracle.com/metalink/plsql/ml2_documents.showFrameDocument?p_database_id=NOT&p_id=263542.1
Yes, but it's a bit misleading. You *can* change the configuration afterwards, but only through one of the DataGuard interfaces (dgmgrl or the graphical manager).

Lots of Greetings!
Volker Received on Thu Oct 28 2004 - 03:06:11 CDT