Oracle 1z0-066 Exam Practice Questions (P. 3)
- 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 #11
Examine the Data Guard configuration:
DGMGRL> show configuration;
Configuration Animals -
Protection Mode: MaxAvailability
Databases:
dogs- Primary database
cats- Snapshot standby database
sheep- Snapshot standby database
Fast-Start Failover: DISABLED -
Configuration Status:
ORA-01034: ORACLE not available -
ORA-16625: cannot reach database "dogs"
DGM-17017: unable to determine configuration status
You wish to perform a failover to Sheep.
Which command, or sequence of commands, should you issue to the broker before executing "failover to sheep", using the broker?
DGMGRL> show configuration;
Configuration Animals -
Protection Mode: MaxAvailability
Databases:
dogs- Primary database
cats- Snapshot standby database
sheep- Snapshot standby database
Fast-Start Failover: DISABLED -
Configuration Status:
ORA-01034: ORACLE not available -
ORA-16625: cannot reach database "dogs"
DGM-17017: unable to determine configuration status
You wish to perform a failover to Sheep.
Which command, or sequence of commands, should you issue to the broker before executing "failover to sheep", using the broker?
- ADGMGRL> convert database cats to physical standby;
- BDGMGRL> convert database sheep to physical standby;
- CDGMGRL> convert database sheep to physical standby; DGMGRL> convert database cats to physical standby;
- DDGMGRL>edit configuration set protection mode as maxperformance; DGMGRL> convert database sheep to physical standby;
- ENone, because you can directly failover to a Snapshot Standby Database.Most Voted
Correct Answer:
C
Note: Oracle Error: ORA-16625 -
Error Description:
Cannot reach the database -
Error Cause:
The broker rejected an operation requested by the client when the database required to execute that operation was not reachable from the database where the request was made. If the request modifies the configuration, the request must be processed by the copy of the broker running on an instance of the primary database.
Action:
Check your network connections between all of the databases in the configuration. Alternatively, you can connect your client to a different database in the Data
Guard broker configuration and try your request again. If you are simply attempting to determine the status of a particular database in the configuration, you may connect your client to that database and get the current value of the StatusReport property for that database.
References:
http://psoug.org/oraerror/ORA-16625.htm
C
Note: Oracle Error: ORA-16625 -
Error Description:
Cannot reach the database -
Error Cause:
The broker rejected an operation requested by the client when the database required to execute that operation was not reachable from the database where the request was made. If the request modifies the configuration, the request must be processed by the copy of the broker running on an instance of the primary database.
Action:
Check your network connections between all of the databases in the configuration. Alternatively, you can connect your client to a different database in the Data
Guard broker configuration and try your request again. If you are simply attempting to determine the status of a particular database in the configuration, you may connect your client to that database and get the current value of the StatusReport property for that database.
References:
http://psoug.org/oraerror/ORA-16625.htm
send
light_mode
delete
Question #12
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.
DGMGRL> start observer:
DGM-16954: Unable to open and lock the Observer configuration file Failed.
Identify two possible reasons for this error.
- AFast-Start Failover is not yet enabled for this Data Guard configuration.
- BThe observer configuration file is marked read-only.
- CThere is already an observer running for this Data Guard configuration.Most Voted
- DThere is another observer running for a Data Guard configuration which uses the same observer configuration file.Most Voted
- EThe broker configuration has not yet been created.
Correct Answer:
BD
Error code: DGM-16954 -
Description: Unable to open and lock the Observer configuration file
Cause: The Observer configuration file cannot be opened or cannot be locked for exclusive access.
Action: Make sure the Observer has the correct operating system privileges to write the file and there is no other Observer that is using the same file. Try the command again.
References:
https://www.oraexcel.com/oracle-12cR1-DGM-16954
BD
Error code: DGM-16954 -
Description: Unable to open and lock the Observer configuration file
Cause: The Observer configuration file cannot be opened or cannot be locked for exclusive access.
Action: Make sure the Observer has the correct operating system privileges to write the file and there is no other Observer that is using the same file. Try the command again.
References:
https://www.oraexcel.com/oracle-12cR1-DGM-16954
send
light_mode
delete
Question #13
Examine the Data Guard configuration:
DGMGRL> show configuration;
Configuration Animals -
Protection Mode: MaxAvailability
Databases:
dogs- Primary database
sheep- (*) Physical standby database
cats- Physical standby database
Fast-Start Failover: ENABLED -
Configuration Status:
SUCCESS -
What happens if you issue "switchover" to sheep;" at the DGMGRL prompt?
DGMGRL> show configuration;
Configuration Animals -
Protection Mode: MaxAvailability
Databases:
dogs- Primary database
sheep- (*) Physical standby database
cats- Physical standby database
Fast-Start Failover: ENABLED -
Configuration Status:
SUCCESS -
What happens if you issue "switchover" to sheep;" at the DGMGRL prompt?
- AThe switchover succeeds but Dogs need to be reinstated.
- BThe switchover succeeds but Fast-Start Failover is suspended.
- CThe switchover succeeds and Cats become the new failover target.
- DThe switchover succeeds and Dogs become the new failover target.
- EIt results in an error indicating that a switchover is not allowed.
Correct Answer:
D
Incorrect Answers:
E: NOT ALLOWED - Either this is a standby database and the primary database has not been switched first, or this is a primary database and there are no standby databases.
D
Incorrect Answers:
E: NOT ALLOWED - Either this is a standby database and the primary database has not been switched first, or this is a primary database and there are no standby databases.
send
light_mode
delete
Question #14
A data file on one of your physical standby databases has been accidentally deleted and you must restore and recover it.
All the archive logs required for recovery are still on disk in the directory pointed to by the log_archive_dest_1 parameter.
Which three steps must be performed to restore the missing file and recover the standby database while it is in the MOUNT state?
All the archive logs required for recovery are still on disk in the directory pointed to by the log_archive_dest_1 parameter.
Which three steps must be performed to restore the missing file and recover the standby database while it is in the MOUNT state?
- ARecover the datafile by using the RMAN RECOVER DATAFILE command
- BRestart the redo apply.Most Voted
- CRestore the datafile by using the RMAN RESTORE DATAFILE command.Most Voted
- DStop the redo apply.Most Voted
- ERecover the database by using the RMAN RECOVER DATABASE command.
Correct Answer:
CDE
Recovery from Loss of Datafiles on the Standby Database
1. Connect SQL*Plus to the standby database.
2. Stop Redo Apply using the SQL ALTER DATABASE ... statement.
3. In a separate terminal, start RMAN and connect to both the standby and recovery catalog databases (use the TARGET keyword to connect to the standby instance).
4. Issue the following RMAN commands to restore and recover datafiles on the standby database:
RESTORE DATAFILE <n,m,...>;
RECOVER DATABASE;
5. To restore a tablespace, use the RMAN 'RESTORE TABLESPACE tbs_name1, tbs_name2, ...' command.
6. At the SQL*Plus prompt, restart Redo Apply using the SQL ALTER DATABASE ... statement.
References:
https://docs.oracle.com/cd/E11882_01/server.112/e41134/rman.htm
CDE
Recovery from Loss of Datafiles on the Standby Database
1. Connect SQL*Plus to the standby database.
2. Stop Redo Apply using the SQL ALTER DATABASE ... statement.
3. In a separate terminal, start RMAN and connect to both the standby and recovery catalog databases (use the TARGET keyword to connect to the standby instance).
4. Issue the following RMAN commands to restore and recover datafiles on the standby database:
RESTORE DATAFILE <n,m,...>;
RECOVER DATABASE;
5. To restore a tablespace, use the RMAN 'RESTORE TABLESPACE tbs_name1, tbs_name2, ...' command.
6. At the SQL*Plus prompt, restart Redo Apply using the SQL ALTER DATABASE ... statement.
References:
https://docs.oracle.com/cd/E11882_01/server.112/e41134/rman.htm
send
light_mode
delete
Question #15
You administer a Data Guard environment consisting of a primary and three physical standby databases.
One physical standby database is used for disaster recovery, one is used for reporting, and one is used as a replica for testing.
The standby database used for testing is occasionally converted into a snapshot standby database and then converted back to a physical standby.
The physical standby database is the only standby that is a mandatory destination.
The broker configuration operates in MAXIMUM PERFORMANCE mode.
Which ARCHIVELOG DELETION POLICY should be set, so that archive logs generated on the primary database are not deleted before they are consumed appropriately on each of the standby databases, but which allows them to be deleted form the primary as soon as it is safe to do so?
One physical standby database is used for disaster recovery, one is used for reporting, and one is used as a replica for testing.
The standby database used for testing is occasionally converted into a snapshot standby database and then converted back to a physical standby.
The physical standby database is the only standby that is a mandatory destination.
The broker configuration operates in MAXIMUM PERFORMANCE mode.
Which ARCHIVELOG DELETION POLICY should be set, so that archive logs generated on the primary database are not deleted before they are consumed appropriately on each of the standby databases, but which allows them to be deleted form the primary as soon as it is safe to do so?
- ACONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
- BCONFIGURE ACHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
- CCONFIGURE ACHIVELOG DELETION POLICY TO SHIPPED TO ALL STANDBY;
- DCONFIGURE ACHIVELOG DELETION POLICY TO SHIPPED TO STANDBY;
- ECONFIGURE ACHIVELOG DELETION POLICY TO NONE;
Correct Answer:
B
You can change this default deletion policy using the following RMAN command:
CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
Use the APPLIED ON STANDBY clause so that archived redo log files that have been applied on all mandatory standby destinations will be deleted.
Incorrect Answers:
A: APPLIED ON ALL STANDBY is not valid.
C, D: SHIPPED TO is not valid.
E: Use the NONE clause so that archived redo logs in flash recovery area that were backed up or obsolete as per the RMAN retention policy are eligible for deletion. This is the default configuration. Archived redo log files that are backed up or obsolete are deleted to make space if the disk space in the flash recovery area becomes full.
References:
https://docs.oracle.com/cd/B19306_01/server.102/b14239/rman.htm#i1031870
B
You can change this default deletion policy using the following RMAN command:
CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
Use the APPLIED ON STANDBY clause so that archived redo log files that have been applied on all mandatory standby destinations will be deleted.
Incorrect Answers:
A: APPLIED ON ALL STANDBY is not valid.
C, D: SHIPPED TO is not valid.
E: Use the NONE clause so that archived redo logs in flash recovery area that were backed up or obsolete as per the RMAN retention policy are eligible for deletion. This is the default configuration. Archived redo log files that are backed up or obsolete are deleted to make space if the disk space in the flash recovery area becomes full.
References:
https://docs.oracle.com/cd/B19306_01/server.102/b14239/rman.htm#i1031870
send
light_mode
delete
All Pages