The Oracle Cloud Management Pack for Oracle Database extends Enterprise Manager to enable private cloud database provisioning and automated lifecycle management. At $7,500 per processor list price, plus the mandatory prerequisite Database Lifecycle Management Pack at $12,000 per processor, the combined cost for self-service infrastructure can reach $19,500 per processor before annual support. This guide covers everything ITAM professionals need: licensing model, pricing, prerequisite requirements, common compliance pitfalls, and strategies for optimising costs while maintaining audit readiness.
This guide is part of our Oracle management pack licensing coverage. See also: Oracle Enterprise Manager Licensing | Diagnostics Pack | Tuning Pack | Data Masking Pack | Oracle Database Licensing Guide
The Oracle Cloud Management Pack for Oracle Database extends Oracle Enterprise Manager (OEM) to facilitate a private cloud for databases. It enables organisations to offer self-service database provisioning and automated database lifecycle management to internal users. It transforms your Oracle Database platform into a private DBaaS (Database-as-a-Service).
| Capability | What It Does | Business Value |
|---|---|---|
| Self-service database portal | Developers and testers request database instances on demand through a web portal. Reduces wait times for environment setup. | Cloud-like agility without leaving Oracle's ecosystem. Eliminates DBA bottleneck for environment requests. |
| Resource pooling and automation | Databases run on pooled server resources ("database zones") with automated provisioning and de-provisioning. | Optimises infrastructure utilisation. Reduces manual DBA effort for routine environment management. |
| Chargeback / showback reporting | Tracks resource consumption (CPU, storage, memory per database) and generates reports for internal chargeback or cost transparency. | Essential for shared-services IT models. Enables department-level cost allocation. |
| Schema-as-a-Service | Allows provisioning just a schema (instead of a whole database instance) for lightweight use cases. | Increases density and efficiency on existing infrastructure. Lower overhead per user. |
The Cloud Management Pack is a separately licensed add-on. It is not included with Oracle Database Enterprise Edition, nor is it part of the base Oracle Enterprise Manager functionality. The features it provides (self-service provisioning, automated lifecycle management, chargeback reporting) all require a specific licence. Simply installing or enabling these features triggers the licence requirement.
Oracle Cloud Management Pack licensing is not included with the standard Oracle Database licence. It must be purchased as a separate management pack for Oracle Database Enterprise Edition environments.
| Requirement | Detail |
|---|---|
| Enterprise Edition only | The pack is only available for Oracle Database Enterprise Edition (including EE on Exadata). It cannot be used with Standard Edition databases. |
| Match database licence metric | You must licence the Cloud Management Pack using the same metric as your database. If your databases are licensed per Processor, the pack must be licensed per Processor on those same servers. |
| Full server coverage | A Cloud Management Pack licence is required for every database server where Cloud Pack features are deployed. All servers in the private cloud pool using self-service provisioning must be fully licensed. |
| Mandatory prerequisite | Oracle requires the Database Lifecycle Management Pack to be licensed before you can use the Cloud Management Pack. The Cloud Pack builds on the Lifecycle Pack's functionality (provisioning, cloning, patching automation). |
| No free use in base OEM | Unlike basic OEM functionality (which is free with a database licence), using Cloud Management Pack features requires a licence. There is no trial usage allowed outside of Oracle's official evaluation agreements. |
If you run a private Oracle DBaaS environment on a cluster with 8 processor licences of Oracle DB Enterprise Edition and enable self-service provisioning via OEM, you need to licence 8 processors of Cloud Management Pack plus 8 processors of the Database Lifecycle Management Pack. Failure to do so would result in non-compliance during an Oracle audit.
| Licensing Metric | Licence List Price (per unit) | Annual Support (22%) |
|---|---|---|
| Processor (per core, following Oracle's core factor) | $7,500 per processor licence | $1,650 per processor per year |
| Named User Plus (NUP) | $150 per named user | $33 per named user per year |
Oracle requires a minimum of 25 Named User Plus licences per processor when using the NUP model. One processor therefore corresponds to at least $3,750 in Cloud Pack NUP licences (25 x $150).
Scope of deployment. The number of processors (cores) enabled for Cloud Pack features is the primary cost driver. Every additional database server or cluster node in the "database cloud" adds $7,500 (list) per core. A server with 4 Oracle-licensed processors costs $30,000 in Cloud Pack licences plus $6,600/year in support.
Prerequisite pack cost. The Database Lifecycle Management Pack has its own cost at approximately $12,000 per processor (list). Implementing Cloud Management Pack from scratch requires budgeting for both packs. This stack (Lifecycle Pack + Cloud Pack) can effectively reach $19,500 per processor for self-service infrastructure.
Oracle Cloud vs on-premises. Oracle Database Cloud Service Enterprise Edition at High Performance and Extreme Performance tiers, and Exadata Cloud Service, include Cloud Management Pack functionality at no additional licensing cost. This can make Oracle's cloud offerings financially attractive compared to licensing the pack on-premises.
NUP vs Processor economics. For a small, known user base (30 developers), NUP licensing can cut costs substantially. 40 NUP licences cost approximately $6,000 for Cloud Pack vs $7,500+ per processor. However, as user counts grow beyond ~50 per processor, NUP licensing becomes impractical. For metric selection guidance, see our NUP vs Processor guide.
Oracle's management packs present some of the most common compliance challenges in Oracle licensing. Being aware of these pitfalls can save your enterprise from costly audit findings.
| Pitfall | How It Happens | Compliance Impact | Mitigation |
|---|---|---|---|
| Accidental usage: packs enabled by default | Oracle Enterprise Manager often has management packs enabled by default. Cloud Pack features may be active without explicit activation. | Oracle's audit scripts detect pack-specific feature usage. Creates compliance violation even without intent. | Always disable unlicensed packs in OEM before deployment. Run internal checks quarterly. |
| Missing prerequisite (DBLM Pack) | Budget for Cloud Pack without first licensing the Database Lifecycle Management Pack. Cloud Pack builds on DBLM. | Using Cloud Pack features without the Lifecycle Pack licence = non-compliant even if you own Cloud Pack itself. | Budget and licence both packs together. Verify both entitlements before enabling features. |
| Metric mismatch or shortfall | Scaling from 2 processors to 4 without adding licences. Or purchasing NUP but having more users than covered. | Any shortfall is a licence violation. Oracle counts every processor and every user. | Track hardware changes and user counts continuously. Require ITAM sign-off before infrastructure changes. |
| Assuming dev/test is free | Oracle requires the same licensing for non-production use if the feature is enabled. No free pass for dev/test. | An internal private "dev/test cloud" using this pack is still subject to full licence requirements. | Licence all environments or disable Cloud Pack features in non-production. |
| Paying double: ignoring cloud entitlements | Databases migrated to Oracle Cloud at a service level that includes Cloud Pack, but on-premises licences continue to renew. | Duplicate costs: on-prem support fees + cloud subscription for the same capability. | Align licensing to current architecture. Decommission on-prem licences for migrated workloads. |
| Audit exposure | Oracle LMS auditors check OEM repository tables, views, and activity logs for Cloud Pack usage. | Not having evidence of controlled usage is itself a risk. Oracle will assume usage = obligation. | Demonstrate disabled unlicensed packs. Document which features are in use. See our Oracle audit guide. |
1. Right-size your licensing model. Choose between Processor and NUP based on your actual environment. For large developer populations or unknown user counts, Processor licensing is safer and simpler. For a limited, known user base (20 to 30 developers), NUP can cut costs substantially. Always enforce Oracle's minimum of 25 NUP per processor in your calculations. See our NUP minimum requirements guide.
2. Leverage Oracle Cloud inclusions. Evaluate whether hosting databases on Oracle Cloud Infrastructure (OCI) is more cost-effective. Oracle's DB Cloud Service at High Performance or Extreme Performance tiers includes management packs at no additional cost. Particularly attractive for short-term projects where buying perpetual licences would be overkill.
3. Consider DBaaS alternatives. If Cloud Pack's cost is prohibitive, consider achieving similar goals via alternative methods: scripting provisioning with Ansible/Terraform (no additional Oracle licensing), using third-party orchestration tools (verify they do not invoke licensable Oracle APIs), or limiting Cloud Pack to specific high-value environments rather than enterprise-wide deployment.
4. Enterprise licence agreements. For broad deployments, negotiate with Oracle to include Cloud Management Pack in a broader ULA or enterprise agreement. This can result in flat-fee unlimited use or bulk discounts that reduce per-processor cost. For negotiation strategies, see our Oracle contract negotiation service.
5. Consolidate and right-size hardware. Since Cloud Pack is licensed per processor, fewer processors = lower cost. Deploy self-service provisioning on the smallest infrastructure that meets performance requirements. Consider consolidating database cloud zones onto fewer, well-utilised servers rather than spreading across a large cluster. For core factor calculations, see our Oracle Core Factor Table calculator.
Step 1: Assess current usage. Inventory your Oracle environments to determine whether Cloud Management Pack features are in use or planned. Check OEM settings. Confirm with your DBA team whether any self-service portals or automated provisioning processes are active.
Step 2: Verify prerequisites and entitlements. Confirm that you have Database Lifecycle Management Pack licences for any environment where Cloud Pack will be used. Review your Oracle contracts to check if any packs are already covered (ULA or Oracle Cloud subscription).
Step 3: Choose a licensing model. Based on scope (number of database servers and users), decide on Processor vs NUP. Use Oracle's core factor table and your hardware information to calculate required processors. Count named users who will access the self-service environment.
Step 4: Calculate costs and obtain approvals. Determine total licensing cost for Cloud Management Pack and Lifecycle Pack (if needed), including first-year support. For example: X processors x $7,500 + 22% support. Prepare budget and negotiate discounts.
Step 5: Implement and control. Enable Cloud Pack features in a controlled manner. Update OEM configuration: enable the pack on licensed targets and disable it on all other targets. Implement governance measures, monitor usage quarterly, and set recurring reviews.
Cloud Management Pack licensing follows the same virtualisation rules as Oracle Database itself. This means Oracle's soft partitioning policy applies when the pack is deployed in virtualised environments.
| Environment | Licensing Rule | Cost Impact |
|---|---|---|
| VMware / Hyper-V / KVM | All physical cores across all hosts in the cluster must be licensed for Cloud Pack (same as database). Soft partitioning not recognised. | A 4-host VMware cluster with 128 total cores requires 64 Cloud Pack processor licences ($480,000 at list) even if OEM runs on a single VM. |
| Oracle VM (hard partitioning) | Only the cores assigned to the OEM/database VM need to be licensed. Oracle recognises OVM as hard partitioning. | 8 assigned vCPUs = 4 processor licences ($30,000 at list). Significant savings vs VMware. |
| Oracle Cloud Infrastructure (OCI) | BYOL: 2 vCPUs = 1 processor licence. Or use cloud service tiers that include management packs at no extra cost. | High Performance and Extreme Performance tiers include Cloud Pack. Evaluate cloud inclusion vs BYOL economics. |
| Bare metal / dedicated physical | Standard core factor calculation. Licence only the cores on the physical server. | No virtualisation multiplier. Most predictable licensing outcome. |
For comprehensive virtualisation guidance, see our Oracle Licensing in Virtualised Environments guide.
Oracle's management pack ecosystem includes multiple separately licensed add-ons. Understanding how Cloud Management Pack relates to the other packs is essential for compliance and cost planning.
| Management Pack | List Price (Processor) | Relationship to Cloud Pack | Common Compliance Issue |
|---|---|---|---|
| Database Lifecycle Management Pack | ~$12,000/processor | Mandatory prerequisite. Must be licensed before Cloud Pack can be used. | Licensing Cloud Pack without DBLM = non-compliant even if Cloud Pack is owned. |
| Diagnostics Pack | $7,500/processor | Separate pack. Not a prerequisite for Cloud Pack. Provides AWR, ADDM, performance monitoring. | Enabled by default in OEM. Most common accidental compliance violation across all Oracle packs. |
| Tuning Pack | $5,000/processor | Separate pack. Requires Diagnostics Pack as prerequisite. Provides SQL Tuning Advisor, SQL Access Advisor. | Using Tuning Pack features without both Tuning and Diagnostics Pack licences. |
| Data Masking and Subsetting Pack | $11,500/processor | Separate pack. Often used alongside Cloud Pack for secure provisioning of masked test data. | Masking features used without separate licence. High per-processor cost creates significant exposure. |
Organisations that implement a full private database cloud often need Cloud Management Pack ($7,500/proc), Database Lifecycle Management Pack ($12,000/proc), Diagnostics Pack ($7,500/proc), Tuning Pack ($5,000/proc), and sometimes Data Masking Pack ($11,500/proc). The combined stack can reach $32,000 to $43,500 per processor in management pack licences alone, on top of the base Oracle Database EE licence ($47,500/proc). For 8 processors, that is $256,000 to $348,000 in pack licences. For negotiation strategies on management pack bundling, see our guide to managing Oracle contracts.
It is an add-on module for Oracle Enterprise Manager that enables private cloud functionality for Oracle Databases. This includes self-service database provisioning, automated lifecycle management, resource pooling, and chargeback/showback reporting. It transforms your Oracle Database platform into an internal DBaaS.
No. It is a separate licensed product. Oracle Database Enterprise Edition does not include it. The only exception is certain Oracle Cloud services (DB Cloud Service at High Performance/Extreme Performance tiers, Exadata Cloud Service) where Oracle bundles the pack features into the cloud subscription at no extra cost.
It uses the same licensing metrics as Oracle Database Enterprise Edition: per Processor (per core, after applying Oracle's core factor) or per Named User Plus. You must licence the pack for every database server managed as part of your "database cloud" environment, and you must also have the Database Lifecycle Management Pack licensed as a prerequisite.
List price is $7,500 per processor or $150 per Named User Plus (one-time). Oracle charges 22% annual support ($1,650 per processor per year). You must also budget for the prerequisite Database Lifecycle Management Pack (~$12,000 per processor list). Four processors would cost $30,000 in Cloud Pack licences plus $6,600/year in support, before the Lifecycle Pack.
The biggest risks are: using Cloud Pack features accidentally (OEM often enables packs by default), failing to licence the prerequisite Lifecycle Management Pack, mixing up NUP and Processor metrics on the same server, assuming dev/test environments do not require licensing, and not tracking hardware changes that increase the required licence count. All of these create audit exposure that Oracle LMS will identify.
Yes. Oracle requires the Database Lifecycle Management Pack as a prerequisite for the Cloud Management Pack. The Cloud Pack builds on the Lifecycle Pack's provisioning, cloning, and patching automation capabilities. Using Cloud Pack without the Lifecycle Pack licence creates a compliance violation even if you own Cloud Pack itself.
Yes, if you use third-party automation tools that do not invoke Oracle Enterprise Manager's Cloud Pack APIs or features, you do not need a Cloud Pack licence. Ansible, Terraform, and similar tools can automate Oracle Database provisioning without triggering Oracle management pack licensing. Verify that your automation does not call any OEM Cloud Pack specific functionality.
Cloud Management Pack follows the same virtualisation rules as Oracle Database. Oracle treats VMware, Hyper-V, and KVM as soft partitioning, requiring all physical cores across the cluster to be licensed. Oracle VM is recognised as hard partitioning, allowing you to licence only the assigned cores. This can create enormous cost differences. See our Oracle Partitioning Policy guide.
Oracle's management packs are one of the most common sources of unplanned compliance exposure. Our independent Oracle advisory team helps enterprises right-size pack licensing, defend against audit findings, and negotiate favourable terms. Independent. Fixed-fee. No Oracle bias.
Oracle Advisory ServicesIndependent Oracle Cloud Management Pack licensing advisory. Compliance assessment, cost optimisation, audit defence. Fixed-fee. Vendor-independent.