Oracle Apps DBA: Keeping E-Business Suite Alive · Module 5 · Backup and recovery
Lab briefing · Lose the database and get it back
Lesson 56 of 184 · 2 min
DESTROY an instance deliberately, restore it, and RECORD THE ELAPSED TIME AND EVERY STEP YOU HAD TO LOOK UP. "Every step you had to look up" is the deliverable, because that list is your runbook. Anything you had to search for at leisure is something you would be searching for at 3am with somebody waiting. DESTROY IT PROPERLY RATHER THAN GENTLY. Shut down and delete the datafiles — not rename them, delete them. A restore where the original files are quietly still present proves considerably less than it appears to, and the temptation to keep a copy is exactly the reflex this exercise is meant to remove. THEN RESTORE FROM THE BACKUP AND THE ARCHIVES ONLY, AND START THE CLOCK AT THE MOMENT OF DESTRUCTION. Include the parts people leave out of the estimate: finding the backup, reading the procedure, applying archives, opening, starting the application tier, and confirming the…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, with a certificate on completion and a fourteen-day refund window.
In this module: Module 5 · Backup and recovery
- 1What you are actually protecting against
- 2The restore you have never testedFree preview
- 3Recovery objectives, in plain terms
- 4Cold backups: when they are still right
- 5RMAN, from nothing
- 6Full, incremental and the strategy behind them
- 7Backing up the application tier
- 8Point-in-time recovery
- 9Restoring to a different host
- 10How long does a restore actually take
- 11Where the backups live
- 12What breaks: five backup failures
- 13Lab briefing · Lose the database and get it back