• If the database is part of an Oracle Data Guard broker configuration, then disable the broker configuration before the rolling upgrade. See Oracle Data Guard Broker for information about disabling a broker configuration.

• The Oracle Data Guard protection mode must be set to either maximum availability or maximum performance. Query the PROTECTION_LEVEL column in the V$DATABASE view to find out the current protection mode setting.

• To ensure the primary database can proceed while the logical standby database is being upgraded, the LOG_ARCHIVE_DEST_n initialization parameter for the logical standby database destination must not be set to MANDATORY.

• The COMPATIBLE initialization parameter set on the primary database must match the software release prior to the upgrade. Therefore, a rolling upgrade from release x to release y requires that the COMPATIBLE initialization parameter be set to release x on the primary database. The rolling upgrade standby database must have its COMPATIBLE initialization parameter set to x or higher.

Table 13-1 lists the steps to prepare the primary and standby databases for upgrading.

Table 13-2 lists the steps.

1. Follow these steps to prepare to perform a rolling upgrade of Oracle Software:

   1. Stop SQL Apply by issuing the following statement on the logical standby database (Database B):

      SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
      

   2. Set compatibility, if needed, to the highest value.

      Ensure the COMPATIBLE initialization parameter specifies the release number for the Oracle Database software running on the primary database prior to the upgrade.

      For example, if the primary database is running release 11.1, then set the COMPATIBLE initialization parameter to 11.1 on both databases. Be sure to set the COMPATIBLE initialization parameter on the standby database first before you set it on the primary database.

2. Upgrade Oracle database software on the logical standby database (Database B) to release y. While the logical standby database is being upgraded, it does not accept redo data from the primary database.

   To upgrade Oracle Database software, refer to the Oracle Database Upgrade Guide for the applicable Oracle Database release.

   Figure 13-2 shows Database A running release x, and Database B running release y. During the upgrade, redo data accumulates on the primary system.

   Figure 13-2 Upgrade the Logical Standby Database Release

   
   Description of "Figure 13-2 Upgrade the Logical Standby Database Release"

3. Restart SQL Apply and operate with release x on Database A and release y on Database B. To start SQL Apply, issue the following statement on Database B:

   SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
   

   The redo data that was accumulating on the primary system is automatically transmitted and applied on the newly upgraded logical standby database. The Oracle Data Guard configuration can run the mixed releases shown in Figure 13-3 for an arbitrary period while you verify that the upgraded Oracle Database software release is running properly in the production environment.

   Figure 13-3 Running Mixed Releases

   
   Description of "Figure 13-3 Running Mixed Releases"

   To monitor how quickly Database B is catching up to Database A, query the V$LOGSTDBY_PROGRESS view on Database B. For example:

   SQL> ALTER SESSION SET NLS_DATE_FORMAT = 'DD-MON-YY HH24:MI:SS';
   Session altered.
   
   SQL> SELECT SYSDATE, APPLIED_TIME FROM V$LOGSTDBY_PROGRESS;
   
   SYSDATE            APPLIED_TIME
   ------------------ ------------------
   27-JUN-05 17:07:06 27-JUN-05 17:06:50
   

4. It is recommended that you frequently query the DBA_LOGSTDBY_EVENTS view to learn if there are any DDL and DML statements that have not been applied on Database B.

   SQL> SET LONG 1000
   SQL> SET PAGESIZE 180
   SQL> SET LINESIZE 79
   SQL> SELECT EVENT_TIMESTAMP, EVENT, STATUS FROM DBA_LOGSTDBY_EVENTS -
   > ORDER BY EVENT_TIMESTAMP;
   
   EVENT_TIMESTAMP
   ---------------------------------------------------------------------------
   EVENT
   --------------------------------------------------------------------------------
   STATUS
   --------------------------------------------------------------------------------
   …
   24-MAY-05 05.18.29.318912 PM
   CREATE TABLE SYSTEM.TST (one number)
   ORA-16226: DDL skipped due to lack of support
    
   24-MAY-05 05.18.29.379990 PM
   "SYSTEM"."TST"
   ORA-16129: unsupported dml encountered
   

   In the preceding example:

   • The ORA-16226 error shows a DDL statement that could not be supported. In this case, it could not be supported because it belongs to an internal schema.

   • The ORA-16129 error shows that a DML statement was not applied.

   These types of errors indicate that not all of the changes that occurred on Database A have been applied to Database B. At this point, you must decide whether or not to continue with the upgrade procedure. If you are certain that this difference between the logical standby database and the primary database is acceptable, then continue with the upgrade procedure. If not, discontinue and reinstantiate Database B and perform the upgrade procedure at another time.

