Which three statements are true about snapshot standby databases?
Which three statements are true about snapshot standby databases?
Snapshot standby databases can have tables dropped, as this involves DML operations which are allowed. The broker may be used to fail over, but the snapshot standby database must first be converted to a physical standby database. Tablespaces can also be created, as this operation is typically permitted to test functionalities or changes. Importantly, snapshot standby databases need to be converted back to physical standby states to apply the redo data.
Answer: B, C and E
BCE - tablespaces cannot be dropped. C not entirely correct because a snapshot must be converted to a physical standby first. But the following steps can both be done via DGMGRL: 1. conversion to physical 2. failover to the new physical
A is wrong, you cannot drop a tablespace the restore point will generate an ORA-38881. Correct answer: B C E
Snapshot Standby Databases: Overview A snapshot standby database is a fully updatable standby database that is created by converting a physical standby database to a snapshot standby database. A snapshot standby database receives and archives—but does not apply—redo data from a primary database. Redo data received from the primary database is applied when a snapshot standby database is converted back to a physical standby database, after discarding all local updates to the snapshot standby database.
Answe ABE Every operation DML or DDL are allowed because Flashback Database can undo later