Oracle Enterprise Manager (OEM) is the centralised database and infrastructure management platform used by Oracle Database administrators at thousands of large enterprises to manage database lifecycle, performance monitoring, patch orchestration, backup and recovery scheduling, and compliance reporting across Oracle Database, Oracle Fusion Middleware, and Oracle Engineered Systems estates. An OEM 12c or 13c environment with years of customised monitoring templates, EM CLI automation scripts, custom compliance frameworks, and notification rules represents a mature database operations toolset that the DBA team depends on daily. It is not a peripheral monitoring tool — it is the operational control plane for Oracle's most critical workloads.
Oracle's positioning is to move OEM customers toward Oracle Management Cloud (OMC) — now Oracle Cloud Observability and Management (O&M) — Oracle's SaaS-based cloud monitoring and management platform. Oracle applies the same migration pressure playbook used across its on-premise portfolio: lifecycle pressure, feature investment claims, and renewal pricing designed to make staying on OEM feel commercially risky. Third-party support on Oracle Enterprise Manager 12c or 13c cuts annual support costs by 50–65% and allows your DBA team to continue operating the monitoring and management platform they know, without an OCI subscription requirement layered on top of your Oracle Database TPS contract.
Running Oracle? Find out exactly what you're overpaying. Free cost analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
Oracle Enterprise Manager 12c (12.1.0.x) Premier Support ended December 2018. OEM 12c is in Sustaining Support — no new patches or security fixes. Oracle Enterprise Manager 13c Release 3 (13.3.x) reached Premier Support end in July 2021. OEM 13c Release 4 (13.4.x) and Release 5 (13.5.x) remain in active Premier Support. For any organisation on OEM 12c or 13c Release 3, TPS is immediately relevant. See our Oracle TPS complete guide for the full Oracle support lifecycle framework and how it applies to OEM.
Oracle Management Cloud Migration — The Customisation Loss Problem
Oracle Cloud Observability and Management (O&M) is architecturally different from Oracle Enterprise Manager. OEM is a Java EE application deployed on Oracle WebLogic with Oracle Database as the management repository — a deeply customisable, extensible platform where DBA teams build custom monitoring metrics, automated job frameworks, compliance rules, and EMCLI scripts that handle day-to-day Oracle Database operational tasks. O&M is a cloud-native SaaS product with pre-configured monitoring rules, API-driven alert management, and a fundamentally different extensibility model.
The migration problem is not just the cost of an O&M subscription (which adds £80K–£500K/year depending on the size of the monitored estate) — it is the loss of institutional DBA tooling. Custom OEM monitoring templates built for specific database performance characteristics, EM CLI automation scripts that handle backup verification and daily health checks, custom compliance frameworks built to internal IT audit requirements, and alerting rule hierarchies tuned over years of operational experience do not migrate to O&M. They must be rebuilt from scratch in a different tooling model. For large Oracle Database estates managed by experienced DBA teams, this represents 6–18 months of re-tooling effort at significant cost. GoVendorFree TPS on the existing OEM environment avoids that tooling loss entirely while delivering immediate cost reduction.
Oracle Enterprise Manager Version Matrix — TPS Eligibility
| Version | Key Capabilities | Oracle Support Status | TPS Available |
|---|---|---|---|
| OEM 11g (11.1.0.x) | Grid Control — classic DBA monitoring and job framework | Sustaining Support only | ✓ Yes — legacy TPS candidate |
| OEM 12c (12.1.0.x) | Cloud Control — real-time performance monitoring, capacity planning | Sustaining Support only | ✓ Yes — significant TPS cohort |
| OEM 13c Release 2 (13.2.x) | Enhanced Exadata monitoring, Ops Centre integration | Sustaining Support only | ✓ Yes |
| OEM 13c Release 3 (13.3.x) | ADB monitoring, Helidon framework, enhanced DBaaS | Sustaining Support only | ✓ Yes — primary TPS candidate |
| OEM 13c Release 4 (13.4.x) | OCI integration, hybrid monitoring, EMCLI enhancements | Extended Support (surcharges) | ✓ Yes |
| OEM 13c Release 5 (13.5.x) | Latest release — enhanced ADB and Exadata Cloud at Customer support | Active Premier Support | ✓ Yes |
GoVendorFree TPS Coverage for Oracle Enterprise Manager
GoVendorFree's Oracle TPS covers Oracle Enterprise Manager as part of a comprehensive Oracle Database estate support contract. Coverage includes:
- OEM Management Server (OMS): OMS application server stability (WebLogic 12c embedded); OMS high availability (active/passive OMS topology) advisory; OMS repository database (Oracle Database 12c–19c) performance and stability; OEM SSL/TLS certificate management; OMS upgrade advisory within supported version boundaries; EMCLI (EM Command Line Interface) stability for automation scripts
- Database Monitoring and Performance: Oracle Database 11g–23ai performance monitoring stability; ASH (Active Session History) and AWR (Automatic Workload Repository) data collection; Top Activity and SQL Monitoring advisory; Custom metric collection stability; Performance Hub and ADDM (Automatic Database Diagnostic Monitor) advisory; Exadata Smart Scan and cell offload monitoring
- Job and Automation Framework: EM Job Library stability for scheduled backup, patch pre-check, and maintenance jobs; Deployment Procedure framework (patching, provisioning workflows) advisory; Database Configuration Management compliance check stability; RMAN backup and recovery job scheduling advisory; Data Masking and Subsetting job stability
- Compliance and Security Frameworks: Custom compliance framework rule stability; Security Configuration assessments (Oracle DB CIS benchmark advisory); Audit Vault integration advisory; Identity Management (LDAP/Active Directory) integration for OEM administrator authentication; Named credential management and rotation advisory
- Agent and Target Management: Oracle Management Agent deployment and connectivity stability; Target discovery and monitoring configuration; Metric collection error troubleshooting; Agent bundle patch advisory; Blackout and maintenance window management; Plug-in lifecycle management advisory
- Engineered Systems: Exadata Database Machine OEM management stability (Exadata storage cell metrics, InfiniBand monitoring, Flash Cache); Oracle Database Appliance (ODA) OEM agent configuration advisory; ZDLRA (Zero Data Loss Recovery Appliance) monitoring integration advisory
OEM TPS as Part of Oracle Database TPS — The Unified Support Model
The most commercially efficient TPS approach for Oracle Enterprise Manager customers is a unified Oracle TPS contract that covers both the managed Oracle Database estate and OEM itself. When you move your Oracle Database environment to TPS, continuing to pay Oracle full annual support rates for Oracle Enterprise Manager — the tool your DBA team uses to manage the TPS-covered databases — creates a structural anomaly: Oracle is still charging 22% NLV for OEM while you have stopped paying Oracle for the underlying database support. GoVendorFree's Oracle TPS framework covers both layers under a single contract, with a single P1 response SLA and a single contract management overhead. See our Oracle Database TPS guide for the full database estate coverage model, and our Oracle TPS service overview for the unified contract framework.
The OEM TPS approach also integrates with Oracle Exadata TPS for organisations managing engineered systems through OEM. Exadata monitoring via OEM — storage cell metrics, InfiniBand fabric health, Smart Flash Cache utilisation, and off-loading statistics — remains fully supported under TPS, maintaining the operational monitoring that Exadata-scale database environments depend on.