English Русский Contacts Site map Add to favorites
Registration
Login
Master braindump list
New braindumps
Submit a dump
Get latest dump
braindumps.com.ua
flame
3COM (7)
Adobe (1)
BEA (1)
Checkpoint (22)
Cisco (20)
Citrix (21)
CIW (15)
Compaq (0)
CompTIA (51)
CWNA (2)
EMC (2)
Exin (4)
GEJOS (4)
HDI (1)
HP (4)
IBM (13)
Juniper (5)
Linux Prof Institute (LPI) (2)
Lotus (11)
Microsoft (2462)
Network Appliance (2)
Novell (16)
Oracle (423)
PLSQL (1)
PMI (5)
SAS (1)
Sun (87)
Teradata (4)
Login:
Password:
RSS feed

Contacts
Certification links
Links
Authorized users can post comments.
Please log in or sign up.

back to list
Back to main forum
Backup and Recovery 

АвторSubject: Q75
written 19 January 2008 10:10   View profile Jonnik  Edit/Delete  Answer  Answer with quotation
Explanation:
There is only one complex recovery situation for read-only table spaces. This is when your readonly table space experiences media failure, and the backup you have was taken when the table space was in read-write state. In order to manage this recovery, you must first recover the table space from backups taken when it was a writable table space and apply redo logs to update the objects in that table space up to point when the table space was made read-only. Then, you can change the table space state to read-only. A DBA needs to do complete media recovery if restores a read-only table space from a backup taken BEFORE the table space was made read-only.
Incorrect Answers:
1: A DBA does not need to recreate the control file in this case.
3: A DBA does not need to make the table space locally managed in this case.
4: A DBA can use the table space BEFORE it became read-only.
Oracle 8, DBA Certification Exam Guide, Jason S. Couchman, p. 721
Chapter 15: Advanced Topics in Data Recovery

Current tread:
back to list

Q75 - Go to question 10:10 19.01.08

back to list
Up ^ gen. 0.081 Server date 02:55 10-01-2009 Developed by Zip © 2006 Up ^
Forum
Start online exam simulation
Master braindump
User braindumps
Main forum
Question comments