5. When you are satisfied that the upgraded database software is operating properly, perform a switchover to reverse the database roles by issuing the following statement on Database A:

   SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO LOGICAL STANDBY;
   

   This statement must wait for existing transactions to complete. To minimize the time it takes to complete the switchover, users still connected to Database A should log off immediately and reconnect to Database B.

   Note:

   The usual two-phased prepared switchover described in Performing a Switchover to a Logical Standby Database cannot be used because it requires both primary and standby databases to be running the same version of the Oracle software and at this point, the primary database is running a lower version of the Oracle software. Instead, the single-phased unprepared switchover procedure documented above is used. The unprepared switchover should only be used in the context of a rolling upgrade using a logical standby database.

   Note:

   If you suspended activity to unsupported tables or packages on Database A when it was the primary database, you must continue to suspend the same activities on Database B while it is the primary database if you eventually plan to switch back to Database A.

6. Step 4 described how to list unsupported tables that are being modified. If unsupported DML statements were issued on the primary database, then import the latest version of those tables using an import utility such as Oracle Data Pump.

   For example, the following import command truncates the scott.emp table and populates it with data matching the former primary database (A):

   impdp SYSTEM NETWORK_LINK=databasea TABLES=scott.emp TABLE_EXISTS_ACTION=TRUNCATE
   

   This command prompts you for the impdp password before executing.

7. When you are satisfied that the upgraded database software is operating properly, complete the switchover to reverse the database roles:

   1. On Database B, query the SWITCHOVER_STATUS column of the V$DATABASE view, as follows:

      SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
      
      SWITCHOVER_STATUS
      --------------------
      TO PRIMARY
      

   2. When the SWITCHOVER_STATUS column displays TO PRIMARY, complete the switchover by issuing the following statement on Database B:

      SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
      

      Note:

      The usual two-phased prepared switchover described in Performing a Switchover to a Logical Standby Database cannot be used because it requires both primary and standby databases to be running the same version of the Oracle software and at this point, the primary database is running a lower version of the Oracle software. Instead, the single-phased unprepared switchover procedure documented above is used. The unprepared switchover should only be used in the context of a rolling upgrade using a logical standby database.

   3. Activate the user applications and services on Database B, which is now running in the primary database role.

   After the switchover, you cannot send redo data from the new primary database (B) that is running the new database software release to the new standby database (A) that is running an older software release. This means the following:

   • Redo data is accumulating on the new primary database.

   • The new primary database is unprotected at this time.

   Figure 13-4 shows Database B, the former standby database (running release y), is now the primary database, and Database A, the former primary database (running release x), is now the standby database. The users are connected to Database B.

   If Database B can adequately serve as the primary database and your business does not require a logical standby database to support the primary database, then you have completed the rolling upgrade process. Allow users to log in to Database B and begin working there, and discard Database A when it is convenient. Otherwise, continue with Step 8.

   Figure 13-4 After a Switchover

   
   Description of "Figure 13-4 After a Switchover"

8. Database A is still running release x and cannot apply redo data from Database B until you upgrade it and start SQL Apply.

   For more information about upgrading Oracle Database software, see the Oracle Database Upgrade Guide.

   Figure 13-5 shows the system after both databases have been upgraded.

   Figure 13-5 Both Databases Upgraded

   
   Description of "Figure 13-5 Both Databases Upgraded"

9. Issue the following statement to start SQL Apply on Database A and, if necessary, create a database link to Database B:

   SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE NEW PRIMARY db_link_to_b;

   Note:

   You must create a database link (if one has not already been set up) and to use the NEW PRIMARY clause, because in Step 4 the single-phased unprepared switchover was used to turn Database A into a standby database.

   You must connect as user SYSTEM or with an account with a similar level of privileges.

   When you start SQL Apply on Database A, the redo data that is accumulating on the primary database (B) is sent to the logical standby database (A). The primary database is protected against data loss once all the redo data is available on the standby database.

10. Raise the compatibility level of both databases by setting the COMPATIBLE initialization parameter. You must raise the compatibility level at the logical standby database before you raise it at the primary database. Set the COMPATIBLE parameter on the standby database before you set it on the primary database. See Oracle Database Reference for more information about the COMPATIBLE initialization parameter.

11. To ensure that all changes performed on Database B are properly applied to the logical standby database (A), you should frequently query the DBA_LOGSTDBY_EVENTS view, as you did for Database A in step 4.

    If changes were made that invalidate Database A as a copy of your existing primary database, you can discard Database A and create a new logical standby database in its place. See Creating a Logical Standby Database for complete information.

