A Data Guard Broker Changed and Deprecated Features

This appendix details the Data Guard broker features that were deprecated or changed. This appendix provides the following sections:

Section A.1, "Data Guard Broker Changed Features"
Section A.2, "Data Guard Broker Deprecated Features"

A.1 Data Guard Broker Changed Features

This section contains information about Data Guard broker features that were changed.

A.1.1 General Features That Changed

The concept of a graceful failover was renamed to complete failover while forced failover was renamed to immediate failover.

See Also:
Chapter 7 for information about the Oracle Database 10g Data Guard broker FAILOVER command
The concept of a primary site was changed to a primary database and standby site was changed to standby database. The former site object of a broker configuration was eliminated for Oracle Data Guard.
The GUI's default behavior has been reversed when removing parts of a broker configuration. The GUI now clears the archive destination parameter upon removal of a database from the broker configuration, or clears all of the parameters upon removal of the entire configuration. The GUI still provides the option of preserving these values as was done by default in previous releases.

A.1.2 Changed Properties

Table A-1 shows properties that changed:

Table A-1 Changed Properties

Property Name	Description of Change
`InconsistentLogXptProps` (monitorable property)	`STANDBY_NAME` column replaces `STANDBY_SITE_NAME`. `INSTANCE_NAME` is a new column. `MEMORY_VALUE` column replaces `DATABASE_VALUE`. `BROKER_VALUE` column replaces `METADATA_VALUE`.
`InconsistentProperties` (monitorable property)	`INSTANCE_NAME` is a new column. `MEMORY_VALUE` column replaces `DATABASE_VALUE`. `BROKER_VALUE` column replaces `METADATA_VALUE`.
`LogXptStatus` (monitorable property)	Output was changed to a table format.
`RecvQEntries` (monitorable property)	Replaces `SbyLogQueue` property. `THREAD` is a new column. `FIRST_CHANGE#` is a new column. `NEXT_CHANGE#` is a new column. `SIZE` is a new column.
`SendQEntries` (monitorable property)	`THREAD` is a new column. `STANDBY_NAME` column replaces `SITE_NAME`. `FIRST_CHANGE#` is a new column. `NEXT_CHANGE#` is a new column. `SIZE` is a new column.
`ApplyParallel` (configurable property)	New default value is `AUTO`
`AsyncBlocks` (configurable property)	New default value is `61,440`
`LogXptMode` (configurable property)	New default values are: `ASYNC` for standby databases with standby redo log files `ARCH` for standby databases without standby redo log files
`ParallelApply` (configurable property)	Allows input values `AUTO` and `NO`.

See Also:

Chapter 8, " Database Properties"

A.1.3 Changed State Names

Table A-2 shows the state names that changed:

Table A-2 State Name Changes

Database Type	State Name Prior to Oracle Database 10g	New State Name as of Oracle Database 10g
Primary	`READ-WRITE`	`LOG-TRANSPORT-OFF`
Primary	`READ-WRITE-XPTON`	`ONLINE`
Physical standby	`PHYSICAL-APPLY-READY`	`LOG-APPLY-OFF`
Physical standby	`PHYSICAL-APPLY-ON`	`ONLINE`
Logical standby	`LOGICAL-APPLY-READY`	`LOG-APPLY-OFF`
Logical standby	`LOGICAL-APPLY-ON`	`ONLINE`

See Also:

Section 3.2, "Database States"

A.1.4 Changed CLI Features

When removing a standby database from the broker configuration, the CLI provides you with a choice about removing the standby destination from the primary database so that log files are no longer transported to that standby database. The default for this choice in Oracle Database 10g is to remove that destination. This is a reversal of the default (and only) behavior as it was implemented in the Oracle9i DGMGRL CLI.

A.1.5 Changed Data Guard GUI Features

This section contains information about GUI features that changed.

You cannot disable broker management of the broker configuration from within the Data Guard GUI as had been allowed in previous releases. You can only do this from the command-line interface.
In this release of Oracle Database 10g, the Test Application feature will not be available. This feature will return in a future release of Data Guard broker.
View Log does not view alert or broker log files.

See Also:
Section 8.1.3, "LatestLog"
When removing a standby database from the broker configuration, the Data Guard GUI presents you with a choice about removing the standby destination from the primary database so that log files are no longer transported to that standby database. The default for this choice in Oracle Database 10g is to remove that destination. This is a reversal of the default as it was implemented in Oracle9i Data Guard Manager.

A.2 Data Guard Broker Deprecated Features

This section contains information about Data Guard broker features that were deprecated or are obsolete.

The concept of a site object is obsolete.
The concept of a database resource object is obsolete.

Both of these objects were replaced by database objects.

A.2.1 Deprecated Properties

Table A-3 shows properties that were deprecated and if there is a replacement property.

Table A-3 Deprecated Properties

Deprecated Property	Replacement Property (if any)
`Alternate`	No replacement
`StandbyArchiveDest`	`StandbyArchiveLocation`
`SbyLogQueue`	`RecvQEntries`

See Also:

Chapter 8, " Database Properties" for information about the properties that replaced deprecated properties.

A.2.2 Deprecated CLI Commands and Keywords

Table A-4 shows CLI commands or keywords that were deprecated and if there is a replacement command or keyword.

Note:

Existing Oracle9i command-line scripts are supported in Oracle Database 10g for non-RAC databases. Oracle recommends upgrading your scripts to replace deprecated commands and keywords with their Oracle Database 10g replacements.

Table A-4 Deprecated Commands or Keywords

Deprecated Command or Keyword	Replacement Command or Keyword
`ALTER CONFIGURATION (protection mode)`	`EDIT CONFIGURATION (protection mode)`
`ALTER CONFIGURATION (state)`	No replacement
`ALTER RESOURCE (property)`	`EDIT DATABASE (property)`
`ALTER RESOURCE (state)`	`EDIT DATABASE (state)`
`ALTER SITE (AUTO PFILE)`	`EDIT INSTANCE (AUTO PFILE)`
`ALTER SITE (state)`	No replacement
`CREATE CONFIGURATION` `PRIMARY SITE IS site-name` `RESOURCE IS resource-name` `HOSTNAME IS host-name` `INSTANCE NAME IS instance-name` `SERVICE NAME IS net-service-name` `SITE IS MAINTAINED AS standby-type`	`CREATE CONFIGURATION` `PRIMARY DATABASE IS database-name` `CONNECT IDENTIFIER IS connect-identifier`
`CREATE SITE`	No replacement
`DISABLE RESOURCE`	`DISABLE DATABASE`
`DISABLE SITE`	No replacement
`ENABLE RESOURCE`	`ENABLE DATABASE`
`ENABLE SITE`	No replacement
`FAILOVER TO site-name` `GRACEFUL` `FORCED`	`FAILOVER TO database-name` `IMMEDIATE`
`REMOVE SITE`	`REMOVE DATABASE`
`SHOW CONFIGURATION VERBOSE property-name`	`SHOW CONFIGURATION`
`SHOW DEPENDENCY TREE`	No replacement
`SHOW LOG`	No replacement
`SHOW RESOURCE`	`SHOW DATABASE`
`SHOW SITE`	No replacement
`SWITCHOVER TO site-name`	`SWITCHOVER TO database-name`

See Also:

Chapter 7, " Data Guard Command-Line Interface Reference" for information about the commands that replaced deprecated commands.

A.2.3 Data Guard GUI Features That Are Deprecated

This section contains information about GUI features that are deprecated.

The Add Site wizard is obsolete and has been replaced by the Add Standby Database wizard. Use the Add Standby Database wizard to create a broker configuration and to create new or add existing standby databases to the broker configuration.