| Oracle® Data Guard Broker 10g Release 2 (10.2) Part Number B14230-01 |
|
|
View PDF |
| Oracle® Data Guard Broker 10g Release 2 (10.2) Part Number B14230-01 |
|
|
View PDF |
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:
If you are currently running an Oracle Data Guard release 9.0.n configuration, you must upgrade to Oracle Database release 10.n and re-create the broker configuration, as follows:
Delete (remove) the release 9.0.n broker configuration using the same release of either Enterprise Manager or DGMGRL. For example, the DGMGRL REMOVE CONFIGURATION command can be used.
Upgrade the database software to Oracle Database release 10.n. See the Oracle installation documentation that is appropriate for your operating system.
If you are using Oracle Enterprise Manager and Data Guard Manager release 9.0.n, you must upgrade to Oracle Enterprise Manager release 10.n to manage a broker configuration running Oracle Data Guard release 10.n:
Data Guard Manager release 9.0.n is not compatible with Oracle Data Guard release 10.n.
Enterprise Manager release 10.n is not compatible with Oracle Data Guard release 9.0.n. You will receive an error message stating that the Oracle database is too old.
If you are using DGMGRL release 9.0.n, you must upgrade to Data Guard command-line interface release 10.n:
DGMGRL release 9.0.n is not compatible with Oracle Data Guard release 10.n.
|
Note: Existing Oracle9i command-line scripts are supported in Oracle Database 10g for non-RAC databases. See Appendix A for information about deprecated commands. |
DGMGRL release 10.n is not compatible with Oracle Data Guard release 9.0.n.
|
Note: Oracle Database 10g command-line scripts are not supported in Oracle9i. |
Invoke the Enterprise Manager or DGMGRL, and re-create the broker configuration.
|
See Also: See Oracle Database Upgrade Guide if you are upgrading from Oracle8i Data Guard to Oracle Data Guard |
If you are currently running an Oracle Data Guard release 9.2.0 configuration, you must upgrade to Oracle Database release 10.n, and re-create the broker configuration, as follows:
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 LOG_ARCHIVE_DEST_n initialization parameter settings by using the ALTER SYSTEM SET LOG_ARCHIVE_DEST_n=" " SQL*Plus command.
Upgrade the database software to Oracle release 10.n. See the Oracle Database installation documentation that is appropriate for your operating system.
If you are using Oracle Enterprise Manager and Data Guard Manager release 9.2.0, you must upgrade to Oracle Enterprise Manager release 10.n to manage a broker configuration running Oracle Data Guard release 10.n. Data Guard Manager release 9.2.0 is not compatible with Oracle Data Guard release 10.n.
If you are using DGMGRL release 9.2.0, you must upgrade to Data Guard command-line interface release 10.n:
DGMGRL release 9.2.0 is not compatible with Oracle Data Guard release 10.n.
|
Note: Existing Oracle9i command-line scripts are supported in Oracle Database 10.n for non-RAC databases. See Appendix A for information about deprecated commands. |
DGMGRL release 10.n is not compatible with Oracle Data Guard release 9.2.0.
|
Note: Oracle Database 10.n 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.1 configuration, you can upgrade the database software to Oracle release 10.2 using the Oracle Database installation documentation that is appropriate for your operating system.
Step 1 Shut down the 10.1 Data Guard broker.
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;
Step 2 Make a copy of the current broker configuration files.
Make a copy of the current broker configuration files, as indicated by the following initialization parameters: DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2.
Step 3 Upgrade the Oracle Database software to release 10.2.
See the Oracle Database installation documentation that is appropriate for your operating system.
If you are using Oracle Enterprise Manager release 10.1, you must upgrade to Oracle Enterprise Manager release 10.2 to manage a broker configuration running Oracle Data Guard release 10.2.If you are using DGMGRL release 10.1, you must upgrade to Data Guard command-line interface release 10.2 to manage a broker configuration running Oracle Data Guard release 10.2.
|
Note: Existing release 10.1 DGMGRL command-line scripts are supported by the DGMGRL command-line interface available in release 10.1.Release 10.2 DGMGRL command-line scripts are not guaranteed to be supported by Oracle Database release 10.1. |
Step 4 Start the broker.
After the upgrade, start the release 10.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 10.2 broker starts, it will detect the existence of the release 10.1 broker configuration files and automatically upgrade them to include any new properties that were introduced in release 10.2 (for example, the fast-start failover properties). This automatic conversion is transparent, permanent, and occurs only once.
If you have upgraded to release 10.2 and want to downgrade to your prior release, you must downgrade the database release and re-create the broker configuration as follows:
Delete (remove) the release 10.2 broker configuration using Enterprise Manager or DGMGRL release 10.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 may downgrade the Data Guard broker to release 10.1, as follows:
If you are using Enterprise Manager, you may continue to use Enterprise Manager release 10.2 to manage your 10.1 broker configuration.
If you are confident that you made no changes to your broker configuration after upgrading to release 10.2, you may copy the broker configuration files that you created during the upgrade procedure (described in Section B.3). Then, invoke Enterprise Manager or the DGMGRL command-line interface and re-enable the broker configuration as it existed at the time you made that copy.
Alternatively, you may invoke Enterprise Manager or the DGMGRL command-line interface to re-create the broker configuration.
You may downgrade the Data Guard broker to Oracle release 9.2.0, as follows:
If you were using Enterprise Manager, you may continue to use the Oracle Enterprise Manager release 10.2 to manage your 9.2.0 broker configuration. You may 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.
You may downgrade to Oracle release 9.0.n, as follows:
If you were using Enterprise Manager, you must downgrade to the Data Guard Manager by re-installing Oracle Enterprise Manager release 9.0.n. The Oracle Database 10g Data Guard GUI is not compatible with Oracle Data Guard release 9.0.n.
Invoke the Data Guard Manager or the DGMGRL command-line interface and re-create the broker configuration.
