MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 5 · Backup and recovery

RMAN, from nothing

Lesson 48 of 184 · 2 min

The tool, the catalogue, and a first backup TAKEN AND VERIFIED. NO PRIOR EXPOSURE ASSUMED. RMAN is Oracle's backup tool, and the thing to understand before any syntax is what it knows that a file copy does not. It understands the database — which files exist, which blocks are in use, what has changed since the last backup — so it can back up an open database consistently, skip empty blocks, and detect corruption while it reads. THE CONTROL FILE IS ITS DEFAULT MEMORY, AND THAT IS THE FIRST THING TO GET RIGHT. RMAN records what it has backed up, and by default it records it in the control file of the database it is protecting. Which is fine until the day you lose that database, at which point your backup history is inside the thing you are trying to restore. A RECOVERY CATALOGUE IS A SEPARATE DATABASE HOLDING THAT…

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 5 · Backup and recovery

  1. 1What you are actually protecting against
  2. 2The restore you have never testedFree preview
  3. 3Recovery objectives, in plain terms
  4. 4Cold backups: when they are still right
  5. 5RMAN, from nothing
  6. 6Full, incremental and the strategy behind them
  7. 7Backing up the application tier
  8. 8Point-in-time recovery
  9. 9Restoring to a different host
  10. 10How long does a restore actually take
  11. 11Where the backups live
  12. 12What breaks: five backup failures
  13. 13Lab briefing · Lose the database and get it back