Oracle 1z0-066 Exam Practice Questions (P. 5)
- Full Access (112 questions)
- Six months of Premium Access
- Access to one million comments
- Seamless ChatGPT Integration
- Ability to download PDF files
- Anki Flashcard files for revision
- No Captcha & No AdSense
- Advanced Exam Configuration
Question #21
Examine this query and its output:
SQL> select fs_failover_status, fs_failover_current_target,
2 fs_failover_observer_present, fs_failover_oserver_host
3 from v$database:
FS_FAILOVER_STATUS FS_FAILOVER_CURRENT_TARGET
FS_FAILOVER_OBSERVER_PRESENT FS_FAILOVER_OBSERVER_HOST
--------------- ----------------------- ---------------- ------------------
BYSTANDER cats NO
O17.example.com -
Which are true?
SQL> select fs_failover_status, fs_failover_current_target,
2 fs_failover_observer_present, fs_failover_oserver_host
3 from v$database:
FS_FAILOVER_STATUS FS_FAILOVER_CURRENT_TARGET
FS_FAILOVER_OBSERVER_PRESENT FS_FAILOVER_OBSERVER_HOST
--------------- ----------------------- ---------------- ------------------
BYSTANDER cats NO
O17.example.com -
Which are true?
- AThe observer is not connected to the database on which the query was executed.Most Voted
- BCats is a bystander database.
- CThe observer is connected to the database on which the query was executed.
- DThe observer is currently running on o17.example.com.
- EThe observer is not running, but should run on o17.example.com.
Correct Answer:
A
Viewing Information About the Observer
You can find information about the observer by querying the following columns in the V$DATABASE view:
* FS_FAILOVER_OBSERVER_HOST shows the name of the computer on which the observer is running. Here it is cats.
* FS_FAILOVER_OBSERVER_PRESENT shows whether or not the observer is connected to the local database. Here the value is NO.
References:
https://docs.oracle.com/cd/B19306_01/server.102/b14230/sofo.htm
A
Viewing Information About the Observer
You can find information about the observer by querying the following columns in the V$DATABASE view:
* FS_FAILOVER_OBSERVER_HOST shows the name of the computer on which the observer is running. Here it is cats.
* FS_FAILOVER_OBSERVER_PRESENT shows whether or not the observer is connected to the local database. Here the value is NO.
References:
https://docs.oracle.com/cd/B19306_01/server.102/b14230/sofo.htm
send
light_mode
delete
Question #22
Which three are true about using RMAN in a Data Guard environment?
- AA 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.
- BBackups of archived redo logs taken on a physical standby are interchangeable with a primary.
- CA 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.
- DBackups of control files taken on a physical standby are not interchangeable with a primary.
- EBackups of data files taken on a physical standby are interchangeable with a primary.
Correct Answer:
BCE
RMAN uses a recovery catalog to track filenames for all database files in a Data Guard environment. A recovery catalog is a database schema used by RMAN to store metadata about one or more Oracle databases. The catalog also records where the online redo logs, standby redo logs, tempfiles, archived redo logs, backup sets, and image copies are created.
RMAN commands use the recovery catalog metadata to behave transparently across different physical databases in the Data Guard environment. For example, you can back up a tablespace on a physical standby database and restore and recover it on the primary database. Similarly, you can back up a tablespace on a primary database and restore and recover it on a physical standby database.
Incorrect Answers:
A: Because a logical standby database is not a block-for-block copy of the primary database, you cannot use a logical standby database to back up the primary database
D: Backups of standby control files and nonstandby control files are interchangeable. For example, you can restore a standby control file on a primary database and a primary control file on a physical standby database. This interchangeability means that you can offload control file backups to one database in a Data Guard environment. RMAN automatically updates the filenames for database files during restore and recovery at the databases.
References:
https://docs.oracle.com/cd/E11882_01/server.112/e41134/rman.htm#SBYDB4853
BCE
RMAN uses a recovery catalog to track filenames for all database files in a Data Guard environment. A recovery catalog is a database schema used by RMAN to store metadata about one or more Oracle databases. The catalog also records where the online redo logs, standby redo logs, tempfiles, archived redo logs, backup sets, and image copies are created.
RMAN commands use the recovery catalog metadata to behave transparently across different physical databases in the Data Guard environment. For example, you can back up a tablespace on a physical standby database and restore and recover it on the primary database. Similarly, you can back up a tablespace on a primary database and restore and recover it on a physical standby database.
Incorrect Answers:
A: Because a logical standby database is not a block-for-block copy of the primary database, you cannot use a logical standby database to back up the primary database
D: Backups of standby control files and nonstandby control files are interchangeable. For example, you can restore a standby control file on a primary database and a primary control file on a physical standby database. This interchangeability means that you can offload control file backups to one database in a Data Guard environment. RMAN automatically updates the filenames for database files during restore and recovery at the databases.
References:
https://docs.oracle.com/cd/E11882_01/server.112/e41134/rman.htm#SBYDB4853
send
light_mode
delete
Question #23
A customer has these requirements for their potential Data Guard implementation:
1. Zero data loss must still be guaranteed through the loss of any one configuration component.
2. The primary database must be protected against a regional disaster.
3. Performance overheads on the primary should be minimized as much as possible given these requirements.
4. Downtime on the primary database for any reason must be kept to a minimum.
Components referred to in the broker commands are:

