Oracle Dedicated Region Minimum Capacity Commitment Rules: How MCC Actually Works in 2026, and Eight Levers to Right-Size It

Why MCC is the most consequential DRCC clause

The minimum capacity commitment (MCC) determines the floor that the customer pays Oracle for OCI services consumed inside a Dedicated Region, regardless of actual consumption. On a typical mid-size DRCC deal, the MCC runs $4M-$8M per year over a 5-7 year term. The MCC is paid in full whether the customer uses the capacity or not. Over a 5-year term at $6M MCC, that is $30M of guaranteed Oracle revenue - and at the typical 65-70 percent actual utilisation, $9M-$10.5M of that pays for capacity that does not get used.

MCC right-sizing - getting the floor at the right level for the actual ramp and steady-state consumption - is the single highest-leverage decision in a DRCC negotiation. The other contract clauses (escalator, exit, hardware refresh) move 5-15 percent of total contract value each. MCC right-sizing routinely moves 25-40 percent.

The mechanics below are based on the standard Oracle DRCC ordering document as published in 2026 and our experience across 30+ DRCC negotiations. The wider DRCC framework is in the Oracle Dedicated Region Guide; the broader contract levers are at DRCC contract negotiation; the post-signing optimisation playbook is at DRCC cost optimisation; the broader cloud framework sits at Oracle Cloud Licensing Guide.

How Oracle calculates the MCC floor

Oracle calculates the proposed MCC using a four-input model:

1. Customer-declared workload list (database services, compute, storage, options)
2. Oracle's internal sizing model converting that workload into ECPU and storage units
3. Oracle's discount matrix applied to the list price for those units
4. The contractual term length (3-, 5-, 7-year)

The output is a discounted annual price, with the term length producing a deeper discount. Oracle's standard discount tiers in 2026:

The discount looks attractive, but the customer is committed to the full MCC for the full term. The 7-year deepest discount comes at the cost of 7 years of MCC liability - a customer's actual workload trajectory over 7 years is rarely predictable enough to make this attractive without aggressive ramp and pooling clauses.

Critical reading note: the workload list Oracle uses to size the MCC comes from the customer's input at the bid stage. The discipline applied at this input stage determines the MCC outcome. Customers who over-state their workload to 'show commitment' or 'leave headroom' end up over-committed at a $30M-$50M cost over the contract life.

Which OCI services count toward MCC consumption

Not all OCI services drawn from inside the DRCC tenancy count equally against the MCC. The 2026 framework:

The implication: customers with substantial BYOL coverage on database options can effectively reduce the MCC required because BYOL options consumption does not count toward MCC. The customer with 100 ECPUs of License-Included EE + Database In-Memory at $0.6552/ECPU-hour consumes more MCC than the same customer running BYOL EE + BYOL Database In-Memory at $0.1008/ECPU-hour plus zero for the options.

Ramp profiles and year-1 mechanics

Oracle's default DRCC ordering document requires the customer to commit to the full annual MCC from day 1 of the contract. This is structurally unfair because customer workload migration into a new DRCC tenancy takes 12-24 months - the customer cannot consume the full MCC in year 1 even if they want to.

The MCC ramp profile is negotiable. Standard patterns we see granted on enterprise DRCC deals in 2026:

On a $6M annual MCC under a 50/75/100 ramp, year-1 cost is $3M instead of $6M, year-2 cost is $4.5M instead of $6M. Combined cash preservation across years 1-2: $4.5M.

Aggressive ramps and milestone-tied ramps are granted on roughly 60-70 percent of enterprise DRCC deals when asked for. They are never offered in the default contract.

Forfeiture rules at year-end

Unused MCC at year-end is forfeited by default. The Oracle ordering document language: 'Any unused minimum capacity commitment shall lapse at the end of the annual measurement period and shall not roll forward.'

This is the most expensive default in the contract. On a $6M MCC running at 65 percent actual utilisation, $2.1M of paid-for capacity is forfeited at year-end. Over 5 years, that is $10.5M of pure waste.

The forfeiture rule is negotiable in two ways:

1. Credit pooling (see next section). Unused MCC rolls into public-OCI Universal Credits.
2. Limited rollover clause. Up to 25 percent of unused MCC rolls into the next contract year. This is less common than pooling but easier to negotiate on smaller DRCC deals.

The customer who signs the default DRCC contract on a 5-year term should expect to write off $8M-$12M of forfeited capacity over the contract life. Neither pooling nor rollover is offered in the default contract - both must be asked for explicitly.

Credit pooling: MCC to Universal Credits

The MCC-to-Universal-Credits pooling clause is the most valuable negotiated MCC mechanism in 2026. The mechanics: unused MCC at year-end rolls into public-OCI Annual Universal Credits, allowing the customer to consume the rolled-over credit on any OCI public-region service during the following year.

This converts MCC waste into useful spend. A customer with a $6M MCC under-utilised by $1.5M (25 percent slack) gets a $1.5M Universal Credits balance in their public-OCI tenancy that can be used for any service - cheaper public-OCI Exadata, GenAI Service token consumption, MySQL HeatWave Lakehouse analytics, OCI Data Science compute - whichever the customer needs.

The pooling clause is granted on roughly 50-60 percent of enterprise DRCC deals when asked for. The Oracle deal team prefers to keep consumption inside the DRCC scope (it locks in the consumption pattern for the next contract renewal) but will agree pooling on competitive deals or where the customer's broader OCI relationship is material.

For customers with both DRCC and material public-OCI workloads, pooling effectively eliminates forfeiture and turns the MCC into a usage-flexible floor rather than a use-it-or-lose-it commitment.

