|Oracle® Data Guard Broker
11g Release 2 (11.2)
Part Number E17023-03
This appendix guides you through the process of upgrading or downgrading the Oracle databases and Oracle Enterprise Manager in a broker configuration. It contains the following topics:
Delete (remove) the release 9.2.0 broker configuration using Data Guard Manager or DGMGRL release 9.2.0. For example, the DGMGRL
REMOVE CONFIGURATION command can be used.
If using DGMGRL, clear the
n initialization parameter settings by using the
ALTER SYSTEM SET LOG_ARCHIVE_DEST_n
=" " SQL*Plus command.
Upgrade the database software to Oracle release 11.2. See the Oracle Database installation documentation that is appropriate for your operating system.
See Also:My Oracle Support note 787461.1 at
http://support.oracle.comfor information about which versions of Enterprise Manager Grid Control are required to manage the full set of Data Guard features in various Oracle Database releases
If you are using DGMGRL release 9.2.0, you must upgrade to Data Guard command-line interface release 11.2:
DGMGRL release 9.2.0 is not compatible with Oracle Data Guard release 11.2.
Note:Existing Oracle9i command-line scripts are supported in Oracle Database 11.2 for non-Oracle RAC databases. See Appendix A for information about deprecated commands.
DGMGRL release 11.2 is not compatible with Oracle Data Guard release 9.2.0.
Note:Oracle Database 11.2 command-line scripts are not supported in Oracle9i.
Invoke Enterprise Manager or the DGMGRL command-line interface, and re-create the broker configuration.
If you are currently running an Oracle Data Guard release 10.n or 11.1 configuration, you can upgrade the database software to Oracle release 11.2 using the Oracle Database installation documentation that is appropriate for your operating system.
Note:Prior to Release 11.2, the configuration file was restricted to reside only on disks having the same sector size (physical block size) as that upon which the file was initially created. This was not a problem because there was typically a single sector size in use within a given broker configuration. In anticipation of having mixed sector sizes somewhere within a given broker configuration, the 11.2 broker configuration file is now completely insensitive to the underlying sector size, so long as the sector size is 4KB or less.
Conversion of the configuration file to be insensitive to the underlying sector size occurs during the upgrade processing in Step 5 below.
Issue the following DGMGRL command to disable fast-start failover:
DGMGRL> DISABLE FAST_START FAILOVER;
Disable the broker's management of the configuration and then stop the broker. For example:
Issue the following DGMGRL command to disable the broker's active management of the databases in the Data Guard configuration:
DGMGRL> DISABLE CONFIGURATION;
Issue the following SQL*Plus statement to stop the broker:
SQL> ALTER SYSTEM SET DG_BROKER_START=FALSE;
Make a copy of the current broker configuration files, as indicated by the following initialization parameters:
For step-by-step upgrade instructions, see the Oracle Database installation documentation that is appropriate for your operating system.
The DGMGRL command-line interface must also be upgraded to release 11.2 in order to manage and monitor a broker configuration running Oracle Data Guard release 11.2. DGMGRL release 11.2 cannot be used to manage Data Guard releases 10.n or 11.1.
Note:Existing release 10.n or 11.1 DGMGRL command-line scripts are supported by the DGMGRL command-line interface available in release 11.2.
Release 11.n DGMGRL command-line scripts are not guaranteed to be supported by Oracle Database release 10.n.
After the upgrade, start the release 11.2 Data Guard Broker. For example:
Issue the following SQL*Plus statements to start the broker:
SQL> ALTER SYSTEM SET DG_BROKER_START=TRUE;
Issue the following DGMGRL command to enable the broker's active management of the databases in the Data Guard configuration:
DGMGRL> ENABLE CONFIGURATION
The first time the release 11.2 broker starts, it will detect the existence of the release 10.n and 11.1 broker configuration files and automatically upgrade them to include any new properties that were introduced in release 11.2 (for example, the fast-start failover properties). This automatic conversion is transparent, permanent, and occurs only once.
Note:As of this automatic upgrade that occurs in Step 5, the configuration file may henceforth reside on a disk having any supported disk sector size (physical block size) up to and including 4KB sectors.
Note:The observer that was started prior to the upgrade will automatically be stopped and unable to observe the configuration once the upgrade is complete. You must use an 11.2 version of the Oracle Observer software to observe Oracle databases running version 11.2 or higher.
Delete (remove) the release 11.2 broker configuration using Enterprise Manager or DGMGRL release 11.2. For example, the DGMGRL
REMOVE CONFIGURATION command can be used.
Downgrade the Oracle Database software to the prior Oracle release. See the Oracle Database documentation that is appropriate for your operating system.
You can downgrade the Data Guard broker to release 10.n or 11.1 as follows:
If you are confident that you made no changes to your broker configuration after upgrading to release 11.2, you can copy the broker configuration files that you created during the upgrade procedure (described in Section B.2). Then, invoke Enterprise Manager or the DGMGRL command-line interface and reenable the broker configuration as it existed at the time you made that copy.
Alternatively, you can invoke Enterprise Manager or the DGMGRL command-line interface to re-create the broker configuration.
You can downgrade the Data Guard broker to Oracle release 9.2.0, as follows:
If you were using Enterprise Manager, you can continue to use the Oracle Enterprise Manager release 10.2 to manage your 9.2.0 broker configuration. You can also downgrade to the Data Guard Manager by re-installing Oracle Enterprise Manager release 9.2.0.
Invoke Enterprise Manager, the Data Guard Manager, or the DGMGRL command-line interface and re-create the broker configuration.