MSAMM
Back to course

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

Growing a tablespace

Lesson 126 of 184 · 2 min

Adding a datafile, autoextend, and THE CEILING THAT AUTOEXTEND DOES NOT REMOVE. A tablespace runs out of space when its datafiles are full, and there are two ways to give it more. ADDING A DATAFILE IS EXPLICIT AND IMMEDIATE. You decide the size and where it goes, which is the property that matters — you are choosing which file system absorbs the growth, rather than letting it land wherever the existing files are. AUTOEXTEND LETS A DATAFILE GROW ON DEMAND, AND IT IS GENUINELY USEFUL. It prevents the three-in-the-morning failure where a transaction fails because a file was one megabyte short. AND THE CEILING IT DOES NOT REMOVE IS THE FILE SYSTEM. A datafile can autoextend only while there is room underneath it. So an estate that considers space solved because autoextend is on has moved the failure rather than removed it — and moved it somewhere with a worse

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