Re: maximum protected phsical standy database

Hi Arslan,
Where did you issue the 'alter database set standby database to maximize protection;' command?
Primary or standby? Can you tell me the exact commands, and their sequence when you switched to max protection mode, and to what database you issued them?

Did you create standby redologs?

What did the PROTECTION_LEVEL column of V$DATABASE tell you on the both ends, after you (thought you) switched to maximum protection mode? If that is not MAXIMUM PROTECTION, it is not MAXIMUM PROTECTION. Verify that, before forcing the thing to fail.

You say logs have been fetched. That is FAL, after a log-gap occurred. In managed standby mode logs get pushed by LGWR on the primary, not fetched by whatever process on the standby.

Further, I never tried a logswitch after shutting down the standby, as you did. Actually, that might succeed and not necessarily shutdown the primary. I always try a smallish transaction, and that will immediately cause the primary to abort. Although the opening of the remote redolog (or the fact that it fails) is reason enough to abort the primary. As I said, I never tested this.

Best regards,

Carel-Jan Engel

===
If you think education is expensive, try ignorance. (Derek Bok) ===

On Wed, 2004-12-01 at 18:14, A.Bahar_at_billing-components.com wrote:

> =20
> I have configured a physical standby database in maximum performance =
> mode by=20
> using ARCH. I have tested and It worked.
>
> Then I wanted to turn on "maximum protection mode". After I set =
> parameters ,=20
> I issued "alter database set standby database to maximize protection;".
>
> And I have tested configuration while stanby database up and running. =
> Redo=20
> logs have been fetched from primary to standby site and they have been =
> applied.
>
> And then I have shutdown standby server. I have shutdown listener on =
> standby=20
> site. And I have issued "alter system swich logfile;". Andddd... It has=20
> switched. Primary database did not shutdown as explained in metalink =
> note:239100.1.
>
> Why...? What is the wrong ? How can I realize a "maximum protected =
> physical standby database"
> Do you have any idea ?
> Is there any thing such "max.protected.phsy.standy.database" in real =
> life or is it only a fable in oracle documentation which is read to =
> children before they sleep.
>
> Rgds.
> Arslan BAHAR.
>
> Parameters on primary site ;
> ---------------------------------------------------------------
> db_name =3D ODG1
> instance_name =3D ODG1
> service_names =3D ODG1.db.corp.dir
> db_domain =3D db.corp.dir
> log_archive_start =3D TRUE
> remote_archive_enable =3D TRUE
> log_archive_format =3D "log%S_%T.arc"
> log_archive_dest_1 =3D "LOCATION=3D/disk1/oradata/admin/odg1/arch"
> log_archive_dest_state_1 =3D enable
> log_archive_dest_2 =3D "SERVICE=3Dodg2 LGWR SYNC AFFIRM"
> log_archive_dest_state_2 =3D enable
> ---------------------------------------------------------------
> parameters on standby side
> ---------------------------------------------------------------
> db_name =3D ODG1
> instance_name =3D ODG2
> service_names =3D ODG2.db.corp.dir
> db_domain =3D db.corp.dir
> log_archive_start =3D TRUE
> log_archive_format =3D "log%S_%T.arc"=20
> log_archive_dest_1 =3D "LOCATION=3D/disk1/oradata/admin/odg2/arch"
> log_archive_dest_state_1 =3D enable
> standby_archive_dest =3D "/disk1/oradata/admin/odg2/arch"
> db_file_name_convert =3D=20
> ("/disk1/oradata/odg1/","/disk1/oradata/odg2/")
> log_file_name_convert =3D=20
> ("/disk1/oradata/odg1/","/disk1/oradata/odg2/")
> standby_file_management =3D Auto
> control_files =3D=20
> ("/disk1/oradata/odg2/ctrl/odg2_cntrl01.ctl","/disk1/oradata/odg2/ctrl/od=
> g2_cnt
> r
> l02.ctl")
> -----------------------------------------------------------------------
> Protection mode of standby database=20
> ---------------------------------------------
> SQL> select=20
> name,open_mode,protection_mode,protection_level,database_role,switchover_=
> status
>
> from v$database
> 2 ;
> NAME OPEN_MODE PROTECTION_MODE PROTECTION_LEVEL DATABASE_ROLE
> --------- ---------- -------------------- -------------------- =
> ----------------
> SWITCHOVER_STATUS
> ------------------
> ODG1 MOUNTED MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE PHYSICAL STANDBY
> NOT ALLOWED
> SQL>=20
> ---------------------------------------------------------
> --
> http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l