Editorial photograph of analytics dashboard on widescreen monitor representing Oracle Analytics Cloud buyer side advisory
Guide · Oracle · OAC

Oracle Analytics Cloud. The complete licensing guide.

A buyer side reference on Oracle Analytics Cloud licensing. OCPU math, BYOL conversion, Autonomous Database pairing, and the seven leverage points on every OAC contract.

Read the guide Contact Us
26Buyer Side OAC Engagements
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent
Key Takeaways

What every buyer must know about Oracle Analytics Cloud licensing.

  • OCPU is the bill driver. Right size OCPU at signing. Over provisioning is the single largest source of overspend.
  • BYOL converts OBIEE perpetual into OAC OCPU. One OBIEE EE processor equals two OAC OCPU.
  • Edition selection matters. Professional edition is half the OCPU rate of Enterprise edition.
  • Autonomous Database bundle discount. The pair price runs 15 to 25 percent below the sum of the two SKUs.
  • No support ceiling at renewal. Anchor renewal uplift caps at signing.
  • Universal Credits are flexible but expire. Unused credit does not roll over.
  • OCI native deployment. The Authorized Cloud Environment policy does not apply.

Two licensing metrics on Oracle Analytics Cloud

Oracle Analytics Cloud uses two metrics. Metered OCPU consumption is the default. BYOL conversion is the alternative when the customer holds idle perpetual OBIEE licenses.

OCPU metered subscription

The buyer commits to a monthly or annual Universal Credit pool. OAC consumes OCPU from that pool at the per hour rate. The bill is the OCPU rate multiplied by the hours consumed.

OCPU consumption is metered at the instance level. Stopping the instance stops the meter. Sizing the instance correctly is the largest cost lever.

BYOL conversion

BYOL stands for Bring Your Own License. The customer applies existing OBIEE perpetual licenses against OAC OCPU consumption. The conversion ratio is one OBIEE EE processor equals two OAC OCPU.

BYOL is the right choice when the customer has idle OBIEE processors and active support. If support has lapsed, the customer cannot use BYOL.

Edition mapping and per OCPU pricing

OAC comes in two editions on new sales. The Standard edition is retired. The Professional edition is the entry tier. The Enterprise edition adds advanced features.

Edition feature comparison

FeatureProfessionalEnterprise
Data visualizationYesYes
Semantic modelingYesYes
Pixel perfect reporting (BI Publisher)NoYes
Mobile native appsNoYes
Data preparation flowsLimitedFull
Embedded analytics in third party appsNoYes
OCPU rate per hour (list)$2.0152$4.0304

When to use each edition

  • Professional: data discovery and self service dashboards for a finance, operations, or marketing team.
  • Enterprise: regulated pixel perfect reporting, mobile delivery, and embedded analytics across business apps.
  • Mixed deployment: some customers run Professional for departmental use cases and Enterprise for the regulated reporting workload. The buyer side must validate this mix at renewal.

BYOL conversion math

BYOL is the largest cost lever for buyers with an existing OBIEE estate. The conversion ratio is fixed: one OBIEE EE processor equals two OAC OCPU.

Example BYOL economics

PositionMetered subscriptionBYOL conversion
OCPU commit40 OCPU annual40 OCPU annual
OAC list rate$4.0304 per OCPU hour$2.4182 per OCPU hour (BYOL)
Annual hours8,7608,760
Annual fee at list$1,412,253$847,377
Required OBIEE processorsNone20 OBIEE EE processors with active support
OBIEE support annual cost$0$104,016 (22 percent of $472,800 list)
Total annual cost$1,412,253$951,393
SavingsBaseline$460,860 per year

The hidden BYOL trap

BYOL math looks clean at signing. The trap is support cost. If the customer drops OBIEE support to save the 22 percent annual fee, the BYOL right disappears. The customer is then locked into the higher metered rate. Always model BYOL with the support line included.

Pairing OAC with Autonomous Database

Oracle pairs OAC with the Autonomous Data Warehouse SKU at a discount. The bundle is sold as Autonomous Database for Analytics. The pricing is the sum of the two SKUs less a 15 to 25 percent bundle discount.

Three deployment patterns

  • OAC standalone: the customer connects OAC to a non Oracle data warehouse (Snowflake, BigQuery, Redshift, Databricks). The bundle discount does not apply.
  • OAC plus Autonomous Data Warehouse: the customer runs both. The bundle discount applies. This is the most common enterprise pattern.
  • OAC plus Autonomous Transaction Processing: the customer runs OAC against transactional Autonomous Database. The bundle discount applies but at a lower tier.

The OAC plus Autonomous bundle looks generous on the price sheet. Strip it apart line by line and the discount is often only 12 percent. Negotiate the bundle as two separate SKUs, then ask for the bundle premium back.

Universal Credits and the OCPU pool

Universal Credits is the Oracle Cloud commitment model. The buyer commits to an annual dollar pool. The pool draws down as OCPU is consumed across all Oracle Cloud services, including OAC.

Universal Credits mechanics

  • Commit tiers: from $5K monthly to $1M plus monthly. Discount scales with commit size.
  • Overage: consumption above the commit bills at the on demand rate, not the committed rate.
  • Rollover: unused commit does not roll over to the next term. Unused credit is forfeited.
  • Cross service consumption: the commit pool serves OAC, Autonomous, OCI compute, OCI storage, and every other OCI service.

