1z0-076 Exam Dumps - Oracle Database 19c: Data Guard Administration

DB_NAME

ARCHIVE_LAG_TARGET

db_file_name_convert

COMPATIBLE

FALSERVER

STANDBY_ARCHIVE_DEST

The Close_by primary database instance forwards redo to the FS_inst Far Sync instance, which forwards the redo in turn to the Far_away physical standby database instance.

The FS_inst Far Sync instance forwards redo to the Far_away physical standby only if the Close_by primary database is not able to do so.

The Far Sync instance will not forward redo to the Far_away physical standby because Fast-Start Failover is disabled.

The Close_by primary database forwards redo to the Far_away physical standby directly and also sends redo to the FS_inst Far Sync instance.

The Far Sync instance will not forward redo to the Far_away physical standby because the Protection mode is not MaxProtection.

Performing transportable tablespaces

Adding or dropping a redo file group

Adding a data file or creating a tablespace

Creating a PDB from the existing PDB within the same CDB

Renaming a data file in the primary database

Open PDBI (remote clone source) in Read Only.

Open PDBI (remote clone source) in Read Write.

Set STANDBY_PDB_SOURCE_FILE_DIRECTORY to in the london database.

Set standby_pdb_source_file_dblink to clone_link in the london database.

Enable Active Data Guard in the _ondon database.

Set STANDBY_FILE_MANAGEMENT to auto in the london database.

Configure a PRIMARY role service on the Primary and Standby and modify the Client connect descriptor to include both the Primary and the Standby.

Set the LOCAL_LISTENER parameter for all the database instances, to register services with the default listener on the primary database host.

Set the DB_NAME parameter identically on all databases; modify the connection descriptor on the clients to use DB_NAME to connect to the primary database instance.

Create a database service on the standby databases; automate the start of the service after a role change, and modify the connection descriptor on the clients to use that service.

To enable Real-Time Query on a physical standby database, a TNS entry enabling connectivity to the standby database instance must be defined on the primary database host.

To start SQL Apply on a logical standby database, a TNS entry enabling connectivity to the primary database instance must be defined on the logical standby database host.

A TNS entry enabling connectivity to the primary database instance must be defined on each of the standby database hosts.

A TNS entry or entries enabling connectivity to standby database instance(s) must be defined on the primary database host.

The LOCAL_LISTENER initialization parameter must be set to the listener used to register the primary database instance.

Their usage will always have a performance impact on the primary database.

Their creation requires that a LOG archive_dest_n parameter be defined in the standby that points back to the primary.

If the CACHE option is set then the size of the cache must be at least 100.

Their usage may have a performance impact on the physical standby database if the CACHE size is too small.

They must have the NOORDEK and CACHE options set.

Sheep will be a disabled logical standby database.

Cats will be a disabled physical standby database that can be manually enabled.

Sheep will be an enabled logical standby database.

Dogs will be the primary database.

Cats will be an enabled physical standby database.