This might be the most important blog post on this site from a business perspective. Oracle Database licensing is complex on-premises. In the cloud, it’s complex in different ways, with different traps. DBAs are not typically licensing experts, but they make decisions daily that have significant licensing implications — which features to enable, which cloud service to use, whether to bring on-prem licenses to the cloud. Getting this wrong is expensive. I’ve seen organizations receive Oracle audit letters for six-figure unplanned costs because a DBA enabled a feature without understanding the licensing implications.

I’m not an Oracle licensing attorney and nothing here is legal advice. But these are the patterns that cause the most problems.

The Diagnostic Pack and Tuning Pack Trap

AWR, ASH, ADDM — the tools I’ve described throughout this blog — require Oracle Diagnostic Pack license (included with Oracle Enterprise Edition, not Standard Edition). SQL Tuning Advisor and SQL Access Advisor require Oracle Tuning Pack.

These packs are enabled by default in Oracle Database. If you’re running Oracle Standard Edition or Standard Edition 2, and you’re generating AWR reports or looking at ASH data, you’re using unlicensed features.

sql

-- Check if Diagnostic/Tuning Pack usage is enabled
SELECT name, value FROM v$parameter
WHERE name = 'control_management_pack_access';
-- Values: DIAGNOSTIC+TUNING (both packs), DIAGNOSTIC (diagnostic only), NONE
-- If you don't have the licenses, set to NONE:
ALTER SYSTEM SET CONTROL_MANAGEMENT_PACK_ACCESS = 'NONE' SCOPE=BOTH;

Disabling these packs doesn’t break your database. It disables the licensed features. On Standard Edition, you can still use Statspack (the free alternative to AWR) for performance monitoring.

On OCI: Autonomous Database and DB System with Enterprise Edition includes the Diagnostic and Tuning Pack. But if you’re running Oracle Standard Edition 2 on OCI DB System, these packs are not included. The same SQL commands apply.

BYOL vs License Included on OCI — When BYOL Saves Money

OCI offers two licensing models:

License Included (LI): Oracle charges a higher hourly rate that includes the database license cost. Simple, predictable.

Bring Your Own License (BYOL): You use your existing on-premises Oracle licenses. Lower hourly OCI rate. Requires eligible on-prem licenses.

BYOL makes economic sense when you have existing Oracle licenses retiring from on-prem hardware. The per-OCPU cost difference between LI and BYOL is significant — often 40-60% lower for BYOL.

The trap: Oracle’s License Mobility rules for cloud are specific. Not all Oracle licenses are eligible for BYOL on OCI. Named User Plus licenses have different conversion rules than Processor licenses. Licenses on hardware past End of Service Life may have eligibility restrictions.

Before choosing BYOL on OCI, verify your license eligibility through Oracle’s LMS (License Management Services). Using BYOL with ineligible licenses is exactly the kind of thing Oracle audits catch.

Standard Edition 2 — The RAC Restriction

Oracle Standard Edition 2 (SE2) does not support Oracle Real Application Clusters as of Oracle 19c. RAC was removed from SE2 in 19c. If you’re running SE2 with RAC (which was technically possible on SE2 in 12c with restrictions), this configuration is not supported — and therefore potentially not licensed — in 19c and later.

On OCI, this is enforced at the service level — you can’t provision a RAC DB System with SE2 edition. But if you’re migrating an old on-prem 12c SE2 RAC to OCI, you need to either upgrade to Enterprise Edition or eliminate RAC from your architecture.

Options and Packs — The Features Most DBAs Don’t Know Are Licensed

These Oracle Database features require separate, additional licenses beyond base Enterprise Edition:

• Oracle Partitioning: CREATE TABLE ... PARTITION BY requires Partitioning license
• Oracle Advanced Compression: compression beyond basic requires this license
• Oracle Advanced Security: required for TDE on on-premises EE (TDE is included in cloud services)
• Oracle Multitenant: more than 1 PDB per CDB requires Multitenant option (21c and later)
• Oracle In-Memory: INMEMORY clause on tables requires Oracle In-Memory option
• Oracle Database Vault: separation of duties for DBAs

sql

-- Check which options have been accessed on this database
SELECT parameter, value
FROM v$option
WHERE parameter IN (
    'Partitioning',
    'Advanced Compression',
    'Oracle Database Vault',
    'Oracle In-Memory',
    'Transparent Data Encryption',
    'Multitenant'
);

A TRUE value means the feature is installed. If v$option shows a feature as TRUE and you’ve ever used it — even in dev — Oracle’s audit methodology counts it as used.

The OCI Always Free Tier — Licensing Is Not a Concern

One genuinely clean licensing scenario: OCI Always Free Autonomous Database (20GB, 1 OCPU). This is free. Forever. No license required. All features available. Oracle absorbs the license cost entirely.

For development, POC work, lightweight applications, and learning — this is the most license-risk-free Oracle Database you can run.

My Practical Advice

If you’re a DBA making decisions about Oracle features, cloud services, or license model selection:

1. Know which features require separate licenses — the list above is a start
2. Before enabling any feature in production, check its license status
3. On OCI, License Included pricing removes most on-prem license complexity — often worth the premium for peace of mind
4. If your organization is considering a significant Oracle cloud expansion, engage Oracle LMS proactively — they’d rather consult than audit
5. Document every licensing decision — “we chose LI specifically to avoid BYOL compliance risk” is a defensible record

Licensing is not a glamorous part of the DBA role. But an Oracle audit letter is one of the fastest ways to end up in a very uncomfortable conversation with your CFO.