Oracle Database 19c vs 23ai: Support, Features and Licensing Compared
Oracle Database 19c and 23ai are both current, both Long Term Releases, and both have support windows running past 2029. Neither is being retired soon, which is exactly why "which one are we on, and does it matter" is a live question in most estates rather than a settled one. The short answer: the core licensing model has not changed between them. What changed is what a licence now includes, and how long each release stays supported.
This is the comparison: support timelines, what moved into the base licence at no extra cost, and what a position built on one release needs to check when the estate runs both.
Support timelines
| 19c | 23ai | |
|---|---|---|
| Release type | Long Term Release | Long Term Release |
| Premier Support | Through December 31, 2029 | Through December 31, 2031 |
| Extended Support | Through December 31, 2032 | Not yet announced |
Oracle extended 19c's support twice: Premier Support, originally set to end years earlier, now runs to the end of 2029, with Extended Support carrying it to the end of 2032. That is a long runway for a release most estates already have in production, and it removes the forced-migration urgency that an earlier support timeline would have created. 23ai, as the newer Long Term Release, follows the same shape: roughly five years of Premier Support plus Extended Support behind it, on its own later clock.
Neither date is a reason to migrate on its own. A 19c estate with a stable workload and no feature gap has years of supported runway left; the decision to move to 23ai is a features-and-operations question, not a support-clock one.
What moved into the base licence
- AI Vector Search ships in Enterprise Edition at no additional licence cost in 23ai. There is no separate option to buy or to accidentally trip a usage flag on; it is part of the base product.
- Spatial and Graph moved into the Enterprise Edition base in 23ai. On 19c, Spatial and Graph functionality sits behind separate licensable options; an estate that touches either on a 19c database is a genuine option-usage finding in an audit report, the kind a script flags the moment it is touched. On 23ai, the same functionality carries no separate licence exposure.
Neither change alters the core mechanics of the licence: the core factor table still applies the same way to the same processor families, Standard Edition 2's socket ceiling is unchanged, and the partitioning policy still decides whether a virtualized deployment counts one VM or the whole cluster, on 19c and 23ai alike. What moved is which features carry a separate cost, not how the database itself is counted.
What this means for a mixed estate
- Re-check option usage per database, per version. A 19c database using Spatial is an option finding; the same feature on a 23ai database, migrated without re-checking the position, might be recorded as an exposure it no longer is. The position has to know which release each database runs, not assume the whole estate matches the newest one.
- Do not budget for AI Vector Search as an option. On 23ai it is base Enterprise Edition. A procurement conversation that prices it separately is pricing something Oracle already includes.
- Track support dates per release, not per estate. A mixed 19c-and-23ai estate has two Premier Support clocks running, and treating the earlier of the two as the whole estate's deadline either forces an unnecessary migration or misses the one that actually matters.
- Migration itself does not change the licence metric. A move from 19c to 23ai is a version upgrade under the same licence agreement, not a re-entitlement; what it changes is which options are included and which support clock applies.
None of this is visible from a version number alone. An Effective License Position built across a mixed estate has to carry the release of every database, not just its edition and core count, so an option that is free on one and licensable on another is priced correctly rather than averaged across the estate. Oracle Database Manager reads the version alongside the edition, the host, and the options actually touched, so a 19c Spatial finding and a 23ai one that costs nothing are never confused with each other.
Checklist
- Release version recorded per database, not assumed from the newest one in the estate.
- Spatial and Graph usage checked against the release: an option on 19c, base Enterprise Edition on 23ai.
- AI Vector Search never priced as a separate option.
- Premier and Extended Support dates tracked per release in a mixed estate, not by the earliest deadline alone.
