What changed
Starting with Oracle APEX 26.1, Oracle REST Data Services must be version 26.1.1 or later. Oracle states this in the APEX 26.1 release notes and in the installation requirements.
This is a version-alignment change, not a loss of capability. Before 26.1, APEX and ORDS were more loosely coupled. For example, APEX 24.2 supported ORDS 23.3 or later, and earlier APEX releases such as 24.1 and 23.x allowed ORDS versions as far back as the 20.x line.
With APEX 26.1, the versions move closer together because APEXlang depends on compiler logic in ORDS and SQLcl. As Oracle enhances APEXlang, those compiler layers need to advance with the APEX release they support.
Before and after
| Planning question | Before APEX 26.1 | Starting with APEX 26.1 |
|---|---|---|
| Can ORDS lag behind APEX? | Often, within documented limits | ORDS must be 26.1.1 or later |
| Is ORDS only a web gateway? | Commonly treated that way | It is also part of the version-sensitive tooling path |
| Should SQLcl be included in planning? | Useful, but sometimes separate | Yes, especially when APEXlang or automation is involved |
| Main operational takeaway | Check compatibility | Plan and validate APEX, ORDS and SQLcl together |
Expect this tighter coupling to continue with the next APEX release later this year. The safest planning model is to treat APEX, ORDS and SQLcl as one tested upgrade set.
Why APEXlang matters
APEXlang changes the relationship between the APEX runtime and the surrounding tooling. The compiler logic that understands APEXlang lives in ORDS and SQLcl. That means ORDS and SQLcl need to understand the APEX release they are serving.
For teams, the operational message is straightforward: do not upgrade APEX in isolation. Test the APEX runtime, ORDS deployment and SQLcl automation together before the production window.
What to track together
For self-managed environments, keep these components in the same upgrade plan:
- Oracle APEX
- ORDS
- SQLcl
- Java runtime used by ORDS
- Database release and release update level
- Front-end proxy configuration, such as Apache or a load balancer
The APEX 26.1 database requirement remains important too: Oracle Database 19c with Release Update 19.18 or newer, or Oracle AI Database 26ai at the documented minimum version.
A practical runbook
1. Build a compatibility matrix
Keep a small table in the upgrade runbook so ownership and validation are clear.
| Component | Current | Target | Owner | Validation |
|---|---|---|---|---|
| APEX | 24.2 or earlier | 26.1 | Database/APEX admin | App smoke tests |
| ORDS | Existing production version | 26.1.1 or later | Platform admin | HTTP, REST, APEX login |
| SQLcl | Existing automation version | Version aligned with APEX work | Release engineer | Export/import, APEXlang tasks |
| Java | Current supported runtime | ORDS-supported runtime | Platform admin | ORDS startup and logs |
2. Make staging match production
Staging should use the same ORDS deployment shape as production: reverse proxy pattern, TLS assumptions, connection pool style and SQLcl automation path.
3. Test APEXlang and SQLcl paths explicitly
If your team uses APEXlang or SQLcl automation, test those paths directly:
- Generate or compile the artifacts you normally generate.
- Run SQLcl automation used in CI or release work.
- Validate application pages touched by generated changes.
- Check ORDS logs for compiler or compatibility messages.
4. Keep plain rollback notes
Record the previous ORDS configuration, deployed ORDS artifact, APEX backup or export posture, proxy configuration, service files and SQLcl scripts used during the upgrade. The goal is a clear recovery path for the full platform set.
What this means for managed hosting
For managed Oracle APEX hosting, version alignment should be handled as part of the platform operation. Application teams should not need to manage the details of which ORDS and SQLcl versions are approved for a given APEX release.
For nwavecloud customers, this is the kind of coordination we treat as hosting work: track supported versions, validate platform changes in staging, communicate maintenance windows and keep the hosted APEX stack consistent. The Cloud Hosting overview explains the platform model, and the plans page shows available hosting options.
FAQ
Does APEX 26.1 require ORDS 26.1.1?
Yes. Oracle’s APEX 26.1 release notes and installation requirements state that Oracle APEX 26.1 requires ORDS 26.1.1 or later.
Why does APEXlang affect ORDS planning?
APEXlang compiler support lives in ORDS and SQLcl. As Oracle enhances APEXlang, those compiler layers need to stay aligned with the APEX release they support.
Should SQLcl be part of the same upgrade plan?
Yes. If SQLcl is used for APEX exports, imports, release automation or APEXlang workflows, test it with the target APEX and ORDS versions before production.
Can APEX be upgraded without changing Apache or the front-end proxy?
Sometimes the proxy configuration may not need changes, but it should still be tested. ORDS often sits behind Apache or another proxy, so login, REST endpoints, redirects, TLS behavior and static assets should be verified after the ORDS change.
Where should teams start?
Start with the official Oracle APEX 26.1 release notes, the APEX installation requirements, your current ORDS and SQLcl versions and a staging environment that resembles production.