MSAMM
Back to course

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

The standard purge programs

Lesson 127 of 184 · 3 min

What EBS ships, what each removes, and THE PARAMETERS THAT DECIDE HOW MUCH HISTORY SURVIVES. EBS provides purge programs for the things that accumulate, and the first useful fact is that they exist — many estates write their own scripts for work that is already delivered and supported. THE MOST IMPORTANT ONE PURGES CONCURRENT REQUEST HISTORY, AND IT REMOVES BOTH THE ROWS AND THE FILES. That pairing matters: a home-made script deleting rows leaves the log and output files on disk forever, which is the larger half of the problem — Module 8 Lesson 10. OTHERS CLEAR PROCESSED INTERFACE DATA, WORKFLOW HISTORY AND SIMILAR ACCUMULATIONS. Which ones an estate needs depends on which modules it uses, and the useful exercise is to find out what is growing — Lesson 1 — and then find the supplied program for it rather than starting from the program list. THE PARAMETERS ARE WHERE

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