MSAMM
Back to course

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

Starting and stopping, properly

Lesson 24 of 184 · 3 min

The states a database passes through, what each allows, and WHY THE ORDER MATTERS when the application tier is involved. Startup is three steps rather than one, and each is a level of access rather than a formality. NOMOUNT builds the instance and touches no database file except the parameter file. Memory and processes exist; nothing is open. This is the state in which you create a control file or restore one, because the database it will describe does not need to be readable yet. MOUNT reads the control file, so the instance now knows what files the database has — and has not opened them. This is the recovery state: you restore datafiles and apply redo in MOUNT, because recovery must happen before anybody can be in the database. Understanding that is what makes Module 5 make sense rather than being a sequence of commands. OPEN makes the datafiles…

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