Oracle Database Options are separately licensed features built into Oracle Database Enterprise Edition. They are not included in the base EE licence — each is a distinct product with its own list price, typically equal to or greater than the base EE processor licence. The most commercially significant Options — Diagnostics Pack, Tuning Pack, Partitioning, Advanced Security, and RAC — are installed in every Oracle Database EE installation and can be activated through routine database administration actions without the DBA being aware that they are triggering a licence requirement. This article is part of our Oracle license negotiation guide. For a broader view of Oracle Database licensing, see our Oracle Database licensing guide. Hands-on Oracle Options licence review is available through our Oracle advisory practice.
Oracle Partitioning is the most widely misunderstood of all Oracle Database Options. It appears to be part of standard Oracle Database functionality — because in many respects it is, as it is always installed and its DDL syntax is available without any explicit enablement. The licensing requirement is triggered not by installing Partitioning (you cannot avoid this — it installs with every Oracle Database EE), but by using it. And Oracle LMS's scripts query the DBA_FEATURE_USAGE_STATISTICS view to identify any use, however brief, however inadvertent.
What Oracle Database Partitioning Does
Oracle Database Partitioning is a feature that allows database tables and indexes to be divided into smaller, more manageable segments called partitions. Each partition contains a subset of the data, defined by a partition key — typically a date, range, or list value. Partitioning provides three primary operational benefits: improved query performance through partition pruning (the database only scans relevant partitions rather than entire tables); improved manageability through partition-level operations (backup, archive, drop); and improved availability through partition-level maintenance operations.
Partitioning is genuinely valuable for large tables — particularly time-series data, financial transaction history, log archives, and any dataset where queries are commonly filtered on the partition key. For very large tables (hundreds of millions of rows), partitioning is one of the most effective tools for maintaining query performance and managing data lifecycle. The question is not whether Partitioning provides value — it does — but whether the licence cost is justified given the available alternatives.
Partitioning Option Licensing Cost
Oracle Database Partitioning is licensed as a Database Option on top of Oracle Database Enterprise Edition. The list price in 2026 is $23,500 per processor licence — approximately half the EE base price. Annual support on Partitioning adds 22 percent per year ($5,170 per processor). For a deployment with 20 processor licences, the Partitioning Option adds $470,000 to the licence cost and $103,400 to the annual support bill.
Free Guide
Oracle Licensing & Negotiation Guide
Everything you need to navigate Oracle's complex licensing rules, true-up traps, and negotiation levers.
Partitioning must be licensed for every Oracle Database processor licence that accesses a partitioned table — not just the processors where partitioning was created. If a partitioned table is in a shared database accessed from multiple servers, all servers accessing that database require a Partitioning licence. This cross-server scope is frequently underestimated in internal licence position assessments.
The cost of common Oracle Database Options in 2026, ranked by list price per processor:
| Oracle DB Option | List Price / Processor | Annual Support / Processor | Audit Frequency |
|---|---|---|---|
| Real Application Clusters (RAC) | $23,000 | $5,060 | Very High |
| Diagnostics Pack | $7,500 | $1,650 | Extreme |
| Tuning Pack | $5,000 | $1,100 | Extreme |
| Partitioning | $23,500 | $5,170 | Very High |
| Advanced Security | $15,000 | $3,300 | High |
| In-Memory Database | $23,000 | $5,060 | Moderate |
How Oracle Detects Partitioning Use
Oracle LMS audit scripts query the DBA_FEATURE_USAGE_STATISTICS view in Oracle Database, which tracks every Oracle feature that has been accessed on that database instance. The feature tracking is automatic and continuous — it requires no deliberate action by the DBA, no explicit activation, and no configuration change. Every CREATE TABLE ... PARTITION BY statement, every query that accesses a partitioned table, and every partition-level maintenance operation increments the Partitioning feature usage counter.
The practical consequence is that Partitioning use is essentially undeniable in an audit once it appears in DBA_FEATURE_USAGE_STATISTICS. Oracle LMS will present the feature usage data as definitive evidence of licence requirement. The only defences are: (a) that the usage count was zero or was attributable to a licensed test environment; (b) that the partitioned tables were subsequently removed before the audit measurement date; or (c) that the DBA_FEATURE_USAGE_STATISTICS data is inaccurate (which is extremely difficult to demonstrate).
Stay Ahead of Vendors
Get Negotiation Intel in Your Inbox
Monthly briefings on vendor pricing changes, audit trends, and contract tactics. Unsubscribe any time.
No spam. No vendor affiliations. Buyer-side only.
Critical Risk: Oracle applications — including Oracle E-Business Suite, Oracle Retail, Oracle Banking, and other packaged Oracle applications — may create partitioned tables automatically during installation or maintenance operations. Organisations running Oracle applications on Oracle Database EE may inadvertently trigger a Partitioning licence requirement through routine application maintenance, without any decision being made to use Partitioning. An Oracle application estate should always be assessed for Partitioning usage as a priority action.
Checking Your Own Partitioning Usage
Before Oracle LMS runs their scripts, you can assess your own Partitioning usage status by querying the feature usage statistics in each Oracle Database instance. The key queries to run:
SELECT name, detected_usages, currently_used, first_usage_date, last_usage_date
FROM dba_feature_usage_statistics
WHERE name LIKE '%Partition%'
ORDER BY name;
-- Check for partitioned tables in the database
SELECT owner, table_name, partitioning_type
FROM dba_part_tables
WHERE owner NOT IN ('SYS','SYSTEM','ORACLE_OCM')
ORDER BY owner, table_name;
If the first query returns rows with detected_usages greater than zero, or if the second query returns application tables with partitioning defined, a Partitioning licence is required (or the usage and partitioned tables must be removed and the feature usage counters allowed to reset). Resetting DBA_FEATURE_USAGE_STATISTICS after removing partitioned tables takes time — Oracle's scripts measure usage over rolling periods — so early detection and remediation is essential.
Alternatives to Oracle Partitioning
For organisations that need the performance and manageability benefits of partitioning but want to avoid the Oracle Partitioning licence cost, several approaches are available:
Application-Level Partitioning (Manual Sharding)
The application manages data distribution across multiple tables — for example, creating separate tables per year (ORDERS_2024, ORDERS_2025) and querying the appropriate table based on the date range. This approach requires application code changes but eliminates the Oracle Partitioning dependency entirely. It is most practical for new applications or significant rearchitecting projects.
Oracle Standard Edition 2 (No Options)
Oracle Database Standard Edition 2 does not include any Database Options — Partitioning is not available in SE2. This makes SE2 structurally safe from Partitioning audit findings. If workloads can be migrated to SE2 (see our Oracle license optimisation guide), the Partitioning question disappears entirely.
PostgreSQL Declarative Partitioning
PostgreSQL has included native declarative table partitioning since version 10 (2017). PostgreSQL partitioning supports range, list, and hash partitioning strategies — broadly equivalent to Oracle's partitioning methods — and is available at zero licence cost. For organisations evaluating migration away from Oracle Database, PostgreSQL's partitioning capabilities are production-grade and well-supported. Our Oracle to PostgreSQL migration guide covers the migration pathway.
Negotiating Oracle Partitioning in a Commercial Context
When Partitioning is genuinely required — because the workload demand justifies it and alternatives are not viable — the commercial strategy is to bundle Partitioning with other Oracle products in a structured negotiation rather than purchasing it as a standalone add-on. Oracle Partitioning purchased as part of an ELA, ULA, or volume discount negotiation can be obtained at 50 to 65 percent of list price, compared to 20 to 35 percent discount for standalone Option purchases.
An alternative commercial approach is to negotiate with Oracle to include Partitioning in an ELA bundle covering other Oracle products at renewal, using the broad Oracle spend as leverage for the Partitioning component. Oracle's standard ELA structures include technology Options as bundled components, making this a natural vehicle for addressing Partitioning costs as part of a broader Oracle renewal strategy.
Conclusion
Oracle Database Partitioning is a valuable feature for the right workloads — but its licence cost, audit detectability, and default installation make it one of the highest-risk Oracle Database Options from a compliance perspective. Organisations should assess their Partitioning usage as a standard part of any Oracle estate review, remediate unintended usage proactively, and evaluate both technical alternatives and commercial structures for managing the cost where Partitioning is genuinely required.
IT Negotiations provides Oracle Database Options assessments as part of every Oracle estate review engagement. Contact our team for a confidential assessment of your Oracle Partitioning licence position.
Are You Accidentally Using Oracle Partitioning?
Our Oracle Database specialists identify unintentional Option usage across your estate — and quantify the audit exposure before Oracle LMS arrives.