Which Data Guard broker commands are needed to implement these requirements?
1. Zero data loss must still be guaranteed through the loss of any one configuration component.
2. The primary database must be protected against a regional disaster.
3. Performance overheads on the primary should be minimized as much as possible given these requirements.
4. Downtime on the primary database for any reason must be kept to a minimum.
Components referred to in the broker commands are:

Which Data Guard broker commands are needed to implement these requirements?
- AEDIT DATABASE prima SET PROPERY REDOROUTES= (LOCAL: physt1, FASTSYNC); EDIT DATABASE prima SET PROPERY REDOROUTES= (LOCAL: fs1 SYNC); EDIT FAR_SYNC fs1 SET PROPERTY REDORUOTES= (prima: physt2 SYNC); EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;
- BEDIT DATABASE prima SET PROPERY REDOROUTES= (LOCAL: fs1 ASYNC); EDIT FAR_SYNC fs1 SET PROPERTY REDORUOTES= (prima: physt FASTSYNC); EDIT CONFIGURATION SET PROTECTION MODE AS MAXPROTECTION
- CEDIT DATABASE prima SET PROPERY REDOROUTES= (LOCAL: fs1 SYNC); EDIT FAR_SYNC fs1 SET PROPERTY REDORUOTES= (prima: physt ASYNC); EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;
- DEDIT DATABASE prima SET PROPERY REDOROUTES=’ (LOCAL: physt1, FASTSYNC)’; EDIT DATABASE prima SET PROPERY REDOROUTES=’ (LOCAL: fs1, FASTSYNC)’; EDIT FAR_SYNC fs1 SET PROPERTY REDORUOTES=’ (prima: physt2 ASYNC)’;
Correct Answer:
A
The route between fs1 and physical standbase in the remote region, like physt2, should be SYNC or SYNC NOAFFIRM.
Note:
Fast Sync is a new Data Guard capability available with Oracle Database 12c. Fast Sync enables use of the destination parameter NOAFFIRM which specifies that the standby acknowledge receipt of redo without waiting for the write to the standby redo log file to complete. Fast Sync can improve application response time in a SYNC configuration by removing remote I/O from the total round trip time.
Active Data Guard Far Sync Architecture

Incorrect Answers:
B: There is no keyword FASTSYNC. To configure fast sync you use SYNC NOAFFIRM.
C: The route between fs1 and physical standbase in the remote region, like physt, should be SYNC, not ASYNC.
D: The route between fs1 and physical standbase in the remote region, like physt2, should be SYNC, not ASYNC.
References:
http://www.oracle.com/technetwork/database/availability/farsync-2267608.pdf
A
The route between fs1 and physical standbase in the remote region, like physt2, should be SYNC or SYNC NOAFFIRM.
Note:
Fast Sync is a new Data Guard capability available with Oracle Database 12c. Fast Sync enables use of the destination parameter NOAFFIRM which specifies that the standby acknowledge receipt of redo without waiting for the write to the standby redo log file to complete. Fast Sync can improve application response time in a SYNC configuration by removing remote I/O from the total round trip time.
Active Data Guard Far Sync Architecture