True-up and burst capacity above MCC

Consumption above the annual MCC is billed at standard public-OCI rates with no discount, by default. This means the customer who exceeds MCC pays at retail rates for the excess - effectively losing the term-discount benefit on burst consumption.

The negotiable clause: above-MCC consumption is billed at the same effective rate as MCC consumption. This is granted on roughly 70 percent of enterprise DRCC deals when asked for. Without this clause, the customer who under-sized MCC and bursts above pays 12-38 percent more for the excess (the term-discount delta).

Worked example: a customer with a $6M MCC at 25 percent discount, who bursts to $7.5M of actual consumption in year 3 because a major workload migration arrived earlier than planned. The first $6M is billed at the discounted rate. The $1.5M excess is billed at public-OCI list - costing the customer $1.5M plus the $375K discount delta they would have got under the negotiated clause. Annual cost of not having the burst clause: $375K.

Annual MCC review process

The standard DRCC ordering document includes an annual MCC review at the end of each contract year. The default review is one-way - Oracle can propose an increase in the following year's MCC tier; the customer cannot propose a decrease unless the contract specifically allows.

Negotiate a bidirectional review clause. The customer should have the right to propose a downward MCC adjustment at the annual review if measured consumption over the trailing 12 months is below 75 percent of MCC. This is a critical safety valve - it provides a structured path to exit over-commitment without triggering the early-termination clause.

The bidirectional review is granted on roughly 40 percent of enterprise DRCC deals. Without it, the customer who finds themselves over-committed has only two options: continue paying for unused capacity or trigger early-termination (which carries 25-75 percent of remaining MCC value as exit fee, see DRCC contract negotiation Lever 4).

Eight levers to right-size the DRCC MCC

The eight specific levers we apply on DRCC MCC negotiations:

1. Validate the workload list inputs Oracle is using. The MCC is calculated from this input. Over-stated workloads produce over-sized MCC. Have your team independently size the workload list before sharing it with Oracle.
2. Maximise BYOL coverage to reduce MCC requirements. BYOL ECPUs cost roughly 70 percent less than License-Included. Every ECPU shifted from LI to BYOL reduces the MCC requirement proportionally.
3. Strip unused database options from the License-Included bundle. Oracle's default proposal often bundles Diagnostics, Tuning, Partitioning, Advanced Compression, In-Memory. Strip what is not needed. Each unused option is $400-$800/ECPU/year of unnecessary MCC.
4. Negotiate the ramp profile to 50/75/100 or aggressive equivalent. Preserves $1M-$3M of cash in years 1-2.
5. Negotiate the credit pooling clause. Eliminates year-end forfeiture, converts under-utilisation into useful public-OCI spend.
6. Negotiate the burst-above-MCC clause. Above-MCC consumption billed at MCC rates, not at public-OCI list.
7. Negotiate bidirectional annual MCC review. Provides a structured path to downward adjustment without triggering exit fees.
8. Cap the annual escalator at 0-3 percent. Default 8 percent compound escalator is the single largest hidden cost on the 5-year MCC.

The eight levers compound. A customer applying all eight on a $6M opening MCC proposal typically ends up at an effective $3.8M-$4.4M annual cost over the contract life - 27-37 percent below the opening proposal. The wider Oracle Negotiation Guide covers the broader procurement playbook and the Cloud Advisory service runs the MCC right-sizing as a fixed-fee engagement.

Frequently asked questions

What is the minimum MCC on a DRCC contract in 2026?

The published minimum DRCC MCC is $1M per year on a minimum 3-year term. In practice, Oracle's deal team typically presents MCCs starting at $3M-$5M per year because the DRCC infrastructure footprint (multiple Exadata + compute racks) requires a substantial baseline consumption to be commercially viable for Oracle. Customers wanting smaller commitments are usually redirected to Compute Cloud@Customer or ExaCC.

Can I reduce MCC mid-contract if workloads do not materialise?

Only if the contract explicitly allows. The standard DRCC ordering document does not allow downward MCC adjustment mid-term. The customer must negotiate the bidirectional annual MCC review clause at signing. Without it, the only routes are: continue paying the full MCC, or trigger early-termination (which carries 25-75 percent of remaining MCC value as exit fee).

How does Support Rewards interact with MCC?

Support Rewards earned on DRCC consumption ($0.25 per $1 consumed at the standard rate, $0.33 for ULA customers) convert to credits applied against the customer's annual Oracle technology support invoice. This effectively reduces the net cost of MCC consumption. On a $6M annual MCC with Support Rewards fully claimed, the net cost is $4.5M after $1.5M of support credits. See Oracle Support Rewards on OCI for the mechanics.

What happens if Oracle's hardware refresh is delayed?

Under the standard DRCC contract, nothing automatic - the customer continues paying full MCC against aged hardware. The contract clause to negotiate (see DRCC contract negotiation Lever 3) is a no-penalty exit right if Oracle misses the contractual hardware refresh date by more than 12 months. Without this clause, the customer is exposed to Oracle's hardware roadmap slippage with no contractual remedy.

How is MCC consumption measured?

Oracle uses the OCI Cost Analysis service inside the DRCC tenancy to measure ECPU-hours, OCPU-hours, GB-months, and option consumption. The measurement is monthly, with the annual MCC measured against the rolling-12-month consumption total. The customer should have direct access to OCI Cost Analysis and run their own monthly reconciliation against Oracle's billing - discrepancies are common and routinely resolved in the customer's favour when challenged.

Related Oracle licensing reading