Oracle E-Business Suite 12.2 Deployment
DB Realm Inc. (Internal)
Challenge
Oracle E-Business Suite is one of the few enterprise platforms where reading the documentation is genuinely insufficient preparation. The online patching cycle, the dual filesystem model, and the technology stack prerequisites all behave in ways that only become clear when a patch fails at 2 a.m. Practising that safely requires a real environment — but a production-shaped EBS deployment is expensive enough that most people never get one.
Solution
Built a deliberately minimal single-node EBS 12.2.15 environment on Oracle Linux 8 — database tier and application tier on one host, sized to the smallest configuration that still starts every service and survives a full adop patching cycle. Provisioned with Terraform against XCP-ng, prepared with Ansible, and documented phase by phase as it was built rather than reconstructed afterwards.
Results
- ✓ EBS 12.2.15 single-node environment, fully scripted
- ✓ Survives a complete adop online patching cycle
- ✓ Infrastructure as code from bare VM to running services
- ✓ Every credential retrieved at run time, none stored
This environment exists to be broken. Its purpose is practice — installing, patching, cloning, breaking and recovering E-Business Suite for real, so that the procedure is known rather than read about.
Deliberate omissions
There is no high availability here, no business data, and no uptime obligation. Those are stated up front in the repository, because they are what make the environment affordable to run continuously. A lab that pretends to be production is worse than one that is honest about what it is — it teaches the wrong lessons about capacity and gives false confidence about failover.
The sizing work was its own exercise: finding the smallest configuration where every service still starts and a full adop cycle still completes. Undersize it and the failures are artifacts of the lab rather than lessons about EBS.
Infrastructure as code
| Layer | Tool |
|---|---|
| Virtual machine | Terraform against XCP-ng / Xen Orchestra |
| Operating system prep | Ansible playbooks |
| EBS install and patching | Silent installs, adop online patching, ETCC |
One constraint shaped the Terraform: it can clone a template but cannot install an operating system, so the Oracle Linux 8 template build is a documented one-time prerequisite rather than something the automation pretends to handle. Automation that silently depends on a manual step nobody wrote down is how environments become unreproducible.
Credentials
Every password — database, application, hypervisor API token — is retrieved from a password manager at run time and piped directly into the consuming process. Nothing is stored in the repository, and the repository holds only item identifiers, never values.
This is not theatre. EBS installs involve response files and silent invocations that will happily accept a password on a command line and log it somewhere unhelpful.
Published as it was built
The documentation discipline matters more than the environment. Content comes only from commands actually run, with their real output — no reconstructed transcripts, no steps that “should” work. An install guide written from memory after the fact is where the subtle prerequisites go missing, and they are exactly the ones that cost a stranger a weekend.