Oracle Apps DBA: Keeping E-Business Suite Alive · Module 2 · The stack you are responsible for
The file system layout
Lesson 15 of 184 · 2 min
Where the code, the configuration, the logs and the data actually sit, and THE DIRECTORIES THAT LOOK LIKE DUPLICATES AND ARE NOT. EBS has a large and highly conventional file system, and the convention is the useful part: once you know the shape, an unfamiliar instance is navigable in minutes. THE BROAD DIVISION IS BETWEEN WHAT ORACLE SHIPS AND WHAT THIS INSTANCE HAS. The application code — forms, reports, programs, libraries — is delivered by Oracle and changed only by patching. The instance-specific material — configuration, logs, output, temporary files — is generated and changes constantly. Knowing which side of that line a directory is on tells you whether editing something there is normal or is a mistake that will be overwritten. AND THE DIRECTORIES THAT LOOK LIKE DUPLICATES ARE THE PART TO GET RIGHT BEFORE YOU EDIT ANYTHING. An EBS file system holds several trees that look interchangeable to…
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