Which three statements are true about snapshot standby databases?

• A.Tables can be dropped
• B.A logical standby database can be converted into a snapshot standby database.
• C.The broker may be used to fail over to a snapshot standby database.
• D.Tablespaces can be dropped.
• E.Tablespaces can be created.

Comment: *

Name: *

Email: *

Verification: *

Which two are prerequisites for configuring flashback database for Oracle 12c databases, in a Data
Guard environment?

• A.The database must be in MOUNT state.
• B.The Data Guard Broker must be used.
• C.a flash recovery area must be configured
• D.A far sync instance must be configured to flash back a standby when the primary has been flashed
  back.
• E.The database must be in ARCHIVELOG mode.

Comment: *

Name: *

Email: *

Verification: *

Which two are true about offloading backups to a physical standby database in a Data Guard environment?
(Choose two.)

• A.The standby database must be registered in an RMAN catalog after the primary database has been registered.
• B.The standby database cannot be registered in an RMAN catalog if the primary database has not been registered.
• C.Backups of the standby control file taken while connected to the catalog where the database is registered, may be used to restore the control file on the primary database.
• D.The standby database must be registered in an RMAN catalog before the primary database has been registered.

Comment: *

Name: *

Email: *

Verification: *

Examine the Data Guard configuration:
DGMGRL> show configuration:
Configuration-Animals
Protection Mode: MaxAvailability
Databases:
Sheep- Primary database
Warning: ORA-16817: unsynchronized fast-start failover configuration
Dogs - (*) Physical standby database (disabled)
ORA- 16661: the standby database needs to be reinstated
Fast-Start Failover: ENABLED
Configuration Status:
WARNING
And the fast-start failover configuration:
DGMGRL> show fast_start failover;
Fast-Start Failover: ENABLED
Threshold : 30 seconds
Target: dogs
Observer : 017.example.com
Lag Limit: 30 seconds (not in use)
Shutdown Primary: TRUE
Auto-reinstate: TRUE
Observer Reconnect: 10 seconds
Observer Override: FALSE
Configurable Failover Conditions
Health Conditions:
Corrupted Controlfile YES
Corrupted Dictionary YES
Inaccessible Logfile NO
Stuck Archiver NO
Datafile Offline YES
Oracle error Conditions:
ORA-01578: ORACLE data block corrupted (file # %s, block # %s)
And finally the reason for the fail over:
SQL> select last_failover_reason from v$fs_failover_stats;
LAST_FAILOVER_REASON
ORA-01578: ORACLE data block corrupted (file # %s, block # %s)
Identify the task, or sequence of tasks, to bring the configuration into the SUCCESS state.

• A.Bring Dogs to the NOMOUNT state and let the broker reinstate Dogs automatically.
• B.MOUNT DOGS and issue "reinstate database dogs:" at the DGMGRL prompt while connected to Dogs.
• C.MOUNT DOGS and issue "reinstate database dogs:" at the DGMGRL prompt while connected to Sheep.
• D.Open Dogs and let the broker reinstate Dogs automatically.

Comment: *

Name: *

Email: *

Verification: *

You must manually reinstate a database using DGMGRL
To which database should you connect with DGMGRL before issuing the REINSTATE command and in
which state should the target database be?

• A.The target database should be MOUNTED and DGMGRL should be connected to the primary
  database.
• B.The target database should be in NOMOUNT state and DGMGRL should be connected to any
  database that is a member of the configuration
• C.The target database should be MOUNTED and DGMGRL should be connected to any database that is
  a member of the configuration
• D.The target database should be MOUNTED and DGMGRL should be connected to the target database
• E.The target database should be in NOMOUNT state and DGMGRL should be connected to the primary
  database

Comment: *

Name: *

Email: *

Verification: *