A Changed and Deprecated Features

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

Section A.1, "Changed Features"
Section A.2, "Deprecated and Obsolete Features"

A.1 Changed Features

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

A.1.1 General Features That Changed

The following sections list features that have changed:

Changed Features in Release 10.2
Changed Features in Release 10.1

A.1.1.1 Changed Features in Release 10.2

Changed failover behavior

After failover to a logical standby database, the broker disables all standby databases in the configuration that were not directly involved in the failover. The disabled databases must be reenabled before they can serve as standby to the new primary database. Previously, failover to a logical standby database resulted in the broker disabling only physical standby databases.
Changed DelayMins property behavior

When the DelayMins property is set to 0, log apply services apply redo data to the standby database as soon as it is received, including using real-time apply if the standby database is configured with standby redo logs.

If Flashback Database is enabled on the primary database, you can reinstate the old primary database after a failover, avoiding having to perform the manual steps required to reenable a database. In addition, when failing over to a physical standby database, other physical standby databases that were not directly involved in the failover can be reinstated (if they had Flashback Database enabled prior to the failover).

Additionally, if you specified the DelayMins and RealTimeApply properties on your release 10.1 database, the delay behavior might change unexpectedly. This is due to the RealTimeApply property being deprecated in release 10.2

For example, if your release 10.1 database had the DelayMins property set to a nonzero value and the RealTimeApply property set to YES, the delay setting was ignored because the real-time apply setting overrides any delay settings. However, because in release 10.2 the RealTimeApply property is deprecated, the release 10.2 database will no longer be affected by the RealTimeApply property and unexpectedly delay the application of redo according to the time specified by the DelayMins property.

A.1.1.2 Changed Features in Release 10.1

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

See Also:
Chapter 8 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 Enterprise Manager default behavior has been reversed when removing parts of a broker configuration. Enterprise Manager 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. Enterprise Manager still provides the option of preserving these values as was done by default in previous releases.

A.1.2 Changed Properties

The following sections list properties that have changed:

Changed Properties in Release 10.2
Changed Properties in Release 10.1

A.1.2.1 Changed Properties in Release 10.2

The following properties were changed in release 10.2:

Table A-1 Changed Properties in Release 10.2

Property Name	Description of Change
`ApplyInstanceTimeout`	The default value has changed from 120 seconds to 0 seconds.
`ApplyParallel` (configurable property)	New default value is `AUTO` Can no longer specify the number of processes to use for Redo Apply
`DelayMins`	Using this property is the preferred method for delaying the application of redo data to a standby database. If you set `DelayMins` property to 0: Any previously configured `DelayMins` setting will be ignored. The standby database will apply redo data as soon as possible, including using real-time apply if the standby database is configured with standby redo logs. If you have more than one physical standby database in the configuration, Oracle recommends using Flashback Database after a failing over to a physical standby databases. You can use Flashback Database to reinstate any physical standby databases that were disabled but were not the target of the failover.
`LogArchiveMaxProcesses`	Range of valid values is now from 1 to 30 (was from 1 to 10)
`LsbyTxnConsistency`	Now imports the value of `PRESERVE_COMMIT_ORDER` from `SYSTEM.LOGSTDBY$PARAMETERS` instead of `TRANSACTION_CONSISTENCY`
`NetTimeout`	The default value has changed from 30 seconds to 180 seconds.

A.1.2.2 Changed Properties in Release 10.1

Table A-2 shows properties that changed in release 10.1:

Table A-2 Changed Properties in Release 10.1

Property Name	Description of Change
`AsyncBlocks` (configurable property)	New default value is 61,440 Note: This property has been deprecated in release 10.2.
`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`.
`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
`LogXptStatus` (monitorable property)	Output was changed to a table format.
`ParallelApply` (configurable property)	Allows input values `AUTO` and `NO`.
`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.

See Also:

Chapter 9, "Database Properties"

A.1.3 Changed State Names in Release 10.1

Table A-3 shows the state names that changed in Release 10.1:

Table A-3 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 4.2, "Database States"

A.1.4 Changed DGMGRL Features in Release 10.2

Data Guard command-line interface (DGMGRL) commands that changed in Oracle Database 10g (10.2) include:

FAILOVER
EDIT CONFIGURATION
EDIT DATABASE
SHOW CONFIGURATION

A.1.5 Changed DGMGRL Features in Release 10.1

When removing a standby database from the broker configuration, DGMGRL 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 (starting in Release 10.1) is to remove that destination. This is a reversal of the default (and only) behavior as it was implemented in the Oracle9i DGMGRL command-line interface.

A.1.6 Changed Enterprise Manager Features in Release 10.1

This section contains information about Enterprise Manager features that changed in release 10.1.

You cannot disable broker management of the broker configuration from within Enterprise Manager 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.
View Log does not view alert or broker log files.
When removing a standby database from the broker configuration, Enterprise Manager 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 Deprecated and Obsolete Features

The following sections list features that have been deprecated or made obsolete:

Deprecated and Obsolete Features in Release 10.2
Deprecated and Obsolete Features in Release 10.1

A.2.1 Deprecated and Obsolete Features in Release 10.2

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

A.2.1.1 Deprecated and Obsolete Properties in Release 10.2

Table A-4 Deprecated Properties

Deprecated Property	Replacement Property (if any)
`ApplyNext`	No replacement.
`ApplyNoDelay`	Set the `DelayMins` property to zero (0).
`AsyncBlocks`	None. Specifying the number of blocks is no longer necessary. The transport mode is determined automatically by redo transport services, based on the protection mode defined for the Data Guard configuration.
`RealTimeApply`	Set the `DelayMins` property to zero (0).

A.2.2 Deprecated and Obsolete Features in Release 10.1

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.

Also, the following sections list properties, DGMGRL commands, and Enterprise Manager features deprecated or made obsolete in release 10.1

A.2.2.1 Deprecated and Obsolete Properties in Release 10.1

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

Table A-5 Deprecated Properties

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

See Also:

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

A.2.2.2 Deprecated and Obsolete DGMGRL Commands in Release 10.1

Table A-6 shows DGMGRL commands or keywords that were deprecated or made obsolete, and indicates 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-6 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 8, "Data Guard Command-Line Interface Reference" for information about the commands that replaced deprecated commands.

A.2.2.3 Obsolete Enterprise Manager Feature in Release 10.1

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.