MSAMM
Back to course

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

What fills up, and in what order

Lesson 124 of 184 · 2 min

Archive destination, trace directories, concurrent output, interface tables and the audit trail. ROUGHLY IN THAT ORDER, IN MOST ESTATES. Space problems are predictable, which means they are preventable — and the order is worth knowing because it tells you where to look first and what to monitor. THE ARCHIVE DESTINATION IS FIRST AND IT IS THE WORST. It fills fastest because it grows with every change made to the database, and its failure is total: the database cannot write, so it hangs. Module 3 Lesson 10's first failure, and the only space problem that stops the entire business. TRACE DIRECTORIES ARE SECOND AND THEY ARE SELF-INFLICTED. Tracing switched on for a diagnosis and left on, or a repeating error writing a file per occurrence. They fill over days and their damage is collateral — whatever else shares that file system. CONCURRENT OUTPUT IS THIRD AND IT IS THE LARGEST BY

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