Oracle Apps DBA: Keeping E-Business Suite Alive · Module 2 · The stack you are responsible for
What breaks: three architecture surprises
Lesson 21 of 184 · 2 min
A shared file system nobody documented, a second application tier nobody mentioned, and a database on a host WITH ANOTHER DATABASE ON IT. All three are the same failure: THE ESTATE IS NOT SHAPED THE WAY THE HANDOVER SAID, and each is discovered in the middle of doing something else. THE SHARED FILE SYSTEM IS DISCOVERED BY BREAKING TWO THINGS AT ONCE. Two instances mount the same storage — for a staging area, an interface directory, a patch repository — and it is documented nowhere. So a cleanup on test deletes files production was using, and the connection between the two events is invisible because the two instances are supposed to be independent. The tell is a file system whose size does not match what you can account for, and checking what is mounted is one command in Lesson 10's map. THE SECOND APPLICATION TIER IS DISCOVERED BY FIXING SOMETHING…
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 2 · The stack you are responsible for
- 1The two tiers, and why the split matters
- 2What is running right now
- 3The file system layout
- 4Environment files, and sourcing the right one
- 5The context file
- 6AutoConfig, and what it overwrites
- 7Ports, and the ones you will be asked about
- 8Logs: where they are and which one to open first
- 9What breaks: three architecture surprises
- 10Lab briefing · Map a running instance