Seven leverage points on every OAC contract

  1. Right size OCPU at signing. Most buyers oversize by 30 to 50 percent. Rebuild the sizing from actual peak usage.
  2. BYOL math with support included. Always model the OBIEE support line. Do not assume BYOL is free.
  3. Edition split. Use Professional for departmental, Enterprise only where features require it.
  4. Bundle vs unbundled negotiation. Negotiate OAC and Autonomous as two SKUs, then ask for the bundle discount on top.
  5. Renewal uplift cap. Anchor at zero to three percent at signing.
  6. Universal Credits overage protection. Negotiate an overage cap or a true up window.
  7. Auto pause on dev and test instances. Cut OCPU consumption by 40 to 60 percent on non production.

What to do next

  1. Pull your current OAC OCPU consumption from OCI cost analysis.
  2. Map your OBIEE perpetual processor count and validate support is active.
  3. Model both metered and BYOL paths against actual usage.
  4. Validate the Autonomous Database bundle against unbundled pricing.
  5. Right size non production instances and enable auto pause.
  6. Anchor renewal uplift caps before signing.
  7. Engage independent buyer side advisory if the OAC line is over $500K annually.

Frequently asked questions

How is Oracle Analytics Cloud licensed?

Two metrics. OCPU consumption on a metered subscription is the default. BYOL conversion lets the customer apply existing OBIEE perpetual licenses against OAC OCPU consumption at a one to two ratio. The OCPU rate is the bill driver in both cases.

What is the OCPU per hour rate on OAC?

List price is 2.0152 dollars per OCPU per hour on the Professional edition. The Enterprise edition runs 4.0304 dollars per OCPU per hour. The Standard edition is retired on new sales. Discounts run 25 to 50 percent through Universal Credits and 50 to 70 percent through annual commit.

Should we use BYOL or metered subscription on OAC?

BYOL is cheaper when the customer holds idle OBIEE perpetual licenses. The conversion is one OBIEE Enterprise Edition processor license for two OAC OCPU. If the customer has 20 OBIEE processors idle, that translates to 40 OAC OCPU. The savings are 40 percent on the metered list rate.

How does OAC pair with Autonomous Database?

Oracle bundles OAC with the Autonomous Data Warehouse SKU at a discount. The bundle is positioned as Autonomous Database for Analytics. The pricing is the sum of the two SKUs less a 15 to 25 percent bundle discount. The buyer side must validate the bundle math against the unbundled price.

What is the support cost on OAC?

Support is included in the subscription rate. There is no separate 22 percent support line as on the perpetual OBIEE base. The trade off is that the price reset hits at renewal with no support ceiling protection unless negotiated.

Can OAC run on third party clouds?

OAC runs natively on Oracle Cloud Infrastructure (OCI). The OBIEE perpetual base can run on AWS, Azure, or Google Cloud, but OAC itself is OCI native. The Authorized Cloud Environment policy applies to perpetual OBIEE deployed elsewhere, not to OAC.

What is the typical OAC contract term?

Three years is standard on enterprise OAC contracts. One year is available but rare. Five years is offered with additional discount tiers. The annual commit model uses Universal Credits, which carries flexibility but no rollover for unused OCPU.

How does Redress engage on Oracle Analytics Cloud?

We run the buyer side process from BYOL conversion math through OCPU sizing through final negotiation. We are not an Oracle partner, do not resell Oracle, and take no kickbacks from Oracle.

Run our Oracle Java License Calculator across your estate.
Open the calculator →
500+
Enterprise Clients
$2B+
Under Advisory
11
Vendor Practices
100%
Buyer Side
Industry
Recognized

Most OAC contracts oversize OCPU by 40 percent. The biggest BYOL savings come before signing, not at renewal.

Fredrik Filipsson
Co Founder, ex Oracle
White Paper · Oracle

Download the Oracle ULA Decision Framework.

A buyer side reference on the Oracle ULA decision: enter, exit, certify, or restructure. Deployment math, certification audit, and renewal leverage.

Independent. Buyer side. Written for CIOs, CFOs, and procurement leaders carrying Oracle contracts. No vendor influence. No sales kickback.

Oracle ULA Decision Framework

Open the white paper in your browser. Corporate email only.

Open the Paper →
More Reading

More from this practice.

All Oracle articles →
Oracle BYOL Strategy Guide
Oracle · Article
Oracle BYOL Strategy Guide
How buyers convert idle perpetual licenses into OCI consumption savings.
10 min read
Oracle HCM Cloud Licensing Guide
Oracle · Article
Oracle HCM Cloud Licensing Guide
Buyer side reference on Oracle HCM Cloud subscription metrics.
12 min read
Oracle EBS Licensing Guide
Oracle · Article
Oracle EBS Licensing Guide
Buyer side reference on Oracle E Business Suite licensing.
13 min read
Oracle ULA Buyers Guide
Oracle · Article
Oracle ULA Buyers Guide
Enter, exit, certify, or restructure the Oracle Unlimited License Agreement.
15 min read
Editorial photograph of enterprise contract negotiation strategy

Ready to price your Oracle OAC deal correctly?

Independent buyer side advisory. No vendor influence. No sales kickback. We sit on your side of the table when you negotiate with Oracle.

Get the buyer side brief.

Monthly. One email. Zero noise.