12. Optionally, perform another switchover of the databases so Database A is once again running in the primary database role (as shown in Figure 13-1).

    Note:

    You use the two-phased prepared switchover described in Performing a Switchover to a Logical Standby Database since at this time, both Database A and Database B are running the same version of the Oracle software.

Table 13-3 summarizes the steps involved.

1. Prepare the primary database for a rolling upgrade (perform these steps on Database A)

   1. Enable Flashback Database, if it is not already enabled:

      SQL> SHUTDOWN IMMEDIATE;
      SQL> STARTUP MOUNT;
      SQL> ALTER DATABASE FLASHBACK ON;
      SQL> ALTER DATABASE OPEN;
      

   2. Create a guaranteed restore point:

      SQL> CREATE RESTORE POINT pre_upgrade GUARANTEE FLASHBACK DATABASE;
      

2. Convert the physical standby database into a logical standby database (perform these steps on Database B).

   1. Follow the steps outlined in Creating a Logical Standby Database except for the following difference. In Convert to a Logical Standby Database you must use a different command to convert the logical standby database. Instead of ALTER DATABASE RECOVER TO LOGICAL STANDBY db_name, issue the following command:

      SQL> ALTER DATABASE RECOVER TO LOGICAL STANDBY KEEP IDENTITY;
      SQL> ALTER DATABASE OPEN;
      

   2. You must take the following actions before you start SQL Apply for the first time:

      1. Disable automatic deletion of foreign archived logs at the logical standby, as follows:

         SQL> EXECUTE DBMS_LOGSTDBY.APPLY_SET('LOG_AUTO_DELETE', 'FALSE');

         Note:

         Do not delete any remote archived logs processed by the logical standby database (Database B). These remote archived logs are required later during the rolling upgrade process. If you are using the recovery area to store the remote archived logs, you must ensure that it has enough space to accommodate these logs without interfering with the normal operation of the logical standby database.

      2. Make sure you capture information about transactions running on the primary database that will not be supported by a logical standby database. Run the following procedures to capture and record the information as events in the DBA_LOGSTDBY_EVENTS table:

         SQL> EXECUTE DBMS_LOGSTDBY.APPLY_SET('MAX_EVENTS_RECORDED', -
         > DBMS_LOGSTDBY.MAX_EVENTS);
          
         SQL> EXECUTE DBMS_LOGSTDBY.APPLY_SET('RECORD_UNSUPPORTED_OPERATIONS', 'TRUE');
         

      3. Start SQL Apply for the first time, as follows:

         SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;

      See Also:

      • Customizing Logging of Events in the DBA_LOGSTDBY_EVENTS View for more information about the DBA_LOGSTDBY_EVENTS view

      • Oracle Database PL/SQL Packages and Types Reference for complete information about the DBMS_LOGSTDBY package

3. You can now follow Steps 1 through 7 as described in Performing a Rolling Upgrade With an Existing Logical Standby Database . At the end of these steps, Database B is your primary database running the upgraded version of the Oracle software, and Database A becomes your logical standby database.

   Move on to the next step to turn Database A into the physical standby for Database B.

4. Flashback Database A to the guaranteed restore point (perform these steps on Database A).

   SQL> SHUTDOWN IMMEDIATE;
   SQL> STARTUP MOUNT;
   SQL> FLASHBACK DATABASE TO RESTORE POINT pre_upgrade;
   SQL> SHUTDOWN IMMEDIATE;
   

5. At this point, switch Database A to use the higher version of the Oracle software. You do not run the upgrade scripts, since Database A is turned into a physical standby, and upgraded automatically as it applies the redo data generated by Database B.

   Mount Database A, as follows:

   SQL> STARTUP MOUNT;
   

6. Convert Database A to a physical standby.

   SQL> ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
   SQL> SHUTDOWN IMMEDIATE;
   

7. Start managed recovery on Database A.

   Database A is upgraded automatically as it applies the redo data generated by Database B. Managed recovery waits until the new incarnation branch from the primary is registered before it starts applying redo.

   SQL> STARTUP MOUNT;
   SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE - 
   >  DISCONNECT FROM SESSION;

   Note:

   When Redo Apply restarts, it waits for a new incarnation from the current primary database (Database B) to be registered.

8. At this point, Database B is your primary database and Database A is your physical standby, both running the higher version of the Oracle software. To make Database A the primary database, follow the steps described in "Performing a Switchover to a Physical Standby Database".

9. To preserve disk space, drop the existing guaranteed restore point created in Database A:

   SQL> DROP RESTORE POINT PRE_UPGRADE;