JSON Relational Duality and the document features in 23ai are core Enterprise Edition capabilities with no separate license, so the headline feature will not raise your bill by itself. The exposure sits underneath: the paid options your JSON tables quietly activate, and the audit evidence that records every one of them.
JSON Relational Duality and the document features in 23ai are core Enterprise Edition capabilities with no separate license, so the headline feature will not raise your bill by itself. The exposure sits underneath: the paid options your JSON tables quietly activate, and the audit evidence that records every one of them.
JSON Relational Duality does not change your license scope on its own. Oracle delivered it as a converged-database capability in 23ai, generally available, not an add-on option, and it functions identically across both Standard Edition 2 and Enterprise Edition. There is no line item called JSON Relational Duality on the price list. The same is true of the non-duality JSON Collection views and JSON Collection tables introduced in 23ai, and of the native JSON datatype (OSON binary format) that actually shipped back in 21c. If a sales rep or an internal architect tells you the document model in 23ai carries its own license, they are wrong, and you should push back with the edition documentation in hand.
The scope question stops being simple the moment you ask what is happening beneath the JSON access layer. Duality is a view. The data lives in relational tables, and those tables are subject to every paid Enterprise Edition option they touch: Partitioning at $11,500 per processor, Advanced Compression, Diagnostics Pack, and so on. You are charged based on what you use, not what you installed, and Oracle's LMS scripts are built to catch usage that was accidental, historical, or driven by a default setting. That is the real risk in this article, and it is why we run a review before any 23ai migration rather than after. Our pre-migration license review checklist exists precisely to surface this class of exposure before Oracle does.
Duality is free. The Partitioned, compressed relational tables underneath it are not. Oracle audits the tables, not the view.
Base your negotiation on documented facts, not assumptions. The following capabilities are core to the converged engine in 23ai and carry no incremental license beyond the edition you already own:
That last point matters for cost planning. Oracle's marketing pitch to MongoDB shops is that you can move administration into Oracle and spend up to 50% less, with document sizes up to 32 MB against a smaller Atlas ceiling. Treat the 50% figure as a vendor claim, not a modeled saving. It compares Oracle's own configuration against a MongoDB baseline the vendor selected. In our experience the number only holds when you already own the underlying Oracle licenses and are folding document workloads onto existing capacity. If you are buying net-new processors to host document data, the economics look very different, and you should model both paths before committing.
None of the 23ai licensing metrics changed relative to prior releases. Enterprise Edition remains $47,500 per processor (with 22 percent annual support at $10,450 per processor per year) or $950 per Named User Plus. Standard Edition 2, the cheaper landing spot for lighter document workloads, lists at $17,500 per processor or $350 per NUP. Processor count is physical cores multiplied by Oracle's core factor for the CPU type, which is where most miscalculations begin. Keep the table below in front of you during any 23ai scoping conversation.
| Item | List (per processor) | Annual support (22%) | Notes |
|---|---|---|---|
| Enterprise Edition | $47,500 | $10,450 | Duality and JSON included at this level |
| Standard Edition 2 | $17,500 | N/A (SE2 support differs) | Duality also included; caps on cores and features |
| Partitioning option | $11,500 | $2,530 | Common accidental trigger under JSON collection tables |
| RAC option | $23,000 | $5,060 | Cluster scaling exposure |
| Multitenant / others | Additional | Additional | On top of EE, per option |
One naming point that trips up buyers writing 2026 plans: as of the October 2025 update, Oracle rebranded 23ai as 26ai. In substance they are the same product (the banner reads 23.26.1 for the January 2026 release) and there are no licensing changes tied to the rename. Do not let a rep use the version relabel as a pretext to renegotiate metrics or re-shape your entitlement. If you want the fuller metric picture across editions and options, our CIO playbook on Oracle option rationalization lays out the full option stack and where the shelfware usually hides.
The version changed from 23ai to 26ai. The license did not. Reject any renegotiation that pretends otherwise.
Here is the mechanism that turns a free feature into a back-license claim. When you build document workloads at scale in 23ai, the natural engineering instinct is to partition or shard the JSON collection tables for performance. Oracle's own JSON full-text search documentation describes JSON tables partitioned across shards. The moment a JSON collection table is partitioned, you have used the Partitioning option, and Partitioning requires explicit licensing at $11,500 per processor. The developer who ran the DDL almost certainly did not know they were consuming a paid option. Oracle's LMS scripts do not care about intent.
The same trap applies to Advanced Compression (if you compress the underlying tables), Diagnostics and Tuning Packs (if anyone runs an AWR report against the workload), and RAC (if you scale the document tier onto a cluster). The document model does not change these rules. It just increases the surface area where relational options get invoked, because document workloads tend to be high-volume, performance-sensitive, and built by developers who are not thinking about the price list. Our guidance on running your own internal Oracle audit covers exactly how to hunt these down before the vendor arrives.
The permanence of the evidence is what makes this dangerous. Feature usage is recorded in DBA_FEATURE_USAGE_STATISTICS with a first-use date, last-use date, and usage count. It is the single most commercially dangerous element of the USMM output, because it captures usage regardless of whether it was accidental, historical, or a default. Even if you deactivate Partitioning tomorrow, the record of past use survives and is discoverable in an audit. There is no clean retroactive fix. The only defense is knowing what your JSON workloads touched before Oracle asks.
Oracle would prefer you land document workloads on Autonomous JSON Database (AJD) in OCI rather than self-manage them on your existing EE estate. AJD is the document-store-oriented configuration of Autonomous Database, alongside ATP for OLTP and ADW for analytics. The commercial hook is Bring Your Own License: one processor license (or 25 Named User Plus) covers 8 ECPUs or 2 OCPUs, and BYOL reportedly cuts Autonomous compute costs by 76 percent against License Included pricing. Autonomous Shared ATP lists at roughly $1.34 per OCPU hour at 2026 benchmarks.
The nudge is real, but read it as a channel-of-consumption decision, not a feature-availability decision. Duality and JSON work on-prem in your self-managed 23ai just as they do in AJD. The reasons to move to AJD are operational (Oracle manages patching, scaling, and the MongoDB API surface) and, for some buyers, financial via BYOL. The risk is that AJD masks the option exposure rather than removing it, and that License Included pricing on document workloads compounds fast if you are not applying BYOL against licenses you already own. We compare these paths in detail in the analysis of Autonomous versus self-managed 23ai cost, and the same logic applies to document workloads as to AI features.
Note also that Oracle now marks a number of database options as available only in OCI, and 23ai Free excludes several options entirely. That is a slow, structural pull toward the cloud. It does not affect Duality itself, which remains free everywhere, but it should factor into any multi-year document-store roadmap. If you are weighing the Free edition for prototyping or a document sandbox, our breakdown of the 23ai Free versus Enterprise Edition feature line shows exactly where the boundaries fall.
The forcing function behind most 23ai adoption is not the document model at all. Oracle Premier Support for Database 19c terminates on April 30, 2026, with Extended Support running through December 2026. Once Premier Support ends, you lose access to security patches, which pushes even conservative estates toward 23ai. Your existing licenses remain valid for 23ai use, so migration is not a new purchase event by default. The danger is that the migration process itself surfaces undocumented databases, unlicensed optional features, and metric misalignments that Oracle will expect remediated before its audit scrutiny tightens.
This is not hypothetical. We have seen LMS teams arrive with back-license claims in the eight-figure range: a $12M claim covering Diagnostics Pack, Partitioning, and RAC exposure across 47 databases is a real settlement scale, not a scare number. If you are adding JSON and duality workloads during the same migration window, you are stacking a new usage pattern on top of an estate that is already under scrutiny. Sequence the work so the internal license review completes before the JSON workloads go live, not after. Our buyer-side audit risk assessment is designed to run in exactly this window.
Net position: the document features in 23ai do not change your license scope directly, and buyers who fear a hidden Duality charge are worrying about the wrong thing. The scope changes only through second-order effects, the paid relational options that JSON workloads activate, the OCI-only drift in the option catalog, and the audit exposure that any migration surfaces. Control those three and the document model is a genuine capability upgrade at no incremental license cost. Ignore them and a free feature becomes the entry point for a seven-figure claim.
No. JSON Relational Duality is a core converged-database capability in 23ai, generally available, and it functions identically in both Standard Edition 2 and Enterprise Edition. There is no separate license line item for it. The cost risk comes from paid options the underlying relational tables may invoke, not from the duality feature itself.
Yes. If you partition or shard the JSON collection tables that back your document workload, you have used the Partitioning option, which lists at $11,500 per processor and requires explicit licensing. Oracle's usage tracking records this regardless of whether it was intentional. Require developer sign-off before any partitioning DDL runs in production.
It depends entirely on whether you apply Bring Your Own License. BYOL reportedly cuts Autonomous compute cost by about 76 percent versus License Included pricing, with one processor license covering 2 OCPUs. Model it on your own numbers. Oracle's marketing claim of spending up to 50 percent less than MongoDB is a vendor comparison, not a guaranteed saving.
No. The October 2025 rebrand to 26ai is cosmetic. It is the same product (the banner reads 23.26.1 for the January 2026 release) with no licensing changes. Reject any attempt by a sales rep to use the version relabel as a reason to renegotiate metrics or entitlements.
Your existing licenses do remain valid for 23ai use, so it is not a new purchase by default. The risk is that the migration surfaces undocumented databases, unlicensed options, and metric misalignments that Oracle expects remediated. We have seen back-license claims reach $12M across 47 databases covering Partitioning, Diagnostics Pack, and RAC. Run your internal review before workloads go live.
Your leverage is documentation and timing. The document model is free, so refuse any charge attached to it directly. Run the feature usage scripts yourself before Oracle does, remediate accidental option usage on your own schedule, and time the work to precede an audit approach rather than follow it. Negotiated discounts of 40 to 70 percent are routine at volume, but the larger savings come from removing unused options.
Oracle Database 23ai bundles options you may never deploy. The buyer side guide to edition right sizing, option pruning, and AI Vector Search licensing.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