Incorrect Answers:
B: There is no keyword FASTSYNC. To configure fast sync you use SYNC NOAFFIRM.
C: The route between fs1 and physical standbase in the remote region, like physt, should be SYNC, not ASYNC.
D: The route between fs1 and physical standbase in the remote region, like physt2, should be SYNC, not ASYNC.
References:
http://www.oracle.com/technetwork/database/availability/farsync-2267608.pdf
send
light_mode
delete
Question #24
Examine the Data Guard configuration:
DGMGRL> show configuration:
Configuration-Animals -
Protection Mode: MaxAvailability
Databases:
Sheep- Primary database -
Warning: ORA-16817: unsynchronized fast-start failover configuration
Dogs (*) Physical standby database (disabled)
ORA- 16661: the standby database needs to be reinstated
Fast-Start Failover: ENABLED -
Configuration Status:
WARNING -
And the fast-start failover configuration:
DGMGRL> show fast_start failover;
Fast-Start Failover: ENABLED -
Threshold : 30 seconds -
Target: dogs -
Observer : 017.example.com -
Lag Limit: 30 seconds (not in use)
Shutdown Primary: TRUE -
Auto-reinstate: TRUE -
Observer Reconnect: 10 seconds -
Observer Override: FALSE -
Configurable Failover Conditions
Health Conditions:
Corrupted Controlfile YES -
Corrupted Dictionary YES -
Inaccessible Logfile NO -
Stuck Archiver NO -
Datafile Offline YES -
Oracle error Conditions:
ORA-01578: ORACLE data block corrupted (file # %s, block # %s)
And finally the reason for the fail over:
SQL> select last_failover_reason from v$fs_failover_stats;
LAST_FAILOVER_REASON -
ORA-01578: ORACLE data block corrupted (file # %s, block # %s)
Identify the task, or sequence of tasks, to bring the configuration into the SUCCESS state.
DGMGRL> show configuration:
Configuration-Animals -
Protection Mode: MaxAvailability
Databases:
Sheep- Primary database -
Warning: ORA-16817: unsynchronized fast-start failover configuration
Dogs (*) Physical standby database (disabled)
ORA- 16661: the standby database needs to be reinstated
Fast-Start Failover: ENABLED -
Configuration Status:
WARNING -
And the fast-start failover configuration:
DGMGRL> show fast_start failover;
Fast-Start Failover: ENABLED -
Threshold : 30 seconds -
Target: dogs -
Observer : 017.example.com -
Lag Limit: 30 seconds (not in use)
Shutdown Primary: TRUE -
Auto-reinstate: TRUE -
Observer Reconnect: 10 seconds -
Observer Override: FALSE -
Configurable Failover Conditions
Health Conditions:
Corrupted Controlfile YES -
Corrupted Dictionary YES -
Inaccessible Logfile NO -
Stuck Archiver NO -
Datafile Offline YES -
Oracle error Conditions:
ORA-01578: ORACLE data block corrupted (file # %s, block # %s)
And finally the reason for the fail over:
SQL> select last_failover_reason from v$fs_failover_stats;
LAST_FAILOVER_REASON -
ORA-01578: ORACLE data block corrupted (file # %s, block # %s)
Identify the task, or sequence of tasks, to bring the configuration into the SUCCESS state.
- ABring Dogs to the NOMOUNT state and let the broker reinstate Dogs automatically.
- BMOUNT DOGS and issue "reinstate database dogs:" at the DGMGRL prompt while connected to Dogs.
- CMOUNT DOGS and issue "reinstate database dogs:" at the DGMGRL prompt while connected to Sheep.
- DOpen Dogs and let the broker reinstate Dogs automatically.
Correct Answer:
C
The command REINSTATE DATABASE reinstates a database as a new standby database in the broker configuration for the current primary database.
References:
https://docs.oracle.com/cd/B28359_01/server.111/b28295/dgmgrl.htm#BABDACIF
C
The command REINSTATE DATABASE reinstates a database as a new standby database in the broker configuration for the current primary database.
References:
https://docs.oracle.com/cd/B28359_01/server.111/b28295/dgmgrl.htm#BABDACIF
send
light_mode
delete
Question #25
You are monitoring your Data Guard broker configuration and issue this set of DGMGRL commands:
DGMGRL> SHOW CONFIGURATION -
Configuration DRSolution -
Protection Mode: MaxPerformance -
Databases:
Close_by-Primary database -
FS_inst- Far Sync -
Far_away Physical standby database
Fast-Start Failover: DISABLED -
Configuration Status:
SUCCESS -
What is true concerning this configuration?
DGMGRL> SHOW CONFIGURATION -
Configuration DRSolution -
Protection Mode: MaxPerformance -
Databases:
Close_by-Primary database -
FS_inst- Far Sync -
Far_away Physical standby database
Fast-Start Failover: DISABLED -
Configuration Status:
SUCCESS -
What is true concerning this configuration?
- AThe 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.
- BThe far sync instance will not forward redo to the Far_away physical standby because the Protection mode is not MaxProtection.
- CThe close_by primary database forwards redo to the Far_away physical standby directly and also sends redo to the FS_inst Far Sync instance.
- DThe far sync instance will not forward redo to the Far_away physical standby because Fast-Start Failover is disabled.
- EThe 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.
Correct Answer:
A
An Oracle Data Guard far sync instance is a remote Oracle Data Guard destination that accepts redo from the primary database and then ships that redo to other members of the Oracle Data Guard configuration. A far sync instance manages a control file, receives redo into standby redo logs (SRLs), and archives those
SRLs to local archived redo logs, but that is where the similarity with standbys ends. A far sync instance does not have user data files, cannot be opened for access, cannot run redo apply, and can never function in the primary role or be converted to any type of standby database.
References:
https://docs.oracle.com/database/121/SBYDB/create_fs.htm
A
An Oracle Data Guard far sync instance is a remote Oracle Data Guard destination that accepts redo from the primary database and then ships that redo to other members of the Oracle Data Guard configuration. A far sync instance manages a control file, receives redo into standby redo logs (SRLs), and archives those
SRLs to local archived redo logs, but that is where the similarity with standbys ends. A far sync instance does not have user data files, cannot be opened for access, cannot run redo apply, and can never function in the primary role or be converted to any type of standby database.
References:
https://docs.oracle.com/database/121/SBYDB/create_fs.htm
send
light_mode
delete
All Pages