Which two are true about rolling release upgrades in a …

Which two are true about rolling release upgrades in a Data Guard environment?

Which two are true about rolling release upgrades in a Data Guard environment?

A.
The background process DMON must be enabled on the primary and standby databases during a rolling
release upgrade procedure.

B.
A physical standby database can be converted to a logical standby database temporarily.

C.
Rolling release upgrades require the background process RVWR to write flashback logs on the standby
database.

D.
The KEEP IDENTITY clause ensures that a logical standby database keeps the same DBID as the primary
database.

E.
The recovery point objective increases proportionally to the duration of the rolling release upgrade
procedure.

Explanation:
D: Performing a Rolling Upgrade With an Existing Physical Standby Database
Step 1 Prepare the primary database for a rolling upgrade (perform these steps on Database A)
Step 2 Convert the physical standby database into a logical standby database (perform these steps on
Database B)
Includes:
issue the following command:
SQL> ALTER DATABASE RECOVER TO LOGICAL STANDBY KEEP IDENTITY;
SQL> ALTER DATABASE OPEN;
https://docs.oracle.com/database/121/SBYDB/rollup.htm#SBYDB4884



Leave a Reply 3

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


Benjamin Kurschies

Benjamin Kurschies

don’t you think this question is related to the 12.1 new feature “DBMS_ROLLING”? therefore I think B and C must be correct:
B is done automatically when you execute “BMS_ROLLING.START_PLAN” procedure
C is needed to convert the logical standby back into a physical standby (it’s not really converted but flash backed and recovered) and is also automatically enabled when you start the plan.

source: https://docs.oracle.com/database/121/SBYDB/dbms_rolling_upgrades.htm#SBYDB5230