Q: 14
You must design an Oracle Data Guard configuration for a DSS database that meets these permanent
requirements:
1. Creating and maintaining bitmap indexes should not impact the performance of the primary
database.
2. Creating and maintaining materialized views should not impact the performance of the primary
database.
Additionally, there are these requirements, only one of which is ever done at any one time:
1. It should be possible to apply designated patches with a minimum amount of downtime.
2. Upgrading to a new database release should be performed with the least possible amount of
downtime.
3. New application software releases should be tested against an exact and up-to-date replica of the
primary database.
Which configuration meets these requirements with the fewest of databases?
Options
Discussion
Option A fits best. Logical standby lets you run DDL like bitmap indexes and materialized views separate from the primary so there's no performance hit, and you can still do rolling upgrades plus app testing easily. Really clear scenario breakdown here, I think A covers all needs with just one standby.
Wouldn’t a physical standby fail the DDL isolation test since it can’t handle those changes off primary? Feels like only logical satisfies both parts.
Be respectful. No spam.
