MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 12 · Space, growth and purging

What breaks: three space failures

Lesson 131 of 184 · 3 min

A full archive destination that FROZE THE DATABASE, a trace directory that FILLED A SHARED DISK, and a first purge that RAN FOR ELEVEN HOURS INTO A WORKING DAY. THE FULL ARCHIVE DESTINATION IS THE WORST SPACE FAILURE THERE IS AND IT IS THE MOST MISREAD. The database cannot write, so it hangs rather than crashing — sessions freeze mid-transaction and users report the system as SLOW. Nobody says "the database is down", because it is up and answering nothing, and the first ten minutes go to performance investigation. The alert log names it in one line, which is Module 2 Lesson 8's ordering rule earning its place. AND THE FIX HAS A TRAP IN IT. Clearing archives to get the system running is correct only for archives that are already backed up — deleting the others solves availability by destroying recoverability, and it creates the gap Module 5 Lesson

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.

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 12 · Space, growth and purging

  1. 1What fills up, and in what order
  2. 2Monitoring space before it matters
  3. 3Growing a tablespace
  4. 4The standard purge programs
  5. 5Deciding what history to keep
  6. 6Purging safely the first time
  7. 7Reclaiming space, and when you cannot
  8. 8What breaks: three space failures
  9. 9Lab briefing · Fill it up on purpose