Enterprise Manager 24ai
DB Realm Inc. (Internal)
Challenge
An Oracle estate needs one place to see database health, patch levels and compliance, and Enterprise Manager is that place. It is also usually installed once, by hand, by someone who then leaves, and the first patch cycle exposes everything that was never written down. The goal was a reproducible build of Oracle Enterprise Manager 24ai, driven by scripts rather than clicks, and documented well enough that a stranger could repeat it.
Solution
Built a self-contained Oracle Enterprise Manager 24ai deployment: repository database and management server on one Oracle Linux 9 host, patched to the current release update, and configured emcli-first so the whole build is scriptable. Enterprise Manager provides the monitoring, patch and compliance views, and its AI assistant is connected to a self-hosted LLM so database telemetry stays on the network. Every credential is generated at run time and retrieved from a password manager, never stored in git.
Results
- ✓ OEM 24ai RU11 on a 26ai repository, built reproducibly
- ✓ Management server and agent patched to RU11, the agent through a scripted emcli patch plan
- ✓ Scriptable end to end: silent installs, Ansible and emcli
- ✓ Connected to a self-hosted LLM instead of cloud AI
Enterprise Manager is usually installed once, by hand, by someone who then leaves. This build treats it as infrastructure code: silent installs, Ansible for OS preparation, emcli for configuration, and a written record of every step taken from real command output rather than reconstructed afterwards.
The certification work came first and settled two constraints before anything was installed. Oracle Linux 10 is not certified for the management server, so the OMS runs OL9. And because the repository is itself a current Oracle AI Database, capabilities that normally need a separate target database can run inside the repository itself.
What Enterprise Manager is for
Enterprise Manager 24ai is the console for monitoring, patch and compliance visibility across Oracle database targets. Having that view in one place is what makes an estate manageable: instead of logging in to each server to find out what is running and what is out of date, the answer is already on one screen.
Patching Enterprise Manager itself
A fresh 24ai install cannot patch itself to Release Update 11 as shipped: the three patching tools it comes with are older than the minimums that release update asks for. The order that worked was to update the tools first, apply the management server release update with OMSPatcher, and then apply the agent release update through a patch plan driven from emcli. Every step is scripted, so the next patch cycle is a repeat of a known procedure instead of a rediscovery.
Local AI instead of cloud
The build connects Enterprise Manager’s AI assistant to a self-hosted, OpenAI-compatible LLM gateway rather than a cloud generative-AI service. The release update ships a generic LLM provider mechanism (a credential type with a free-text provider URL and a management-server-level allow-list) that Oracle has not publicly documented. It had to be proven on the box before it was used. With it, database telemetry and DBA questions never leave the network.
Written down
Credentials are generated at run time and held in a password manager, and the build is documented from the real command output, so the deployment can be rebuilt from scratch by someone who was not there the first time.