Vce 1z0-066 Questions Latest

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).