MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 3 · The database itself

Archive log mode, and the day it was off

Lesson 27 of 184 · 3 min

The SINGLE configuration decision that determines whether point-in-time recovery EXISTS AT ALL. How to check, and what to do about the answer. Archive log mode is on or off, and everything about your recovery capability follows from which. WITH IT ON, redo logs are copied before reuse and you can recover to any point in time. A backup plus the archives since it gets you to one second before the problem. WITH IT OFF, THE ONLY THING YOU CAN RECOVER TO IS THE MOMENT A BACKUP WAS TAKEN — and only a backup taken with the database shut down, because an online backup of a database in this mode is not recoverable at all. Everything since is unrecoverable, in principle, by anybody. SO THE DAY IT WAS OFF IS A REAL AND COMMON SITUATION AND IT IS ALWAYS THE SAME STORY. The instance was created for testing, or cloned from…

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 3 · The database itself

  1. 1Instance and database: two different things
  2. 2Starting and stopping, properly
  3. 3Tablespaces and datafiles
  4. 4Redo: the reason recovery is possible
  5. 5Archive log mode, and the day it was off
  6. 6Undo, and read consistency
  7. 7Parameters, and the ones that matter here
  8. 8The data dictionary, as a diagnostic tool
  9. 9Reading an error you have never seenFree preview
  10. 10What breaks: four database-tier failures
  11. 11Lab briefing · Stop it, start it, break it