READ Free Dumps For Oracle- 1z0-023
| Question ID 8783 | In the event of an Instance failure, which files store committed data, NOT written to the datafiles?
|
| Option A | Control files
|
| Option B | Online redo logs
|
| Option C | Network segment
|
| Option D | Archived redo logs
|
| Correct Answer | B |
Explanation Explanation/Reference: Explanation: Answer B is correct. Online redo logs are used to recover committed data, not written to the datafiles, after an instance failure. Incorrect Answers: A: Control files are used to store structure of database to mount and open database, they do not store committed data. C: There is no network segment object in Oracle. D: Archived redo logs stores ALL data, not only committed and, probably written to the datafiles. These files can be used for instance recovery, but this answer is not completely correct for the given question. Oracle 8, DBA Certification Exam Guide, Jason S. Couchman, p. 332-333 Chapter 7: Managing the Physical Database Structure
| Question ID 8784 | Which two statements about online redo log members in a group is true? (Choose two)
|
| Option A | All files in all groups are the same size.
|
| Option B | All members in a group are the same size.
|
| Option C | The members should be on different disk drives.
|
| Option D | The rollback segment size determines the member size.
|
| Option E | Differently sized of transactions requires that the DBA should have differently-sized members.
|
| Correct Answer | BC |
Explanation Explanation/Reference: Explanation: Answer B and C are correct. For more reliability the members should be placed on different disk drives. Also it is requirement that all members in a group were the same size. Incorrect Answers: A: Members in different groups may have different size, only members within one group need to be the same size. D: The rollback segment size does not determine the member size. E: Size of transaction has nothing to do with member's size of redo log group. Oracle 8, DBA Certification Exam Guide, Jason S. Couchman, p. 324-327 Chapter 7: Managing the Physical Database Structure