B Upgrading Databases in a Data Guard Configuration

The procedures in this appendix describe how to upgrade to Oracle Database 11g Release 1 (11.1) when a physical or logical standby database is present in the configuration.

This appendix contains the following topics:

B.1 Before You Upgrade the Oracle Database Software

Consider the following points before beginning to upgrade your Oracle Database software:

  • If you are using the Data Guard broker to manage your configuration, follow the instructions in the Oracle Data Guard Broker manual for information about removing or disabling the broker configuration.

  • The procedures in this appendix are to be used in conjunction with the ones contained in the Oracle Database Upgrade Guide for 11g Release 1 (11.1).

  • The procedures in this appendix use the Database Upgrade Assistant (DBUA) to perform the upgrade. For instructions on performing the upgrade manually, refer to the Oracle Database Upgrade Guide. The manual upgrade steps described should be performed whenever use of DBUA is mentioned.

  • Check for nologging operations. If nologging operations have been performed then you must update the standby database. See Section 13.4, "Recovering After the NOLOGGING Clause Is Specified" for details.

  • Make note of any tablespaces or datafiles that need recovery due to OFFLINE IMMEDIATE. Tablespaces or datafiles should be recovered and either online or offline prior to upgrading.

B.2 Upgrading Oracle Database with a Physical Standby Database In Place

Perform the following steps to upgrade to Oracle Database 11g Release 1 (11.1) when a physical standby database is present in the configuration:

  1. Review and perform the steps listed in the "Preparing to Upgrade" chapter of the Oracle Database Upgrade Guide.

  2. Shut down the primary database.

  3. Shut down the physical standby database.

  4. Install the new release of the Oracle software into a new Oracle home on the physical standby database system, as described in the Oracle Database Upgrade Guide.

  5. Mount the physical standby database.

    Note:

    The standby database should not be opened until the primary database upgrade is completed.
  6. Start Redo Apply on the physical standby database.

  7. Install the new release of the Oracle software into a new Oracle home on the primary database system as described in the Oracle Database Upgrade Guide.

  8. Upgrade the primary database as described in the Oracle Database Upgrade Guide. Note that the physical standby database will be upgraded when it applies the redo generated by the primary database as it is upgraded.

  9. Open the upgraded primary database.

  10. If Active Data Guard was being used prior to the upgrade, then refer to Section 9.2.1 for information about how to reenable it after upgrading.

B.3 Upgrading Oracle Database with a Logical Standby Database In Place

Note:

This appendix describes the traditional method for upgrading your Oracle Database software with a logical standby database in place. A second method in Chapter 12, "Using SQL Apply to Upgrade the Oracle Database" describes how to upgrade with a logical standby database in place in a rolling fashion to minimize downtime. Use the steps from only one method to perform the complete upgrade. Do not attempt to use both methods or to combine the steps from the two methods as you perform the upgrade process.

The procedure described in this section assumes that the primary database is running in MAXIMUM PERFORMANCE data protection mode.

Perform the following steps to upgrade to Oracle Database 11g Release 1 (11.1) when a logical standby database is present in the configuration:

  1. Review and perform the steps listed in the "Preparing to Upgrade" chapter of the Oracle Database Upgrade Guide.

  2. Set the data protection mode to MAXIMUM PERFORMANCE at the primary database, if needed:

    SQL> ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE;
    
  3. On the primary database, stop all user activity and defer the remote archival destination associated with the logical standby database (for this procedure, it is assumed that LOG_ARCHIVE_DEST_2 is associated with the logical standby database):

    SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=DEFER SCOPE=BOTH;
    SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
    
  4. Stop SQL Apply on the standby database:

    SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
    
  5. On the primary database install the newer release of the Oracle software as described in the Oracle Database Upgrade Guide.

  6. On the logical standby database, install the newer release of the Oracle software as described in Oracle Database Upgrade Guide.

    Note:

    Steps 5 and 6 can be performed concurrently (in other words, the primary and the standby databases can be upgraded concurrently) to reduce downtime during the upgrade procedure.
  7. On the upgraded logical standby database, restart SQL Apply. If you are using Oracle RAC, start up the other standby database instances:

    SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
    
  8. Open the upgraded primary database and allow users to connect. If you are using Oracle RAC, start up the other primary database instances.

    Also, enable archiving to the upgraded logical standby database, as follows:

    SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;
    
  9. Optionally, reset to the original data protection mode if you changed it in Step 2.