MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 2 · The stack you are responsible for

Environment files, and sourcing the right one

Lesson 16 of 184 · 2 min

Half the "command not found" problems in this course are A SHELL THAT SOURCED THE WRONG ENVIRONMENT, OR NONE. Nothing in EBS works from a bare shell. The utilities are not on the default path, the database connection details are not set, and the tools cannot find the instance they belong to. An environment file sets all of that, and sourcing the right one is the first thing you do in any session. THERE IS ONE PER TIER AND THEY ARE NOT INTERCHANGEABLE. The database tier has its own; the application tier has its own. Sourcing the database environment and then running an application utility produces exactly the "command not found" in the title, and the error is about the path rather than about the tool being missing — which is why people go looking for an installation problem that does not exist. THE WORSE VERSION IS SOURCING THE WRONG…

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 2 · The stack you are responsible for

  1. 1The two tiers, and why the split matters
  2. 2What is running right now
  3. 3The file system layout
  4. 4Environment files, and sourcing the right one
  5. 5The context file
  6. 6AutoConfig, and what it overwrites
  7. 7Ports, and the ones you will be asked about
  8. 8Logs: where they are and which one to open first
  9. 9What breaks: three architecture surprises
  10. 10Lab briefing · Map a running instance