Objective: Plan complete media recovery of a permanent application tablespace with RMAN.
A storage failure has damaged the datafiles of the permanent CUSTOMER tablespace in the House-O-Pets application PDB, PETSPDB. The CDB and PDB remain open. The current control file, SPFILE and online redo logs are intact. Your goal is to recover all committed changes.
Assume ARCHIVELOG mode, usable disk backups known to RMAN, and every required archived and online redo log. The original file locations are writable after storage repair. CUSTOMER is neither SYSTEM nor an active undo or temporary tablespace. Use a configured disk channel and an authorized administrative connection directly to PETSPDB. For encrypted files or backups, the required keystore or decryption credentials must also be available.
This is a written planning exercise; you do not need to damage files or execute recovery commands. Replace example service and account names only in an approved lab. Never submit passwords or invent successful recovery output.
Compare your response with the model solution. This exercise does not automatically grade free-text answers.
| Criterion | Points |
|---|---|
| Correct PDB, affected permanent tablespace, usable backups and required redo; storage and access checks | 2 |
| Take CUSTOMER offline before restoring its files | 1 |
| Restore CUSTOMER and then recover it, in that order | 2 |
| Inspect successful recovery before bringing CUSTOMER online; verify application access | 2 |
| Explain why complete media recovery does not undo a dropped table | 1 |
| Distinguish catalog metadata from backup pieces and explain the control-file alternative | 2 |
Review the tablespace recovery lesson before answering.