You must propose an Oracle Data Guard configuration tor a database supporting an OLTP workload that meets these permanent requirements:
1. Data loss is not permitted.
2. Read-only applications should not connect to the primary database instance.
Additionally, there are these requirements, only one of which is ever done at any one time:
3. It should be possible to apply and test designated patches with a minimum amount of downtime.
4. Upgrading to a new database release should be performed with the least possible amount of downtime.
5. New application software releases should be tested against an exact up-to-date replica of the production database.
You propose a primary database with one physical standby database configured in Maximum Protection mode.
Which requirements do you meet?
A.
2,3, 4, and 5
B.
1,2, 3,4, and 5
C.
1 and 2
D.
only requirement 5
E.
only requirement 1
Hi
I would say only 1
for me answer is E
Any remarks
regards
2. Read-only applications should not connect to the primary database instance.
is also fullfiled. You can open physical standby to RO mode without ADG.
C
1. Data loss is not permitted
-> Max protection mode.
2. Read-only applications should not connect to the primary database instance.
-> physical standby database
Trying to figure a better answer…
The scenario meets requirements 1, 2, 3, 5
1. Data loss is not permitted
-> Max protection mode.
2. Read-only applications should not connect to the primary database instance.
-> physical standby database
3. It should be possible to apply and test designated patches with a minimum amount of downtime.
-> Standby-First Patch Apply
Oracle Data Guard Standby-First Patch Apply provides support for different database home software between a primary database and its physical standby database(s) for the purpose of applying and validating Oracle patches in rolling fashion with minimal risk to the primary database.
Reference:
https://docs.oracle.com/database/121/HABPT/schedule_outage.htm#HABPT5321
Oracle Data Guard Standby-First Patch Apply provides a supported method to apply a patch initially to a physical standby database while the primary database remains at the previous software release.
Oracle Data Guard Standby-First Patch Apply is supported between database patch releases between the primary and standby that are a maximum of one year apart from the patch release dates or the patches are within 6 versions of each other.
Reference:
Dataguard Study Guide 12c, 17-3
Oracle Patch Assurance – Data Guard Standby-First Patch Apply (Doc ID 1265700.1)
4. Upgrading to a new database release should be performed with the least possible amount of downtime.
-> Logical standby database
5. New application software releases should be tested against an exact up-to-date replica of the production database.
-> Snapshot standby database
@JFK
4. Logical stdby don’t work at Maximum protection mode. Lowering protection mode cause that first requirement (1. Data loss is not permitted.
) isn’t fully fullfiled
5. A snapshot standby database cannot be the only standby database in a Maximum Protection Data Guard configuration
Best option is C. 1 and 2
I think E
To use read-only applications on standby data guard it need configure Active Data Guard
C