Oracle Analytics Cloud licensing. End to end.

Oracle Analytics Cloud is licensed on a consumption metric, billed per OCPU per hour. The Oracle Analytics Cloud service meters on the compute it runs, not on the user count, which makes scheduling the main cost lever.

The licensing splits across a Professional and an Enterprise edition, with a Bring Your Own License path for customers carrying existing Oracle analytics licenses.

This guide sets the OCPU metric, the edition split, the BYOL math, and the OBIEE migration economics that decide the OAC bill.

How does the Oracle Analytics Cloud OCPU metric work?

Oracle Analytics Cloud bills per OCPU per hour. An OCPU is an Oracle compute unit, and the bill is the OCPU count multiplied by the hours the service runs.

Because the metric is compute and time, not users, the cost lever is scheduling. A cluster left running overnight or at the weekend bills for compute no one is using.

The scheduling lever

• Stop idle clusters outside business hours where the workload allows.
• Size to concurrent demand, not peak headroom.
• Use auto scaling so the OCPU count tracks real load.

What is the difference between OAC Professional and Enterprise?

Oracle Analytics Cloud splits across a Professional edition and an Enterprise edition. Professional covers self service visualization and reporting. Enterprise adds the semantic model, enterprise reporting, and the heavier governance capabilities.

Matching edition to need

The move is to match the edition to the actual capability used. Paying the Enterprise rate for a workload that only needs Professional visualization is a common and avoidable cost.

White Paper · Oracle

The Oracle Buyer Side Framework

The moves we use across Oracle Database, Java and ULA estates. Read it free.

Read it free

How does BYOL work for Oracle Analytics Cloud?

Customers carrying existing Oracle analytics licenses, including OBIEE, can apply them through a Bring Your Own License path that reduces the OAC cloud rate. The license offsets part of the consumption charge.

The check is the same as any BYOL: confirm the existing license covers the deployment and carries active support. Read the related Oracle pricing metrics playbook for the underlying license math.

• Confirm coverage: the existing license must cover the OAC footprint.
• Confirm support: BYOL requires active support on the underlying license.
• Model the offset: compare the reduced BYOL rate against the full cloud rate.

What are the OBIEE migration economics?

Customers moving from Oracle Business Intelligence Enterprise Edition to OAC face a migration economics question. The answer depends on whether the existing OBIEE licenses carry over through BYOL.

With carryover, the OAC rate is the reduced BYOL rate and the migration is largely a compute decision. Without it, the migration pays the full cloud rate, which changes the business case. Anchor the comparison against the published OCI price list.

How Redress engages on OAC

Redress right sizes OAC consumption, claims the BYOL carryover, and models the OBIEE migration inside the Benchmark Program. Vendor Shield covers the ongoing position. Read the Oracle services practice and the Oracle knowledge hub.

Where the common advice on Oracle Analytics Cloud sizing is wrong

The standard advice is to size Oracle Analytics Cloud for peak demand so users never hit a performance wall, then leave it running for availability. We disagree. Across the 15 to 25 OAC reviews we ran in 2024 and 2025, sizing for peak headroom inflated the OCPU count by 20 to 35 percent, and clusters left running outside business hours billed for 30 to 50 percent more hours than the workload needed. Because OAC bills on compute and time rather than users, idle headroom is pure carried cost. The buyer side move is to size to concurrent demand, schedule clusters to stop when idle, and let auto scaling absorb the occasional peak rather than paying for it around the clock.

What to do next

1. Measure concurrent demand. Profile real concurrent OAC usage across a full week.
2. Right size the OCPU count. Match compute to concurrent demand, not peak headroom.
3. Schedule the stops. Stop idle clusters outside business hours where the workload allows.
4. Match the edition. Use Professional where Enterprise capability is not needed.
5. Claim BYOL carryover. Apply existing OBIEE or analytics licenses to reduce the rate.
6. Model the OBIEE migration. Compare the BYOL rate against the full cloud rate.
7. Enable auto scaling. Let the OCPU count track real load.

Frequently asked questions

How is Oracle Analytics Cloud licensed?

Oracle Analytics Cloud is licensed on a consumption metric, billed per OCPU per hour. The bill is the OCPU count multiplied by the hours the service runs, so scheduling and sizing are the main cost levers, not the user count.

What is an OCPU in Oracle Analytics Cloud?

An OCPU is an Oracle compute unit. OAC bills per OCPU per hour, which means a cluster left running while idle continues to bill for compute that no one is using.

What is the difference between OAC Professional and Enterprise?

Professional covers self service visualization and reporting at a lower per OCPU rate. Enterprise adds the semantic model, enterprise reporting, and heavier governance at a higher rate. Match the edition to the capability actually used.

Can I use BYOL with Oracle Analytics Cloud?

Yes. Customers with existing Oracle analytics licenses, including OBIEE, can apply them through a Bring Your Own License path that reduces the cloud rate, provided the license covers the deployment and carries active support.

How do I reduce an Oracle Analytics Cloud bill?

Size to concurrent demand rather than peak headroom, schedule idle clusters to stop outside business hours, enable auto scaling, and claim any BYOL carryover. Oversizing and idle compute drive most avoidable OAC spend.

What are the OBIEE to OAC migration economics?

With BYOL carryover of existing OBIEE licenses, the OAC rate is the reduced BYOL rate and the migration is largely a compute decision. Without carryover, the migration pays the full cloud rate, which changes the business case.

Does Oracle Analytics Cloud bill by user?

No. OAC bills on compute consumed, measured per OCPU per hour, not on the number of users. This is why scheduling and right sizing the OCPU count matter more than headcount.

How do I right size Oracle Analytics Cloud?

Profile real concurrent usage across a full week, size the OCPU count to that concurrent demand rather than peak headroom, and let auto scaling absorb occasional peaks instead of paying for them around the clock.