Oracle Database 19c Third-Party Support: Premier Support Ended April 2024 — Here Is Your Alternative

Oracle Database 19c is the most widely deployed Oracle Database version in the enterprise. Introduced as Oracle's designated long-term release (LTR), Database 19c was positioned by Oracle as the stable, multi-year platform for EBS, PeopleSoft, JD Edwards, and standalone database workloads. Oracle's Premier Support for Database 19c ended in April 2024. As of this writing, Database 19c is in Sustaining Engineering — Oracle's support tier that provides fixes for catastrophic issues only, with no new security patches, no new fix releases, and no obligation to address known vulnerabilities.

Oracle's account teams are using Database 19c Sustaining Engineering status to drive two commercial objectives simultaneously: Database 23ai subscription (Oracle's latest cloud-first offering) and Oracle Cloud Infrastructure (OCI) migration. Neither is a technical necessity for enterprises that have operated stable, high-performance Oracle 19c environments for the past five years. Third-party support breaks this pressure cycle: Oracle Database 19c continues under full supported cover at 62–65% less than Oracle's Software Update Licence & Support (SULS) fees.

Oracle's 23ai Upgrade Push — What It Actually Involves

Oracle has positioned Database 23ai as the successor to Database 19c, with AI Vector Search and other "AI-native" features marketed as compelling reasons to upgrade immediately. What Oracle does not advertise: the upgrade path from Database 19c to 23ai on on-premise infrastructure requires a major version upgrade with full application compatibility testing, any custom code dependent on Oracle-internal packages requires re-certification, and in cloud deployments (Exadata Cloud Service, Base Database Service), Oracle 23ai is subscription-only.

For enterprises running Oracle Database 19c as the backend for Oracle EBS, PeopleSoft, JD Edwards, or SAP, the upgrade to 23ai requires explicit application certification from the respective application vendor. SAP does not certify Oracle 23ai for SAP production systems as of Q1 2026. Oracle EBS certifications lag major Database releases by 12–18 months. For these customers, the "upgrade to 23ai" path is not commercially or technically available in the short term regardless of the support deadline pressure — which makes third-party support the only rational response to Premier Support end.

Oracle Database Version Matrix — TPS Eligibility

What TPS Covers for Oracle Database 19c

Oracle Database 19c TPS covers the complete database stack — core RDBMS, options, and infrastructure layers:

Oracle Database Engine — Core Coverage

• Instance management — startup, shutdown, parameter file (SPFILE/PFILE), memory configuration
• SQL and PL/SQL defect analysis — query plan regression, performance degradation, optimizer statistics issues
• Backup and Recovery — RMAN configuration, backup strategy review, point-in-time recovery testing
• Tablespace management, datafile extension, undo/redo configuration
• Security patching advisory — CVE analysis and risk assessment where Oracle patches are not available
• Oracle Multitenant (CDB/PDB architecture) — container database and pluggable database management

Oracle RAC (Real Application Clusters)

• Cluster configuration, node eviction analysis, OCR/Voting disk management
• Oracle Clusterware (Grid Infrastructure) — CRS configuration, SCAN listener, VIP management
• Cache Fusion and interconnect performance analysis
• RAC-specific backup strategy — RMAN with RAC, archivelog management across nodes
• Workload management — services, instance-level affinity, connection load balancing

Oracle Data Guard

• Primary/standby configuration — physical standby, logical standby, Active Data Guard
• Redo transport troubleshooting — synchronous and asynchronous redo shipping
• Switchover and failover procedure support and testing
• Data Guard Broker configuration and monitoring

Oracle Database Options

• Oracle Partitioning — partition-level operations, partition pruning performance, interval and reference partitioning
• Oracle Advanced Compression — OLTP table compression, archive compression
• Oracle Spatial and Graph — where deployed as part of the application stack
• Oracle Advanced Security — TDE (Transparent Data Encryption), VPD, Oracle Label Security
• Oracle Diagnostics and Tuning packs (AWR, ADDM, ASH) — analysis support

The Extended Support Premium — Why TPS Is Better Value

Oracle offers Extended Support for Database 19c through April 2027, at a price premium above standard SULS. Oracle's Extended Support pricing for Database 19c adds a surcharge of approximately 10–20% above the standard SULS rate in years 1–2 of Extended Support, escalating to 20–30% in year 3. For a customer paying £480,000/year in Oracle DB 19c SULS, Extended Support would cost approximately £528,000–£624,000/year — before Oracle's annual price increase escalation (typically 4–8% per year under current Oracle pricing).

Third-party support at the equivalent coverage level costs approximately £168,000–£173,000/year — a saving of £355,000–£451,000 annually versus Extended Support pricing, and a saving of £307,000–£312,000 annually versus standard SULS. The TPS contract is fixed-price with no annual escalation clause. Extended Support is not a better deal than TPS for any Oracle Database 19c customer with more than £250,000/year in SULS spend.

Oracle LMS Risk After DB 19c Support Cancellation

