Will upgrading to Oracle Database 23ai be Worth It?

The arrival of Oracle Database 23ai promises exciting new features and capabilities. However, with most organizations still standardizing on Oracle Database 19c and extending the lifespan of their current databases, the upgrade may not be worth the hype.

Navigating the decision to upgrade requires careful evaluation of the trade-offs and associated business impact. Consider if there is a genuine need for you to upgrade, will the new features justify the costs and the complexity of the upgrade process.

Will upgrading to Oracle Database 23ai be Worth It?
arrows pointing to the top right corner
arrows pointing to the top right corner
01

Timing and Upgrade Paths

Timelines are Uncertain

Oracle Database 23ai, or Oracle Database 23.4 has made its debut within Oracle Cloud Infrastructure (OCI) and some select environments for developers. However, the rollout for its integration into mainstream on-premises versions is still somewhat uncertain.1

This uncertainty has left organizations, especially those dependent on Linux and Windows, wondering when 23ai will be available in their production environments. Without solid release dates, the ambiguity has led business and technical teams wondering if they should wait to archive or explore alternative paths for support.

Drawing from past releases and trends, on-premises versions tend to trail behind OCI by a few months. With this in mind, we estimate the following release dates:

Platform
Estimated Release Date
Oracle Database Oracle Database 23ai accessible via Oracle OCI :

• Exadata Database Service
• Oracle Exadata Cloud@Customer
• Oracle Base Database Service
• Oracle Exadata Cloud@Customer
• Oracle Base Database Service
• Always Free Autonomous Database

Released1
Oracle Database Oracle Database 23ai accessible via Azure Oracle Database Service
Released1
Oracle Database Oracle Database 23ai downloadable on premise as:

• Autonomous Database Oracle Database 23ai Container Image
• Oracle Database Oracle Database 23ai Free

Released1
On Premise Exadata, Linux and Windows
Estimated to release 6/2024 – 9/2024

Even if you have Oracle Database 23ai in your archive now, it’s essential to remember that achieving a stable release typically takes time, often at least two years. This means even if its accessible now, the version you’ve archived may not be stable.

Your Path to Oracle Database 23ai

If you’re upgrading from versions older than Oracle Database 19c, you’ll likely hit two hurdles:

  • Upgrade Paths. Oracle Database 23c only allows direct upgrades from versions Oracle Database 19c and 21c.2 Users with older versions need to perform at least one extra upgrade, which will take time, effort, testing, downtime and risk. This multi-upgrade requirement can add even more significant time (and downtime), effort, and risk.
  • Removal of the Classic Oracle Architecture. Oracle Database 23c no longer supports the classic non-CDB architecture, requiring adoption CDB/PDB model introduced in 12.2. There is a significant amount of time and work to be done to convert existing non-CDB databases to use the CDB/PDB model.3

Upgrading needs to be a strategic decision – does the promise of these new capabilities really outweigh the potential business disruption, costs, benefits, time and risk?

arrows pointing to the top right corner
02

Environment Stability

The Foundation Could be Rocky

New releases of any software inherently carry some instability. To gauge stability of this most recent release, let’s look at adoption patterns of previous versions:

Early versions of Oracle Database, from Oracle 8 to 18, have encountered their fair share of challenges. Accessibility issues plagued Oracle 84, while memory management complexities surfaced in Oracle 11g and 12c, serving as reminders of the hurdles that can accompany new releases.5

We have witnessed healthy adoption with versions such as Oracle 11.2, 12.2, and Oracle Database 19c. The commonality being that each were final iterations of the long-term support releases, affording ample time for optimization.

Prioritizing stability and reliability are critical. By assessing historical patterns, we’ll likely see resolution of early bugs and the establishment of a more mature ecosystem in two to three years.

23.5 Potential Increased Chance of Instability

Although it could be earlier, we’re estimating that the next version of Oracle Database 23 will debut a year following the initial release of Oracle Database 23.4, with the earliest on-premises version expected in mid-2025.

With the addition of substantial new features, it’s crucial to acknowledge the potential for added instability within the release. Should version 23.5 introduce further enhancements, we should anticipate an impact to the base version as a result of the additional new code required.

Estimated Release Schedule for 23.5

Platform Estimated Release Date
OCI Exadata Database Service and Oracle Exadata Cloud@Customer 1/2025
OCI Other DBaaS 2025
On Premise Exadata 2/2025 – 6/2025
On Premise Linux 2/2025-6/2025
On Premise Windows 3/2025-7/2025
arrows pointing to the top right corner
03

Capabilities and Business Impact

Your Organization’s Needs Should Dictate the Decision to Upgrade

The core functionality of 23c will remain fairly consistent with Oracle Database 19c, however, it will introduce new AI centric feature changes and additions, such as AI vector search, secure encoding of data and natural language processing.

With these new features, we’ll also see capabilities removed entirely. For example, the ability to create Oracle Databases in the classic style was depreciated in 12c and completely removed in 21c. This change alone may well impact your ability to easily upgrade.6

Take the time to assess whether these new features genuinely align with your business objectives and if they’ll deliver tangible benefits.

Partial List of New Features

Performance Optimization and Efficiency Data Modelling and Management Developer Productivity and Flexibility Security and Compliance Advanced Analytics and Search
• Priority transactions
• Priority graphs
• Shrink table space
• True Cache
• Rolling patching
• Real-time SQL plan management
• JSON Schema
• JSON / Relational Duality
• Globally Distributed Databases
• SQL Domains
• Boolean Datatype
• Schema Level Privileges
• SQL Firewall
• Read-only per PDB Standby
• JS Stored Procedures
• Developer role
• Microservice support
• AI vector search
arrows pointing to the top right corner
04

The Cost of Upgrading

The Cost of Upgrading is Not Insignificant

As you explore Oracle Database 23ai, it’s essential to consider the potential costs associated with upgrading.

Upgrading requires time, effort, retraining and quality assurance, all of which have associated costs. If there is a need for your organization to adopt Oracle Database 23ai in a limited capacity, it is possible to negotiate for the use of OCI as a DBaaS solution while still maintaining your support with Rimini Street.7 You may also be able to access Oracle Database 23ai through runtime/embedded licenses or your system integrator.

It’s important for you to anticipate potential costs and licensing adjustments when upgrading to Oracle Database 23ai. If you’re worried about falling behind, don’t be – Oracle typically provides development licensed versions of all databases so you can run them on your personal computers (with your organization’s consent).

The Need to Upgrade is Minimal

In our opinion, the current version of your Oracle Database likely serves your needs well. It’s essential to keep clear-sighted with all the industry buzz and consider the following:

Evaluate your Upgrade Paths. You invested a significant amount of resource of people, time and money to get to your current stable implementation. Transitioning to Oracle Database 23ai could potentially take two to three years, pending the project is successful, especially if you’re navigating a complex multi-upgrade path.

Prioritize System Stability. While Oracle Database 23ai has many new and enhanced features, it’s natural to be cautious about its initial stability. Your business relies on a stable database, and it would be wise to prioritize this over immediate access to the latest features.

Surface the Hidden Costs. Your decision to upgrade should align with your business need. Take the time to contemplate your specific use cases and the potential business impact, as well as the time and resources needed to drive value.

We’re dedicated to empowering you to make informed decisions. While new AI features hold significant potential, timing is crucial. Ensure your resources are directed towards initiatives that not only deliver tangible business value but also minimize disruption and foster innovation. It’s essential to strike a balance that drives progress without compromising stability. Learn more about Rimini Street Support to see how you can optimize your existing Oracle investments, while ensuring your AI investments are thoughtfully adopted, ensuring minimal disruption to your current operations.