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.

Backups of archived redo logs taken on a physical standby are interchangeable with a primary.

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.

Backups of control files taken on a physical standby are not interchangeable with a primary.

Backups of data files taken on a physical standby are interchangeable with a primary.

A configuration consisting only of a primary and one or more physical standby databases can support a rolling release upgrade.

A Logical Standby Database can be converted to a Snapshot Standby Database.

A Logical Standby Database can cascade redo to a terminal destination.

A Snapshot Standby Database can be a fast-start failover target.

A Physical Standby Database can be converted into a Logical Standby Database.

Real Time Query must be enabled on the primary database.

Real Time Query must be enabled on the physical standby database.

If a physically corrupt block is discovered on a physical standby database, then a valid block image from the primary database is retrieved.

If a physically corrupt block is discovered on the primary database, then a valid block image from a physical standby database is retrieved.

If a physically corrupt block is discovered on a logical standby database, then a valid block image from the primary database is retrieved.

If a physically corrupt block is discovered on a primary database, then a valid block image from the logically standby database is retrieved.

Client TNS entries for the databases use the correct service names for the intended service.

A service name is registered with the local listener of each database instance.

Oracle Net connectivity to the primary database instance must be established on all the standby database instances.

The LOCAL_LISTENER parameter on the primary database instance must always be set.

The standby database services must be defined statically with the Listeners running on the standby database hosts.

The DB_NAME and DB_UNIQUE_NAME parameters must be set to the same value for all the databases in the Data Guard environment.

The client applications must use the correct TNS entries when requesting connections to the database instances.

It succeeds only if SQL apply is stopped before deleting the SQL Apply filter.

It succeeds but the SQL Apply filters are not deleted.

It deletes both the SQL Apply filters.

It returns an error because the syntax to delete a SQL Apply filter must specify the same object names as specified when the filter was added.

It succeeds only if all DML statements executed on the primary have been applied on the logical standby deleting the SQL Apply filter.

In a broker configuration, the primary database name must match the DB_UNIQUE_NAME value in the database initialization parameter file.

A primary database profile may be added to the configuration prior to creating the primary database.

A standby database profile may be added to the configuration prior to creating that standby database.

A newly created broker configuration requires at least one standby database profile to be specified at the time the configuration is created.

A newly created broker configuration is in the disabled state.

If the primary database cannot write its redo to at least one synchronized standby database, then the protection level remains unchanged.

The primary database instance will remain up and running, if it cannot write redo to at least one synchronized standby database.

Transactions will not commit until all redo data needed to recover those transactions are written to the online redo log, and to the standby redo log on at least one synchronizes standby database.

Fast start failover can be enabled when making the chance.

Real time apply will be automatically turned on.

SYNC NOAFFIRM and Maximum Protection

SYNC NOAFFIRM and Maximum Availability

ASYNC and Maximum Performance

SYNC AFFIRM and Maximum Availability

SYNC AFFIRM and Maximum Protection

They can be used to skip execution of DML triggers on a table while allowing the DML to execute.

They can be used to skip ALTER SYSTEM and ALTER DATABASE commands.

They can be used to stop SQL apply if it encounters an error.

They can be used to skip all SQL statements executed on a specific pluggable database (PDB) within a standby multitenant container database (CDB).

They can only be used to skip DML statements on a table.

They can be used to skip ALTER TABLE commands on a specific tables.

They can be used to skip CREATE TABLE commands.

Sheep will be an enabled logical standby database.

Cats will be an enabled physical standby database.

Dogs will be the primary database.

Sheep will be a disabled logical standby database.

Cats will be a disabled physical standby database.

The command will execute successfully only if Oracle Net connectivity to the PROD database instance is defined on the primary host.

The command will execute successfully only if the DG_BROKER_START initialization is set to TRUE for the PROD database instance.

The PRODSBY1 standby database is automatically added to the configuration if DG_BROKER_START IS TRUE for PRODSBY1.

The Data Guard Broker configuration files is automatically created in the destinations specified by the DG_BROKER_CONFIG_FILEn initialization parameters on the primary database.

The PRODSBY1 standby database is automatically added to the configuration if Oracle Net connectivity to the PRODSBY1 database instance is defined on the primary host.

The command will execute successfully only if Oracle Net connectivity to the PROD and PRODSBY1 database instances are defined on the primary host.