Re: dataguard protection mode...

"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

> - it's better to go through dgmgrl for the standby stuff because then it's easier to
> have consistent log_-properties.
>

jg

--
@home.com is bogus.
http://www.signonsandiego.com/news/world/20041027-1533-arafatshealth.html