After converting your physical standby database to a logical database, you get an error:
DGMGRL> show configuration
Configuration- proddg
Protection Mode: MaxPerformance
Databases:
prod-Primary datatabse
prodsby-Physical standby database
Error: ORA-16810 multiple errors or warnings detected for database
Fast-Start Failover: DISABLED
Configuration Status:
ERROR
How can you rectify the error?

• A.Add a logical standby database PRODSBY and enable it, thereby replacing the physical standby database metadata in the broker configuration.
• B.Remove the physical standby database PRODSBY from the broker configuration, add a logical standby database PRODSBY to the broker configuration and enable it.
• C.Reinstate the physical standby database PRODSBY as a logical standby, thereby replacing the physical standby database metadata in the broker configuration.
• D.Reinstate both the primary and physical standby databases. The broker will automatically detect that PRODSBY is a logical standby update to the metadata.

Comment: *

Name: *

Email: *

Verification: *

Examine the Data Guard configuration:
DGMGRL> show configuration;
Configuration -Animals
Protection Mode: MaxPerformance
Databases:
dogs- Primary database
sheep- Physical standby database
cats- Snapshot standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
You receive an error while attempting to raise the protection mode to Maximum Protection:
DGMGRL> edit configuration set protection mode as maxprotection:
Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode Failed.
What can you conclude based on this error?

• A.Cats is a snapshot standby database.
• B.The redo transport mode is set to ASYNC for the standby database Sheep.
• C.The redo transport mode is set to ASYNC for both standby databases.
• D.The redo transport mode is set to ASYNC for the standby database Cats.

Comment: *

Name: *

Email: *

Verification: *

You created a physical standby database PRODSBY1 from the primary database PROD using SQL and RMAN.
Which two are prerequisites for creating a Data Guard Broker configuration to manage these databases?
(Choose two.)

• A.The standby database must have supplemental logging enabled.
• B.The primary database must have FORCE LOGGING enabled.
• C.The DG_BROKER_START parameter must be set to TRUE for both database instances.
• D.The primary database must have supplemental logging enabled.
• E.A local net service name to enable connectivity to the PRODSBY1 database instance must be defined on the primary database host.

Comment: *

Name: *

Email: *

Verification: *

Which three statements are true about Data Guard database modes and states? (Choose three.)

• A.A primary database may ship redo directly to more than mine standby databases.
• B.Force Logging Mode is not required for a primary database but is recommended.
• C.A Logical Standby Database can be in MOUNT state while applying changes.
• D.The Primary Database can operate in noarchivelog mode.
• E.Databases in a Data Guard Configuration need not operate in Flashback Logging mode.

Comment: *

Name: *

Email: *

Verification: *

Which three are true about using RMAN in a Data Guard environment?

• A.A recovery catalog is required when RMAN is used to take backups from a logical standby database in a Data Guard configuration if you plan to recover the primary using those backups.
• B.Backups of archived redo logs taken on a physical standby are interchangeable with a primary.
• C.A recovery catalog is required when RMAN is used to take backups from a physical standby database if you plan to recover the primary using those backups.
• D.Backups of control files taken on a physical standby are not interchangeable with a primary.
• E.Backups of data files taken on a physical standby are interchangeable with a primary.

Comment: *

Name: *

Email: *

Verification: *