MSAMM
Back to course

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

What breaks: four database-tier failures

Lesson 32 of 184 · 3 min

A full archive destination, a datafile that could not extend, a parameter change that stopped a restart, and a trace directory that filled a disk. THE FULL ARCHIVE DESTINATION STOPS THE DATABASE COMPLETELY, AND THAT IS CORRECT BEHAVIOUR. Archiving cannot write, so redo cannot be reused, so nothing can be written at all. The database hangs rather than crashing, which is the important detail: sessions freeze mid-transaction and users report the system as "slow" before anybody says it is down. The alert log names it in a line — and reaching for it fast is the difference between a ten-minute incident and an hour of guessing. Free space, or move archives; never delete them without knowing they are in a backup, or you have solved availability by destroying recoverability. THE DATAFILE THAT COULD NOT EXTEND FAILS A SINGLE TRANSACTION AND LEAVES THE SYSTEM RUNNING. One user gets an error, everyone…

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