Oracle 1z0-066 Dumps

A: Before you create a standby database you must first ensure the primary database is properly configured.

Place the primary database in FORCE LOGGING mode.

B: If archiving is not enabled, issue the following SQL statements to put the primary database in ARCHIVELOG mode and enable automatic archiving:

SQL> SHUTDOWN IMMEDIATE;

SQL> STARTUP MOUNT;

SQL> ALTER DATABASE ARCHIVELOG;

SQL> ALTER DATABASE OPEN;

References:

This is accomplished by shipping redo directly from the primary database log

References:

B: For automatic block media recovery to work, a physical standby database must be in real-time query mode, which requires an Oracle Active Data Guard license.

D: A physical standby database operating in real-time query mode can be used to repair corrupt data blocks in a primary database.

C: If corruption occurs on the primary database, blockmedia recovery is performed automatically using a good copy of the block from the standby database and vice versa.

References:

The Maximum Availability protection mode provides the highest level of data protection that is possible without compromising the availability of a primary database.

When a transport is performed using SYNC/AFFIRM, the primary performs write operations and waits for acknowledgment that the redo has been transmitted synchronously to the physical standby and written to disk. A SYNC/AFFIRM transport provides an additional protection benefit at the expense of a performance impact caused by the time required to complete the I/O to the standby redo log.

References:

Note: LOG_ARCHIVE_DEST_n specifies an alternate archiving destination to be used when the original destination fails.

The ALTERNATE attribute is optional. If an alternate destination is not specified, then redo transport services do not automatically change to another destination if the original destination fails.

References:

References:

C: Prerequisites that must be met before the broker allows you to enable fast-start failover include: Enable Flashback Database and set up a fast recovery area on both the primary database and the target standby database.

E: Introduced in 11g, snapshot standby allows the standby database to be opened in read-write mode. When switched back into standby mode, all changes made whilst in read-write mode are lost. This is achieved using flashback database, but the standby database does not need to have flashback database explicitly enabled to take advantage of this feature, thought it works just the same if it is.

References:

Configure the following database settings before enabling Flashback Database:

You must have a fast recovery area enabled, because flashback logs can only be stored in the fast recovery area.

Your database must be running in ARCHIVELOG mode, because archived logs are used in the Flashback Database operation.

For Oracle Real Application Clusters (Oracle RAC) databases, the fast recovery area must be in a clustered file system or in ASM.

References:

A: DB_NAME

On a primary database, specify the name used when the database was created. On a physical standby database, use the DB_NAME of the primary database.

C: Ensure the COMPATIBLE initialization parameter is set to the same value on both the primary and standby databases. If the values differ, redo transport services may be unable to transmit redo data from the primary database to the standby databases.

D: DB_FILE_NAME_CONVERT

Specify the path name and filename location of the primary database data files followed by the standby location. This parameter converts the path names of the primary database data files to the standby data file path names.

E: DB_UNIQUE_NAME

Specify a unique name for each database. This name stays with the database and does not change, even if the primary and standby databases reverse roles.

F: FAL_SERVER

Specify the Oracle Net service name of the FAL server (typically this is the database running in the primary role).

References:

C: Flashback Database is similar to conventional point-in-time recovery in its effects. It enables you to return a database to its state at a time in the recent past. Flashback Database uses its own logging mechanism, creating flashback logs and storing them in the fast recovery area. You can only use Flashback Database if flashback logs are available. Flashback Database is used to convert a snapshot standby database back into a physical standby database.

E: When we convert the physical standby database to snapshot standby database a guaranteed restore point is created. This guaranteed restore point is used to flashback a snapshot standby database to its original state.

Recovery from Loss of Datafiles on the Standby Database

References:

B: If fast-start failover is enabled, the observer will automatically reinstate the standby databases after failover has completed.

E: FastStartFailoverAutoReinstate= ‘FALSE’ means that the former primary database will not be reinstated automatically after a failover,

Note: The FastStartFailoverAutoReinstate configuration property causes the former primary database to be automatically reinstated if a fast-start failover was initiated because the primary database was either isolated or had crashed. To prevent automatic reinstatement of the former primary database in these cases, set this configuration property to FALSE.

The observer is the third party in an otherwise typical primary/standby Data Guard configuration. Only the observer can initiate FSFO failover. It's secondary job is to automatically reinstate a failed primary as a standby if that feature is enabled (the default).