1Z0-067 · Question #140
Your database is running in archivelog mode. Examine the parameters for your database instance: LOG_ARCHIVE_DEST_l ='LOCATION=/disk1/arch MANDATORY' LOG_ARCHIVE_DEST_2 ='LOCATION=/disk2/arch'…
The correct answer is A. The database instance hangs and the redo log files are not overwritten. Made more logfile switch until all redos groups are full. first log switch succeds, second also succeds then next will hang database.
Question
Your database is running in archivelog mode. Examine the parameters for your database instance:
LOG_ARCHIVE_DEST_l ='LOCATION=/disk1/arch MANDATORY' LOG_ARCHIVE_DEST_2 ='LOCATION=/disk2/arch' LOG_ARCHIVE_DEST_3 ='LOCATIO=/disk3/arch' LOG_ARCHIVE_DEST _4 ='LOCATIONs/disk4/arch' LOG_ARCHIVE _MIN_SUCCEED_DEST = 2 While the database is open, you notice that the destination set by the log_archive_dest_1 parameter is not available. All redo log groups have been used. What happens at the next log switch?
Options
- AThe database instance hangs and the redo log files are not overwritten.
- BThe archived redo log files are written to the fast recovery area until the mandatory destination is
- CThe database instance is shutdown immediately.
- DThe destination set by the log_archive_dest parameter is ignored and the archived redo log files
How the community answered
(33 responses)- A82% (27)
- B9% (3)
- C3% (1)
- D6% (2)
Explanation
Made more logfile switch until all redos groups are full. first log switch succeds, second also succeds then next will hang database.
Topics
Community Discussion
No community discussion yet for this question.