Which is the minimum number of steps in the correct ord…

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?

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.
$,2.4,3,6,1

B.
1,$,2,4,6,3

C.
$,2,4,6,3,1

D.
4,6,$,2,3,1

E.
$,2,4,1



Leave a Reply 6

Your email address will not be published. Required fields are marked *


Wim J

Wim J

incorrect

it’s B or C
The database comp level is a little bit confusing.
It’s required at the start that both database are on the highest possible value (for the current release, see dataguard study guide). *Optional*, after the upgrade process, it can be augmented to the new release compatibility.

As such, I would answer C

JFK

JFK

Raising the compatibility level of an upgraded database is one of the last steps on an upgrade, so I concur with “C”

Incorrect
A: starting the SQL Aply before the upgrade
B: compatible is the last parameter to update
D: The switchover is performed after the upgrade
E: steps missing, namely upgrading the old primary

JAC

JAC

Prepare for the rolling upgrade as follows:
Copyright © 2014, Oracle and/or its affiliates. All rights reserved.
epa e o t e o g upg ade o o s
a. Stop SQL Apply by issuing the following statement on the logical standby
database:
ALTER DATABASE STOP LOGICAL STANDBY APPLY;
b. Set the COMPATIBLE initialization parameter to the highest value. Ensure that the
COMPATIBLE initialization parameter specifies the release number for the Oracle
Database software running on the primary database prior to the upgrade.

I think B

Mafalda

Mafalda

I think C

At step 10 “Raise the compatibility level of both databases”

https://docs.oracle.com/database/121/SBYDB/rollup.htm#SBYDB4883
Performing a Rolling Upgrade With an Existing Logical Standby Database
….
1)
Ensure the COMPATIBLE initialization parameter specifies the release number for the Oracle Database software running on the primary database prior to the upgrade.
…..
…..
…..
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.

Chunn

Chunn

It is C

Rolling Upgrade by Using an Existing Logical Standby Database

Prepare for the rolling upgrade by stopping SQL Apply and setting the COMPATIBLE initialization parameter.
Upgrade the Oracle Database software on the logical standby database and upgrade the logical standby database. (5)
Restart SQL Apply on the upgraded logical standby database. (2)
Query DBA_LOGSTDBY_EVENTS to monitor the upgraded logical standby database.
Begin a switchover to the upgraded logical standby database. (4)
Import any tables that were unsupported and modified.
Complete the switchover and activate user applications.
Upgrade the original primary database. (6)
Start SQL Apply on the original primary database (3)
Monitor events on the new logical standby database.
Optional: Perform a switchover to return to the original configuration.
Optional: Raise the compatibility level on both databases (1)