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 DNION 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.

Show Hint

Leave a Reply 6

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

JAG

JAG

B , D correct

Create a logical standby database and execute the following command:

ALTER DATABASE RECOVER TO LOGICAL STANDBY KEEP IDENTITY;
Note: A logical standby database created with the KEEP IDENTITY clause retains
the same DB_NAME and DBID as those of its primary database.

Reply

Steampower

Steampower

in Short: B and C are correct (at least my opinion)

why? I think oracle is referencing to the new feature DBMS_ROLLING (https://docs.oracle.com/database/121/SBYDB/dbms_rolling_upgrades.htm) – and to use this feature you have to use DBMS_ROLLING only, no DGMGRL or “ALTER DATABASE” in sqlplus, otherwise it’s not working.

the process is converting a physical database temporary into a logical one, and when the update is finished back to a physical one. (so answer B should be correct). Technically it’s not possible to convert a logical standby back to a physical standby. Instead oracle is creating a guaranteed flashback restore point on the former primary during the switchover to the upgraded (transient / logical standby) database automatically. When “converting” back to physical standby, oracle is performing a flashback database and applies all archivelogs it has received from the new primary – so answer C is correct.

Reply

JFK

JFK

I don’t agree with “C”:
I see why the background process RVWR has to write flashback logs, but it’s in the instance beeing upgraded, not the standby database.

Reply

JorgeZG

JorgeZG

Pretty sure B and D.

Reply