Borrachito_DG_T_T

A Data Guard environment has this configuration and these attributes: 1. A primary database 2. A physical standby database named sbdb 3. The configuration is in maximum availability protection mode. Then sbdb is converted to a snapshot standby database. Which two statements are true?. The recovery time objective increases. The recovery point objective increases. sbdb can still receive redo. The protection mode is lowered to maximum performance. sbdb can still apply redo.

Which THREE statements are true about snapshot standby databases?. A snapshot standby database can have Real-Time apply enabled. FLASHBACK DATABASE is enabled automatically on a snapshot standby database after converting it from a physical standby database if not already enabled. FLASHBACK DATABASE is enabled automatically on a physical standby database as part of the conversion into a snapshot standby database, if not already enabled. FLASHBACK DATABASE must be manually enabled on a physical standby database before converting it into a snapshot standby database. A snapshot standby database may be opened read-write. A snapshot standby database may be opened read-only.

Which THREE statements are true about snapshot standby databases?. A snapshot standby database must be opened at least once in read-write mode before it can be converted into a physical standby database. A guaranteed restore point is created automatically when a physical standby database is converted into a snapshot standby database. Snapshot standby databases may be used for rolling database upgrades. A snapshot standby database can be the only standby database in a Maximum Protection Oracle Data Guard configuration. If datafiles grow while a database is a snapshot standby database, then they shrink when converted back to a physical standby database.

Your Data Guard configuration consists of these components and settings: 1. A primary database 2. A remote physical standby database 3. Real-time query is enabled 4. Redo transport mode is synchronous 5. Protection mode is maximum availability 6. The Data Guard broker is used You notice that the standby destination fails to acknowledge reception of redo within NET_TIMEOUT period of time. Which is true in this scenario?. The physical standby database instance is shut down by the Data Guard broker. The protection mode will automatically change to Maximum Performance. Real-time query will be disabled on the physical standby. Synchronous redo transport mode connections to the standby database are terminated.

Your Data Guard environment consists of these components and settings: 1. A primary database supporting an OLTP workload 2. A remote physical standby database 3. Real-time query is enabled 4. The redo transport mode is set to SYNC. 5. The protection mode is set to Maximum Availability. Which two statements are true regarding the DelayMins database property for the standby database?. It allows logical corruptions on the primary to be recovered by using the physical standby database. It can only be enabled for a configuration in Maximum Performance mode. It can only be enabled for a configuration in Maximum Availability mode. It allows user errors on the primary to be recovered by using the physical standby database. It enables you to bypass the default network timeout interval specified for the standby redo transport destination. It specifies a delay before the primary ships redo to the standby destination having DelayMins set.

Which TWO are prerequisites for enabling Automatic Block Media Recovery in a Data Guard environment consisting of a primary database, one physical standby database and one logical standby database?. FLASHBACK DATABASE must be enabled on the physical standby database. The logical standby database must have Real-Time Query enabled. The physical standby database must have Real-Time Apply enabled. There must be connectivity between the primary and the physical standby database. FLASHBACK DATABASE must be enabled on the primary database.

The broker configuration was created with the DGMGRL utility after creating all the databases and the far sync instance with command-line tools. What is the correct way to add this configuration to Enterprise Manager Cloud Control assuming all the nodes have been discovered already as Enterprise Manager targets?. Discover the primary database as a target in Enterprise Manager Cloud Control. Then discover the existing Data Guard Broker configuration for the primary and configuration will be discovered as targets and be ready to be monitored. Discover either of the physical standby databases as a target by refreshing the node on which they run, and the other databases and instances in the Data Guard Broker configuration will be discovered as targets automatically and be ready to be monitored. Discover the primary as a target by refreshing the node on which it runs, and the other databases and instances in the Data Guard Broker configuration will be discovered as targets automatically and be ready to be monitored. Delete the Data Guard Broker configuration using DGMGRL and then re-create it using Enterprise Manager Cloud Control to enable all the databases in the configuration as targets and to be ready to be monitored. Use the DGMRL utility to register the configuration with the Enterprise Manager Cloud Control agent on the primary database node. This will enable the configuration as targets which will be ready to be monitored.

Which feature is available when monitoring a Data Guard configuration using Enterprise Manager Cloud Control, but is not available using DGMGRL or by using SQL?. Automatic creation of standby redo logs. Performing a verify operation. Creating a broker configuration before creating the databases. Analyzing the dmon process trace file. Viewing a logical standby database apply lag.

Your Data Guard environment has two remote physical standby databases. Client applications use the local naming method to connect to the primary database instance. You want applications to automatically connect to the new primary database instance in case of a switchover or a failover. Which set of actions will fulfill this requirement?. Set DB_NAME and DB_UNIQUE_NAME identically on all databases; modify the connection descriptors on client applications to include all the standby hosts and connect to the instance using that service name. Create a database service on the primary database that is started automatically by a trigger, when the database role is PRIMARY; modify the connection descriptors on client applications to include all the standby hosts and connect to the database instance using that service name. Set the INSTANCE_NAME parameter identically on all databases; modify the connection descriptor on client applications to include all the standby hosts and connect to the instance using that service name. Create a database service on each standby database that is started automatically by a trigger, when the database role is PRIMARY; modify the connection descriptors on client applications to include all the standby hosts and connect to the database instance using that service name.

