Oracle9i Data Guard Broker Release 2 (9.2) Part Number A96629-01 |
|
This section describes new features of Oracle9i Data Guard broker release 2 (9.2) and provides pointers to additional information.
Oracle9i Data Guard Release 2 (9.2) provides several new features that enhance your ability to centrally control, manage, and monitor a broker configuration. In particular, release 2 introduces support for logical standby databases as well as providing significant enhancements to the existing support for physical standby databases and Data Guard broker components.
This release provides the following new features:
The Data Guard broker configures, controls, manages, and monitors a logical standby database in much the same way as is done for a physical standby database.
A supported broker configuration in release 1 (9.0.1) supported a primary site and a single physical standby site. Now, there is support for up to nine standby sites for each broker configuration. Furthermore, support includes a mix of standby databases (both physical and logical standby databases) in a single broker configuration.
The Data Guard broker makes it very easy to switchover or failover the role of the primary site and database to one of the standby sites. The new Switchover and Failover wizards in Data Guard Manager and the new SWITCHOVER
and FAILOVER
commands available with the Data Guard command-line interface essentially reduce these complex tasks to push-button operations.
You can dynamically tune the configuration to balance data protection levels and application performance to maximize data protection, maximize availability, or maximize performance.
InconsistentLogXptProps (Inconsistent Log Transport Properties)
InconsistentProperties (Inconsistent Database Properties)
LogXptStatus (Log Transport Status)
LsbyFailedTxnInfo (Logical Standby Failed Transaction Information)
LsbyParameters (Logical Standby Parameters)
LsbySkipTable (Logical Standby Skip Table)
LsbySkipTxnTable (Logical Standby Skip Transaction Table)
SbyLogQueue (Standby Log Queue)
SendQEntries (Send Queue Entries)
Alternate
ApplyNext
ApplyNoDelay
ApplyParallel
ArchiveLagTarget
AsyncBlocks
Binding
DbFileNameConvert
DelayMins
Dependency
LogArchiveFormat
LogArchiveMaxProcesses
LogArchiveMinSucceedDest
LogArchiveTrace
LogFileNameConvert
LogShipping
LogXptMode
LsbyASkipCfgPr
LsbyASkipErrorCfgPr
LsbyASkipTxnCfgPr
LsbyDSkipCfgPr
LsbyDSkipErrorCfgPr
LsbyDSkipTxnCfgPr
LsbyMaxEventsRecorded
LsbyMaxSga
LsbyMaxServers
LsbyRecordAppliedDdl
LsbyRecordSkipDdl
LsbyRecordSkipErrors
LsbyTxnConsistency
MaxFailure
ReopenSecs
StandbyArchiveDest
StandbyFileManagement
In release 1, the Data Guard configuration file was named automatically for you using the operating system default name. Beginning with release 2, you can override the default name by setting the DG_BROKER_CONFIG_FILE
n (where n
is number 1 or 2) initialization parameters:
DG_BROKER_CONFIG_FILE1
DG_BROKER_CONFIG_FILE2
SWITCHOVER
and FAILOVER
commands for the Data Guard command-line interface.DGMGRL> ALTER SITE 'Primary' SET STATE=OFFLINE >;
This release provides the following changed or removed features:
FAL_SERVER
and FAL_CLIENT
properties; these are managed automatically by Data Guard broker.DRS_START
initialization parameter to DG_BROKER_START
.
|
Copyright © 2000, 2002 Oracle Corporation. All Rights Reserved. |
|