MSAMM
Back to course

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

Tablespaces and datafiles

Lesson 25 of 184 · 3 min

How space is organised, what an EBS instance actually uses, and THE TABLESPACE THAT FILLS FIRST IN EVERY ESTATE. A tablespace is a logical container and a datafile is the physical file behind it. Objects live in tablespaces; tablespaces are made of one or more datafiles; datafiles sit on a file system that itself has a size. Three layers, and running out of space at any of them produces a different error with a different fix. AN EBS DATABASE HAS FAR MORE TABLESPACES THAN A BESPOKE ONE, AND MOST OF THEM ARE NOT YOUR CONCERN DAY TO DAY. Product data, indexes, the system tablespaces, undo, temporary. The ones you will actually watch are few, and knowing which is the difference between monitoring everything badly and monitoring the right three well. THE ONE THAT FILLS FIRST IN EVERY ESTATE IS TEMPORARY, AND THE REASON IS STRUCTURAL RATHER THAN ACCIDENTAL. Sorting, hashing…

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