Examine this list of possible steps:
1.Raise the compatibility level on both databases.
2.Restart SQL Apply on the upgraded logical standby database.
3. Start SQL Apply on the old primary database.
4. Perform a Switchover to the logical standby database.
5. Upgrade the logical standby database.
6. Upgrade the old primary database.
Which is the minimum number of steps in the correct order, to perform a rolling release upgrade of a data
guard environment using an existing logical standby database and to enable the new functionality?
A.
5, 2, 4, 3, 6, 1
B.
1, 5, 2, 4, 6, 3
C.
5, 2, 4, 6, 3, 1
D.
4, 6, 5, 2, 3, 1
E.
5, 2, 4, 1
Explanation:
Execution: Execution of the rolling upgrade has five stages.
Stage 1 (5): The DBMS_ROLLING.START_PLAN procedure starts the execution of the rolling upgrade. Thisconverts the LGM database, the future primary database, to a logical standby and starts the SQL Apply
process at the LGM.
Stage 2 (2): You upgrade the database software at the databases that are part of the leading group. You also
run the upgrade scripts at the LGM. After this is done, you must restart SQL Apply processes at the LGM
database.
Stage 3 (4): After the apply lag reaches a given threshold (set to 10 minutes by default, but can be configured
during the specification stage), the DBMS_ROLLING.SWITCHOVER procedure proceeds with the switchover
operation. When the switchover is complete, the LGM becomes the primary database.
Stage 4 : The LGM is now the primary database running the new database software and the databases in the
leading group are protecting it. The TGM is mounted and the databases in the trailing group are still running the
older version of the database software. You must prepare the TGM and TGS databases for upgrade by
upgrading the database software and re-mounting the databases on the higher version binaries.
Stage 5 (3, 6): Execute the DBMS_ROLLING.FINISH_PLAN procedure at the current primary database
(originally the LGM). It reinstates all the databases in the trailing group to become the standbys of the current
primary database, and restarts the apply processes. The FINISH_PLAN procedure waits for all databases in
the trailing group to be upgraded to the new release (although the database software for the trailing group
databases was changed in Stage 4, the data dictionary of the trailing group databases, except for any logical
standbys in the trailing group, are updated based on media recovery of the redo generated during the upgrade
at the LGM database).
Note: To upgrade the database software in an Oracle Data Guard configuration in a rolling fashion, you first
designate a physical standby as the future primary database.
Conceptually, the rolling upgrade process splits the Oracle Data Guard configuration into two groups: the
leading group (LG) and the trailing group (TG).
Databases in the leading group are upgraded first; hence the name leading group. The leading group contains
the designated future primary database, and the physical standbys that you can configure to protect the
designated future primary. The future primary is first converted into a logical standby database and then the
new database software is installed on it and the upgrade process is run. Other standby databases in the
leading group also must have their software upgraded at this point.
https://docs.oracle.com/database/121/SBYDB/dbms_rolling_upgrades.htm
I think that is:
1o (5) apply the upgrade on the standby database, that will be made a logical standby database and …
2o (2) start a sql apply in this logical standby databases upgraded
3o (4) perform a switchover and the logical standby databases will be made the new primary databases
4o (6) stage 4 upgrade the old primary database to the high version binaries
5o (3) in stage 5
6o (1) see above
https://docs.oracle.com/database/121/SBYDB/upgrades.htm#SBYDB5129
B.4 Modifying the COMPATIBLE Initialization Parameter After Upgrading
When you upgrade to a new release of Oracle Database, certain new features might make your database incompatible with your previous release. Oracle Database enables you to control the compatibility of your database with the COMPATIBLE initialization parameter.
After the upgrade is complete, you can increase the setting of the COMPATIBLE initialization parameter to the maximum level for the new Oracle Database release. When you are certain that you no longer need the ability to downgrade your database back to its original version, set the COMPATIBLE initialization parameter based on the compatibility level you want for your new database.
In an Oracle Data Guard configuration, if you decide to increase the setting of the COMPATIBLE initialization parameter after upgrading, then it is important that you perform the following steps in the order shown (be sure the standby database has a COMPATIBLE setting equal to, or higher than, the primary):
Increase the value of the COMPATIBLE initialization parameter on all standby databases in the configuration first, as follows:
Ensure that apply is current on the standby database(s).
On one instance of each standby database, execute the following SQL statement:
ALTER SYSTEM SET COMPATIBLE= SCOPE=SPFILE;
If Redo Apply or SQL Apply is running, then stop them.
Restart all instances of the standby database(s).
If you previously stopped Redo Apply or SQL Apply, then restart them.
Increase the value of the COMPATIBLE initialization parameter on the primary database, as follows:
On one instance of the primary database, execute the following SQL statement:
ALTER SYSTEM SET COMPATIBLE= SCOPE=SPFILE;
Restart all instances of the primary database.
What do you think?
Correct:
1o (5) stage 1: apply the upgrade on the standby database, that will be made a logical standby database and …
2o (2) stage 2: start a sql apply in this logical standby databases upgraded
3o (4) stage 3: perform a switchover and the logical standby databases will be made the new primary databases
4o (6) stage 4: upgrade the old primary database to the high version binaries
5o (3) stage 5: start the SQL Apply process on the old primary database
6o (1) see below
Correct Ans: C – 5, 2, 4, 6, 3, 1
Rolling Upgrade by Using an Existing Logical Standby Database:
1. Prepare for the rolling upgrade by stopping SQL Apply and setting the COMPATIBLE initialization parameter.
2. Upgrade the Oracle Database software on the logical standby database and upgrade the logical standby database. (5)
3. Restart SQL Apply on the upgraded logical standby database. (2)
4. Query DBA_LOGSTDBY_EVENTS to monitor the upgraded logical standby database.
5. Begin a switchover to the upgraded logical standby database. (4)
6. Import any tables that were unsupported and modified.
7. Complete the switchover and activate user applications.
8. Upgrade the original primary database. (6)
9. Start SQL Apply on the original primary database (3)
10. Monitor events on the new logical standby database.
11. Optional: Perform a switchover to return to the original configuration.
12. Optional: Raise the compatibility level on both databases (1)
C