Overview
Oracle Enterprise Manager (EM) provides web-based monitoring, backups, and performance dashboards. Database Express is built into Oracle Database; Cloud Control manages fleets.
Choose Express for single-instance labs; Cloud Control for data centers.
Implementation
Enable EM Express: EXEC DBMS_XDB_CONFIG.SETHTTPSPORT(5500); and ensure XML DB is enabled. Access https://host:5500/em. For Cloud Control, deploy the management agent and discover targets with proper credentials and firewall rules.
Use wallets and TLS certificates in production.
When implementing guidance from Oracle EM Configuration, start in a controlled environment that mirrors production versions of operating systems, runtimes, and network policies. Capture a baseline before changes: export configs, snapshot VMs, or tag releases in source control so rollback stays straightforward if behavior regresses.
Document prerequisites, expected outcomes, and verification steps in a short runbook. Automated checks—smoke tests, health endpoints, or query validations—catch regressions early when platforms receive patches. Security belongs in every workflow: apply least privilege, rotate secrets, and review audit logs after deployment.
If results differ across machines, compare environment variables, permission models, time zones, and regional settings. Intermittent issues often trace to caching layers, stale DNS, or duplicated services bound to the same port.
Example
SELECT DBMS_XDB_CONFIG.GETHTTPSPORT() FROM dual;
EXEC DBMS_XDB_CONFIG.SETHTTPSPORT(5500);Tips
- Change default ports in regulated environments.
- Patch EM components with the database stack.
- Least-privilege EM admin users.
- Monitor listener and EM logs together.
- Re-verify after reboots, certificate renewals, or failover exercises.
- Align monitoring and alerts with the failure modes described in this guide.
- Keep vendor documentation links handy for breaking changes between versions.
- Pair automation with a manual spot check during initial production rollout.