Oracle Database 23ai is Oracle's most significant database release in years, introducing over 300 new capabilities including AI Vector Search, JSON Relational Duality, True Cache, Globally Distributed Database, and SQL Domains. Oracle's marketing presents 23ai as a unified platform for AI and operational workloads. What Oracle's marketing does not clarify is which of these new capabilities require additional license options, how AI Vector Search interacts with Oracle Database Enterprise Edition license obligations, and which features carry hidden compliance exposure when enabled in production. This independent guide cuts through Oracle's narrative to deliver the buyer-side analysis.
Oracle Database 23ai is the long-term support (LTS) release successor to Oracle Database 19c. The "ai" branding signals Oracle's strategic positioning of the database as an AI infrastructure platform, not just a relational engine. Technically, 23ai consolidates innovations from the 21c innovation release with a tranche of new AI-oriented capabilities, making it the recommended upgrade path for enterprises on 19c whose extended support contracts are approaching end-of-life in April 2027.
From a licensing standpoint, 23ai is not a new product requiring a separate license — existing Oracle Database Enterprise Edition or Standard Edition 2 licenses cover 23ai as a version upgrade. The compliance complexity arises from the new features themselves. Oracle's strategy in 23ai mirrors its historical playbook: embed capabilities that overlap with separately licenced options, make them easy to enable, and let LMS audit scripts detect their use after the fact. Enterprises that upgrade to 23ai without a forensic review of which new features are in scope for existing license options risk creating audit exposure before Oracle even sends a letter.
Oracle Database 23ai is available on-premise, on Oracle Cloud Infrastructure (OCI) via BYOL or Database Cloud Service, and via Oracle Autonomous Database. Each deployment model has distinct licensing implications covered below.
Independence note: Oracle Licensing Experts is not affiliated with Oracle Corporation. This analysis is independent, buyer-side guidance based on our team's 25+ years of Oracle licensing advisory experience. Not affiliated with Oracle Corporation.
Our Oracle Compliance Review identifies which 23ai features create license exposure before you deploy. We have protected enterprises from seven-figure back-license claims arising from version upgrades. Get a confidential assessment before Oracle's LMS team arrives.
AI Vector Search is the headline feature of Oracle Database 23ai, enabling vector embeddings to be stored, indexed, and queried natively within Oracle Database. This allows enterprises to build retrieval-augmented generation (RAG) architectures where Oracle Database serves as the vector store alongside relational data — a genuinely compelling capability for organizations already standardized on Oracle Database.
Oracle has confirmed that AI Vector Search is included in Oracle Database Enterprise Edition at no additional license cost. This distinguishes it from historically separate options like Partitioning, Diagnostics Pack, and Advanced Security, which require separate license fees. The VECTOR data type, VECTOR_DISTANCE functions, and HNSW/IVF indexing methods are all included in the base Enterprise Edition license.
However, there are nuances enterprise buyers must understand. First, AI Vector Search on Oracle Database 23ai running in Oracle Autonomous Database (shared or dedicated) is covered within the Autonomous Database service pricing — there is no separate vector search charge. Second, running AI Vector Search workloads on-premise requires Oracle Database 23ai on a supported platform, and the standard Processor or Named User Plus (NUP) metric applies to all processors or users accessing the database, not just those executing vector queries. Oracle's license metric does not distinguish by workload type.
Compliance trap: Enterprises that use AI Vector Search in a production Oracle Database 23ai instance must ensure all processors hosting the database instance are fully licenced — including development, test, and staging environments if those environments run production-equivalent features. Oracle's test and development license rules do not carve out AI Vector Search as an exception.
Third, Oracle's AI Vector Search documentation references the use of embedding models for generating vectors. If Oracle's own OCI Generative AI or OCI Data Science is used to generate embeddings, that triggers separate OCI service costs. If third-party models (Azure OpenAI, Hugging Face, etc.) are used, there is no additional Oracle license cost for the embedding generation itself — only the Oracle Database license for storing and querying the resulting vectors.
| AI Vector Search Scenario | License Status | Additional Cost? |
|---|---|---|
| VECTOR data type & HNSW indexing in Oracle DB EE 23ai on-premise | Included in EE license | No — existing EE metric applies |
| AI Vector Search in Oracle Autonomous Database (OCI) | Included in ADB service | No separate vector charge |
| AI Vector Search in Oracle DB 23ai via BYOL on OCI | Included in EE license | OCI compute/storage costs only |
| Vector search with OCI Generative AI embedding | DB: included in EE; OCI Gen AI: token-based pricing | Yes — OCI Generative AI usage charges |
| AI Vector Search in Standard Edition 2 (SE2) | SE2 does not support VECTOR data type | Upgrade to EE required |
The last row in the table above is significant: AI Vector Search is not available in Oracle Database Standard Edition 2. Enterprises on SE2 that want to implement vector search capabilities must either upgrade to Enterprise Edition or use a different vector database solution. Oracle's SE2 license terms restrict many advanced features — AI Vector Search follows this pattern.
JSON Relational Duality is one of the most architecturally significant features in Oracle Database 23ai. It allows application developers to interact with the same underlying relational data through both a relational SQL interface and a JSON document interface simultaneously — effectively presenting a unified data model to both traditional SQL applications and modern JSON-based applications without data duplication.
From a licensing perspective, JSON Relational Duality is included in Oracle Database Enterprise Edition 23ai at no additional cost. There is no separate "JSON Duality" option that requires a separate license fee. The feature is part of the core database engine.
The compliance consideration arises in two scenarios. First, enterprises using Oracle Database in a microservices architecture where individual services access the database via JSON Relational Duality views must still comply with the standard NUP minimums — if Named User Plus is the metric in use, each user or device accessing the database through a JSON Duality view counts against the NUP license pool. Oracle does not distinguish between "users accessing via JSON" and "users accessing via SQL" for metric counting purposes.
Second, Oracle's indirect access rules apply to JSON Relational Duality just as they apply to other Oracle Database access methods. If an application tier — whether a Java microservice, a Node.js API, or a Python FastAPI layer — queries Oracle Database through JSON Duality views, every unique end-user session or device that triggers those queries may be countable against the NUP metric. This has historically been a significant source of audit claims in architectures where Oracle Database is accessed through middleware layers that obscure the true user count from Oracle's LMS scripts.
Oracle True Cache is a new 23ai capability providing an in-memory, application-transparent read cache that sits between the application tier and the primary Oracle Database. Unlike Oracle's existing GoldenGate-based replication approaches or Active Data Guard read-replica patterns, True Cache uses Oracle's shared cache coherency protocol to maintain consistency automatically without application changes.
Oracle has confirmed that True Cache requires an Oracle Database Enterprise Edition license. The True Cache instance itself must be licenced using the standard Processor or NUP metric. This is a significant cost consideration: each True Cache node effectively requires its own Oracle Database Enterprise Edition license footprint, priced at the same per-processor rate as the primary database. For enterprises deploying True Cache for high-read workloads — typical in web-scale transaction systems — this creates a multiplicative license cost that Oracle's marketing materials do not emphasise.
Cost alert: If your 23ai architecture uses True Cache on a four-socket server with multi-core processors, each processor must be licenced at Oracle's standard Processor metric rate (adjusted for the Core Factor Table). For Intel Xeon processors, the Core Factor is 0.5 — meaning an 8-core Xeon requires 4 Processor licenses per socket. A four-socket True Cache node would require 16 Processor licenses at standard EE pricing.
True Cache should be evaluated against alternative caching approaches that may have lower overall license costs. Oracle Coherence provides distributed in-memory caching but is itself a separately licenced product. Redis-based caching architectures (on OCI or third-party) introduce a non-Oracle component but carry no additional Oracle Database license cost. The right-size decision requires forensic modelling of both the technical and commercial dimensions of each approach.
Our Oracle License Optimization service models the full license cost of 23ai deployment architectures before you commit to infrastructure. We have saved clients 30–40% by right-sizing feature adoption to licenced entitlements. Talk to a former Oracle insider before you build.
Oracle Database 23ai introduces Globally Distributed Database (GDD) as a built-in capability, superseding what was previously only achievable via Oracle Sharding in older releases. GDD enables enterprises to distribute Oracle Database workloads across multiple geographic regions with full SQL, ACID transactions, and strong consistency — a capability that was previously only available in competitive distributed SQL databases like CockroachDB or YugabyteDB.
The license model for Globally Distributed Database follows the standard Oracle Database EE Processor or NUP metric applied across all shards and coordinator nodes. Each node participating in a GDD configuration requires a full Oracle Database Enterprise Edition license. For a three-region, two-shard-per-region GDD deployment, enterprises need to license all six shard nodes plus any coordinator or proxy nodes — the license cost scales linearly with topology, not just user count or data volume.
Oracle's GDD licensing does not include a separate "Globally Distributed Database" option surcharge — it is included within Oracle Database EE. However, the infrastructure implications are substantial. Enterprises evaluating GDD against competing distributed SQL solutions must model the full Oracle Database EE license cost for the entire cluster footprint, which typically adds significant annual support costs at 22% of net license value per year across all nodes.
Our Oracle Cloud Advisory team has conducted several GDD vs. competing distributed SQL cost comparisons for enterprises considering this architecture. In most cases, the Oracle Database EE license cost across all GDD nodes significantly exceeded the all-in infrastructure and software cost of CockroachDB or YugabyteDB for equivalent workloads — a factor Oracle's account teams consistently underemphasise.
Oracle has introduced several new separately licenced options in the 23ai release cycle that extend database capabilities beyond what is included in the base Enterprise Edition. Understanding which of these are enabled — intentionally or accidentally — in your environment is essential before Oracle's LMS team arrives.
| Feature / Option | License Status in 23ai | Audit Risk Level |
|---|---|---|
| AI Vector Search | Included in Enterprise Edition | Low (if on EE) |
| JSON Relational Duality | Included in Enterprise Edition | Medium (indirect access NUP) |
| True Cache | Requires EE license on each cache node | High (node count) |
| Globally Distributed Database | Included in EE; all shard nodes need EE | High (node count) |
| Blockchain Tables (enhanced in 23ai) | Included in Enterprise Edition | Low |
| Advanced Security Option (ASO) | Separate option — always licenced separately | High (frequently accidentally enabled) |
| Diagnostics Pack | Separate option — still applies in 23ai | Very High (default-enabled metrics) |
| Tuning Pack | Separate option — still applies in 23ai | High (SQL Tuning Advisor) |
| Partitioning | Separate option — still applies in 23ai | High (widely adopted) |
| Multitenant (>1 PDB) | Requires EE or specific metric — see below | High (common CDB/PDB confusion) |
The Diagnostics and Tuning Pack compliance risk is particularly acute in 23ai environments. These packs are controlled by the CONTROL_MANAGEMENT_PACK_ACCESS parameter. In 23ai, Oracle has made several performance monitoring and SQL diagnostic capabilities more prominent in the user interface, increasing the likelihood that database administrators activate these packs inadvertently. Our Oracle Diagnostics Pack guide explains the parameter settings and monitoring queries needed to verify you are not consuming these options without a license.
Multitenant licensing in 23ai follows the rule established post-Oracle Database 21c: from Oracle Database 21c onward, the "one free PDB" rule no longer applies. All PDB usage beyond a single user PDB in a CDB requires Enterprise Edition licensing. In Oracle Database 23ai, Oracle has simplified some multitenant management capabilities, but the fundamental license obligation remains: if you are running multiple PDBs in a production CDB without Enterprise Edition multitenant licenses, you are non-compliant.
Oracle Database 19c enters End of Extended Support in April 2027, making 23ai the natural migration target for enterprises on the 19c LTS release. Oracle is actively promoting 23ai upgrades — and Oracle's LMS team historically uses upgrade periods as trigger events for compliance reviews. Understanding the license implications of migration before initiating the upgrade is essential.
The upgrade itself does not require new licenses if you are moving from an existing Oracle Database EE or SE2 license. Your existing Oracle Master Agreement and associated license order forms already cover the 23ai version. However, the upgrade process frequently reveals compliance gaps that existed before the migration — gaps that become harder to argue away once the upgrade is complete and Oracle can see your deployment in 23ai's enhanced diagnostic tools.
There are three specific pre-migration activities we recommend enterprises undertake before upgrading to 23ai. First, run an internal license position assessment using Oracle's USMM (Usage Measurement for Management) or equivalent tooling to establish a baseline of current option usage. Second, review all Diagnostics Pack and Tuning Pack parameter settings and disable any packs not covered by your licenses before the upgrade. Third, assess whether any new 23ai features you plan to adopt — particularly True Cache or GDD — require licensing beyond your current entitlements, and negotiate those license additions as part of your broader Oracle contract strategy rather than after deployment.
Our Oracle Audit Defense team has guided dozens of enterprises through 23ai migration licensing reviews. In a significant proportion of cases, we identified pre-existing compliance gaps during migration preparation that, had they been discovered by Oracle's LMS team post-upgrade, would have resulted in seven-figure back-license claims.
Oracle Database 23ai's AI positioning creates new commercial traps that enterprises evaluating the platform need to understand. Based on our advisory experience, the following represent the highest-risk compliance scenarios in 23ai deployments.
Trap 1: Enabling AI Vector Search on SE2. If your team enables AI Vector Search features on a Standard Edition 2 database believing these are "just features," they will likely fail — SE2 does not support the VECTOR data type. However, the attempt to enable them may create confusion about license scope, and if SE2 is subsequently upgraded to EE to support vector search without updating Oracle license order forms, this creates an unlicenced EE deployment.
Trap 2: True Cache node licensing omissions. Development and proof-of-concept True Cache deployments are frequently built on unlicenced infrastructure. Once promoted to production without a license review, these deployments become audit exposure. Oracle's LMS scripts can identify True Cache instances in the AWR and Oracle inventory tables.
Trap 3: GDD coordinator nodes as "infrastructure." Enterprises sometimes attempt to classify GDD coordinator nodes as "infrastructure" rather than licenced Oracle Database instances. Oracle does not accept this argument — all nodes participating in a GDD topology require full Enterprise Edition licenses per Oracle's Database Licensing Guide.
Trap 4: Diagnostics Pack enablement by default in 23ai tooling. Oracle's new 23ai Performance Hub and Database Advisor integrations make it easier than ever to access performance diagnostic data — but accessing this data in a production environment may constitute use of the Diagnostics Pack even if the access is through a new 23ai-native interface. Our Oracle Compliance Review specifically tests for this scenario.
Trap 5: Autonomous Database feature overlap. Enterprises using Oracle Autonomous Database on OCI that also maintain on-premise 23ai deployments may inadvertently believe their ADB subscription covers on-premise 23ai feature usage. It does not. ADB subscription licenses are cloud-specific and do not substitute for on-premise Oracle Database EE licenses.
23ai licensing updates, LMS audit intelligence, and negotiation tactics — delivered weekly to Oracle stakeholders at 2,000+ enterprises.
No spam. Unsubscribe any time.
Before you upgrade, know your license position. A pre-migration compliance review protects you from back-license claims and ensures your 23ai architecture is fully covered. Not affiliated with Oracle Corporation.