Oracle Apps DBA: Keeping E-Business Suite Alive · Module 3 · The database itself
Parameters, and the ones that matter here
Lesson 29 of 184 · 2 min
Where parameters live, WHICH EBS MANDATES, and the difference between a change that takes effect NOW and one that WAITS FOR A RESTART. Parameters configure the instance, and there are two things to know before changing one: where the change is written, and when it applies. THE SCOPE OF A CHANGE IS THE PART THAT CATCHES PEOPLE, AND IT HAS THREE ANSWERS. Memory only: it applies now and disappears at the next restart. Persistent only: it is recorded and applies at the next restart. Both: applies now and survives. Choosing wrongly gives you a fix that works today and reverts silently on the next bounce, or a fix that is recorded and does nothing while you are watching it not work. AND SOME PARAMETERS CANNOT BE CHANGED IN A RUNNING INSTANCE AT ALL. Anything that sizes a memory structure at startup, for instance. The instance will accept the persistent change…
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.
In this module: Module 3 · The database itself
- 1Instance and database: two different things
- 2Starting and stopping, properly
- 3Tablespaces and datafiles
- 4Redo: the reason recovery is possible
- 5Archive log mode, and the day it was off
- 6Undo, and read consistency
- 7Parameters, and the ones that matter here
- 8The data dictionary, as a diagnostic tool
- 9Reading an error you have never seenFree preview
- 10What breaks: four database-tier failures
- 11Lab briefing · Stop it, start it, break it