1Z0-043 · Question #179
You lost the PRODSTD tablespace, which was read-only. The tablespace was read-only when the last backup was taken. How would you recover the tablespace?
The correct answer is D. restore the tablespace from the backup. See the full explanation below for the reasoning.
Question
You lost the PRODSTD tablespace, which was read-only. The tablespace was read-only when the last backup was taken. How would you recover the tablespace?
Options
- Arestore the tablespace from the backup, and then perform an incomplete recovery
- Brestore the tablespace from the backup, and then apply all the redo information
- Crestore all the data files in the database, and then perform an incomplete recovery
- Drestore the tablespace from the backup
How the community answered
(32 responses)- A13% (4)
- B3% (1)
- C3% (1)
- D81% (26)
Community Discussion
6D is the right call here, and the reasoning clicks once you understand what read-only means at the storage level. A read-only tablespace accepts no writes after it is placed in that mode, which means no redo is generated for it and no redo needs to be applied. The backup you took while it was already read-only is a perfect, self-consistent snapshot of every block in that tablespace, so restoring it puts you right back to the current state with zero divergence. Redo application, incomplete recovery, and full-database restores are all unnecessary overhead that this scenario simply does not require.
D is the only move, and I knew it the second I saw "read-only." Mine had the same wording almost word for word, and I flagged it, came back, still picked D because a read-only tablespace has no redo to apply, the backup is already current.
Read-only tablespace reasoning is solid, but rehearse saying it in your own words under pressure, because if the stem adds a wrinkle like a point-in-time recovery or a different backup type, that shortcut can misfire fast.
Totally D, restore only since read-only means zero redo needed.
The good news is Bao is actually right, D is the answer. Read-only tablespaces do skip redo application during recovery, so restore only is exactly what is needed.
This one trips people up because the instinct is to always apply redo after a restore, but a read-only tablespace generates no redo after it goes read-only, so the backup you have is already the complete picture. Did you know ahead of time that it was read-only at backup time, or were you working through the options by elimination?