One of the most frequently cited concerns about Oracle Database TPS is the risk of an Oracle LMS (Licence Management Services) audit following support cancellation. This concern deserves direct treatment:

Oracle cannot initiate a compliance audit as retaliation for a support cancellation decision. Oracle LMS audits are triggered by different commercial mechanisms — typically, an Oracle account team requesting an LMS engagement when they perceive a large compliance gap that Oracle can monetise. The risk is not higher post-TPS; it is a pre-existing risk that applies equally to Oracle support customers.

The practical LMS risk for Database 19c customers is the Oracle Database processor metric. In virtualised environments (VMware, Hyper-V, KVM), Oracle's default position is that all physical processors in the server are licensable unless specific Oracle-approved hard partitioning technology is used. TPS providers assist with Oracle LMS audit preparation and defence as a standard TPS service. The Oracle Audit Defence Playbook provides comprehensive guidance on LMS risk management for TPS customers.

Oracle Database 19c — Sector-Specific TPS Considerations

Banking and Financial Services

The largest concentration of Oracle Database 19c RAC deployments is in financial services — tier 1 and tier 2 banks, insurance carriers, and capital markets firms. Oracle RAC on SPARC/T-Series servers and x86 Exadata is the high-availability database platform for core banking, payments, and risk management systems. DORA Article 9 ICT risk management requirements are satisfied by TPS engagements with documented SLAs and tested incident response. The financial services TPS page provides the full regulatory framework analysis.

Healthcare and Life Sciences

Oracle Database 19c underpins a significant proportion of NHS Electronic Patient Record (EPR) systems and hospital information systems — Cerner (now Oracle Health), Epic, and various NHS-specific systems. GxP-validated pharmaceutical systems (including systems covered in the pharma SAP + Oracle case study) typically run Oracle Database 19c as the underlying RDBMS. TPS for Oracle Database does not affect GxP validation status — the software is unchanged.

Oracle EBS, PeopleSoft, and JD Edwards Customers

Oracle application customers — EBS, PeopleSoft, JD Edwards — almost universally run Oracle Database 19c as the backend RDBMS. These customers can consolidate both the application-layer TPS and the Database-layer TPS into a single engagement, providing a unified support envelope and a single point of contact for all Oracle-related incidents.

Four-Profile Cost Model — Oracle Database 19c TPS Saving

Moving Oracle Database 19c to Third-Party Support

1. Database estate inventory — Document all Oracle Database instances: version, edition (EE/SE2), options, processor count, and virtualisation technology. This inventory is critical for both TPS scoping and ongoing LMS risk management.
2. Application dependency mapping — Identify all applications connecting to Oracle DB 19c instances (EBS, PeopleSoft, SAP, custom apps). Confirm that application-tier TPS is aligned or separately addressed.
3. Oracle SULS cancellation — 30-day written notice to Oracle. Oracle will attempt to negotiate retention. The cancellation right is unambiguous under standard Oracle licence terms.
4. TPS onboarding — TPS provider performs database environment discovery, installs monitoring, establishes AWR/ASH performance baselines. Typically 10–15 working days for a standard DB estate.
5. LMS documentation — Confirm licence documentation (CSI, NUP/Processor certificates) is on file. TPS provider assists with Oracle LMS audit preparation and licence position documentation.

See the Oracle Support Cost Reduction white paper for complete Oracle SULS cancellation mechanics, Extended Support comparison, and Oracle LMS risk management guidance.

Frequently Asked Questions

Is Oracle Database 19c still a valid platform for production workloads?

Absolutely. Oracle Database 19c is technically mature, highly stable, and fully capable of supporting enterprise production workloads for a further 7–10 years. The EOS date is an Oracle commercial decision, not a reflection of the software's technical capability. Many of the world's most demanding transactional systems run on Oracle Database 19c today.

What does TPS do about new Oracle security vulnerabilities?

TPS providers maintain a security advisory service that analyses Oracle Critical Patch Update (CPU) advisories and determines risk exposure for each customer's specific configuration. Where Oracle patches are not available (Sustaining Engineering), TPS provides compensating control recommendations. This is materially better than Oracle's own Sustaining Engineering tier, which does not proactively address known CVEs.

Can TPS support Oracle Exadata?

Database software TPS covers the Oracle Database software layer running on Exadata. Exadata hardware and storage server software require separate hardware maintenance arrangements. Most large TPS engagements for Exadata deployments combine database software TPS with Exadata hardware maintenance from an independent Exadata hardware specialist.

What if Oracle releases a security patch for DB 19c that TPS can't provide?

Under Sustaining Engineering, Oracle does not release scheduled quarterly patches for Database 19c. Oracle provides fixes only for catastrophic issues — defined by Oracle as issues affecting the majority of customers with no workaround. TPS providers monitor Oracle's security advisories and provide risk assessments and compensating controls for all publicly disclosed CVEs. In practice, the security advisory coverage provided by TPS is superior to Oracle Sustaining Engineering for the vast majority of vulnerabilities.