MSAMM
Back to course

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

Point-in-time recovery

Lesson 51 of 184 · 2 min

Recovering to THE MOMENT BEFORE THE MISTAKE. What it needs in place beforehand, which is DECIDED IN MODULE 3. This is the answer to Lesson 1's third failure — somebody deleted the wrong thing — and it is the recovery that a business actually asks for. THE MECHANISM IS THE ONE MODULE 3 DESCRIBED. Restore the datafiles from a backup taken before the mistake, then apply archived redo forward, stopping at the moment you choose. The database is then exactly as it was one second before 14:05. WHAT IT NEEDS IN PLACE BEFOREHAND IS ARCHIVE LOG MODE, AND THAT WAS DECIDED MONTHS AGO BY SOMEBODY WHO MAY NOT HAVE KNOWN THEY WERE DECIDING IT. Without archives there is nothing to roll forward with, so the only reachable state is the backup itself. No tool, no expertise and no amount of money changes that on the day — which is why…

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