Professional Documents
Culture Documents
Fixed font
Go to End
Content
Type:
Creation
Date:
Last
Revision
Date:
TEXT/PLAIN
01-JUL-2002
27-OCT-2004
There is currently no automate way to invoke the Failover Procedure. The Problem is that
there is no exact Definition at which Point we should invoke the Failover. For example if
there is a Network outage between Primary and Standby Database, the Standby may consider
the Primary as down and invoke Failover by Fault. Using DGMGRL or DG Manager Failover is
simplyfied down to a single Command, but the start of this Procedure needs to be exec
uted
manually.
PURPOSE
------Oracle9i Data Guard Broker documentation explains how to set up
a Disaster Recovery Configuration (DRC) by using Oracle Enterprise
Manager (OEM).
This paper is intended to provide the following:
1. a brief overview of Oracle9i Data Guard Broker.
2. instructions on implementing DRC by using a command line utility,
called DGMRGL.
3. an overview of common maintenance operations
4. an example on debugging a typical erroneous situation
The examples are from a Windows environment but are also applicable
for UNIX.
SCOPE & APPLICATION
------------------Oracle9i DBA community
READ-WRITE
READ-WRITE-XPTON
Properties:
INTENDED_STATE
= 'READ-WRITE-XPTON'
ENABLED
= 'yes'
IGNORE_STATUS
= 'no'
LogXptMode
= 'ARCH'
Dependency
= ''
Alternate
= ''
DelayMins
= '0'
Binding
= 'OPTIONAL'
MaxFailure
= '0'
ReopenSecs
= '300'
AsyncBlocks
= '2048'
LogShipping
= 'ON'
ApplyNext
= '0'
ApplyNoDelay
= 'NO'
ApplyParallel
= '1'
StandbyArchiveDest
= 'd:\oracle\oradata\V920\standby'
LogArchiveTrace
= '0'
StandbyFileManagement
= 'AUTO'
ArchiveLagTarget
= '0'
LogArchiveMaxProcesses
= '2'
LogArchiveMinSucceedDest
= '1'
DbFileNameConvert
= 'stby , v920 '
LogFileNameConvert
= 'stby , v920 '
LogArchiveFormat
= 'ARC%S.%T'
InconsistentProperties
= '(monitor)'
InconsistentLogXptProps
= '(monitor)'
SendQEntries
= '(monitor)'
LogXptStatus
= '(monitor)'
SbyLogQueue
= '(monitor)'
Properties for 'PRIMARY' state:
DEFAULT_STATE = 'READ-WRITE-XPTON'
EXPLICIT_DISABLE = 'no'
REQUIRED
= 'yes'
Properties for 'STANDBY' state:
DEFAULT_STATE = 'PHYSICAL-APPLY-ON'
EXPLICIT_DISABLE = 'no'
REQUIRED
= 'yes'
Current status for "prim_db":
SUCCESS
3. MAINTENANCE OPERATIONS IN A DRC
----------------------------------
=> Switch the standby database between read-only and recovery mode:
DGMGRL> alter resource 'standby_db' on site 'standby_site'
set state = 'READ-ONLY';
Succeeded.
DGMGRL> alter resource 'standby_db' on site 'standby_site'
set state = 'PHYSICAL-APPLY-ON';
Succeeded.
=> Put the DRC in MaxProtection mode (Oracle9.2 onwards)
DGMGRL> alter resource 'prim_db' set property LogXptMode = 'SYNC';
Property "logxptmode" updated.
DGMGRL> alter resource 'standby_db' set property LogXptMode = 'SYNC';
Property "logxptmode" updated.
DGMGRL> alter configuration set protection mode as 'MaxProtection';
Operation requires restart of site "prim_site"
Shutting down site prim_site...
Database closed.
Database dismounted.
ORACLE instance shut down.
Restarting site prim_site...
Started "prim_site" as new primary
=> Graceful switchover from primary to standby (Oracle 9.2 onwards)
(takes around 3 minutes on a laptop)
DGMGRL> switchover to 'standby_site';
Performing switchover NOW. Please wait...
Operation requires restart of site "prim_site"
Operation requires restart of site "standby_site"
Shutting down site prim_site...
database not mounted
ORACLE instance shut down.
Shutting down site standby_site...
database not mounted
ORACLE instance shut down.
Restarting site prim_site...
Restarting site standby_site...
Started "prim_site" as standby
Started "standby_site" as new primary
Switchover succeeded. New primary is "standby_site"