The Primary database Data Guard environment is a four-instance RAC database. There are two remote physical standby databases, each with two instances. Real-time query is enabled on the standby databases, fast-start failover is enabled for the Data Guard configuration, and the observer has been started. The clients use OCI for connectivity to the database instances. Consider this list of tasks: 1. Restart database services for the new primary database. 2. Create a database service on the primary database using DBMS_SERVICE. 3. Register all databases as clusterware resources if not already done. 4. Create and configure role-based services for all the databases. 5. Add ONS as a clusterware resource. 6. Enable Transparent Application Failover (TAF) for the services. Identify the required steps in the correct sequence to automate failover of applications to the new primary database. 2, 1, 3, 6. 3, 4, 6. 3, 1, 4, 6. 2, 1, 6. 3, 4, 5, 6.

Your Data Guard environment has two remote physical standby databases. Client applications use the local naming method to connect to the primary database instance. You want applications to automatically connect to the new primary database instance in case of a switchover or a failover. Which will fulfill this requirement?. Create a database service on each standby database that is started automatically by a trigger, when the database role is PRIMARY; modify the connection descriptors on client applications to include all the standby hosts and connect to the database instance using that service name. Set DB_NAME and DB_UNIQUE_NAME identically on all databases; modify the connection descriptors on client applications to include all the standby hosts and connect to the database instance using that service name. Set the INSTANCE_NAME parameter identically on all databases; modify the connection descriptor on client applications to include all the standby hosts and connect to the database instance using that service name. Create a database service on the primary database that is started automatically by a trigger, when the database role is PRIMARY; modify the connection descriptors on client applications to include all the standby hosts and connect to the database instance using that service name.

You must configure an Oracle Data Guard environment consisting of: 1. A primary database 2. Two physical standby databases Examine these requirements: 1. Data loss is not permitted. 2. It should be possible to convert either of the physical standby databases to a snapshot standby database. 3. Under normal operations, transactions should not commit before redo is written to disk on both the primary database and at least one standby database. 4. The availability of the primary database should not be compromised by the availability of the standby databases. 5. It should be possible to enable fast-start failover. 6. It should be possible to deploy Real Application Clusters on all databases. You configure FASTSYNC redo transport mode to both standby databases in combination with Maximum Availability mode. Which requirements will you meet?. 2, 4, 5, and 6. 1, 2, 3, 4, 5, and 6. 2, 3, 4, 5, and 6. 2, 4, and 5. 1, 2, 4, 5, and 6.

You must configure an Oracle Data Guard environment consisting of: 1. A primary database 2. One physical standby database 3. One logical standby database You must meet these requirements: 1. Primary database availability should not be compromised by the availability of the standby databases. 2. Under normal operations, transactions executed on the primary database should not commit before redo is written to disk on both the primary database and at least one standby database. Which redo transport mode and which protection mode would you configure to meet these requirements?. SYNC AFFIRM and Maximum Availability. SYNC AFFIRM and Maximum Protection. ASYNC and Maximum Performance. SYNC NOAFFIRM and Maximum Protection. SYNC NOAFFIRM and Maximum Availability.

You must configure an Oracle Data Guard environment consisting of: 1. A primary database 2. A physical standby database 3. A snapshot standby database You must meet these requirements: 1. Primary database availability should not be compromised by the availability of the standby databases. 2. Under normal operations, transactions executed on the primary database should not commit before redo is written to disk on the primary database and on at least one standby database. Which redo transport mode and which protection mode would you configure to meet these requirements?. ASYNC and Maximum Performance. SYNC AFFIRM and Maximum Protection. SYNC NOAFFIRM and Maximum Protection. SYNC AFFIRM and Maximum Availability. SYNC NOAFFIRM and Maximum Availability.

Attempting to start the observer raises an error: DGMGRL> start observer; DGM-16954: Unable to open and lock the Observer configuration file Failed. Identify two possible ways to start the observer successfully. Start the observer in a different working directory. Enable Fast-Start Failover before starting the observer. Set the ObserverOverride property to TRUE before starting the observer. Create a broker configuration and enable Fast-Start Failover before starting the observer. Start the observer using a different observer configuration file.

Attempting to start the observer raises an error: DGMGRL> start observer; DGM-16954: Unable to open and lock the Observer configuration file Failed. Identify two possible reasons for this error. There is already an observer running for this Data Guard configuration. Fast-Start Failover is not yet enabled for this Data Guard configuration. The observer configuration file is marked read-only. There is another observer running for a Data Guard configuration which uses the same observer configuration file. The broker configuration has not yet been created.

Which TWO are TRUE about offloading backups to a physical standby database in a Data Guard environment?. The standby database must be registered in an RMAN catalog after the primary database has been registered. 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. The standby database must be registered in an RMAN catalog before the primary database has been registered. The standby database cannot be registered in an RMAN catalog if the primary database has not been registered.

Which TWO are TRUE about offloading backups to a physical standby database in a Data Guard environment? (repeted). The standby database must be registered in an RMAN catalog after the primary database has been registered. 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. The standby database must be registered in an RMAN catalog before the primary database has been registered. The standby database cannot be registered in an RMAN catalog if the primary database has not been registered.

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?. The redo transport mode is set to ASYNC for both standby databases. The redo transport mode is set to ASYNC for the standby database Sheep. Cats is a snapshot standby database. The redo transport mode is set to ASYNC for the standby database Cats.