By An Oracle APEX 26.2 upgrade starts with the platform versions, the features your environment can use, and the application behavior you need to preserve. For teams already on 26.1, the ORDS and SQLcl requirements deserve attention before planning new functionality.
This guide is based on Oracle documentation checked on October 12, 2026. The checks below are a proposed validation plan; no runtime upgrade, performance benchmark, or application-specific compatibility test was performed for this article.
1 Check the Oracle APEX 26.2 upgrade requirements
Record exact versions, including the database release update and installed APEX patches. Use this comparison for the Oracle APEX 26.2 upgrade conversation with your administrator.
| Component | APEX 26.1 | APEX 26.2 |
|---|---|---|
| Oracle Database 19c | RU 19.18 or later | RU 19.18 or later |
| Oracle AI Database 26ai | Version 23.26.0 or later | Version 23.26.0 or later |
| ORDS | 26.1.1 or later | 26.3.0 or later |
| SQLcl | No general minimum stated on the prerequisite page reviewed | 26.3.0 or later |
| Supported Universal Theme | 26.1 and 24.2 | 26.2 and 26.1 |
Sources: 26.1 prerequisites; 26.2 prerequisites
For self-managed installations, also verify memory, tablespace capacity, XML DB, and the installation procedure. Oracle specifies at least 1,200 MB SGA and 300 MB PGA. These are installation minimums, not a capacity estimate for your workload. Installation requirements
2 Confirm availability on your server
Oracle announced 26.2 on October 6, 2026, with immediate on-premises availability and OCI and multi-cloud rollout to follow. Check the version displayed by your own environment and the provider’s upgrade options. The launch date alone does not establish that a particular hosted instance has received the release. Oracle announcement
3 Check feature eligibility separately
The general database floor remains compatible with 19c. Deep Data Security has a separate requirement: Oracle AI Database 23.26.3 or later, plus Social Sign In using OCI IAM or Microsoft Entra. Identity-provider configuration, database identities, data roles, and grants must also be prepared. A successful APEX installation does not establish that this integration is ready. Deep Data Security prerequisites
4 Review changes that affect your workflow
APEXlang file-level import helps development teams update selected files through SQLcl or SQL Developer for VS Code. The target application must already exist. App Builder does not support this route, and themes, templates, plug-ins, and workspace components are excluded. Keep full-application imports in the production deployment process. Compare local files with server changes before importing. File-level import guidance
If Git holds your canonical APEXlang source, plan an import and re-export after upgrading. Keep that structural update in its own reviewed commit. Back up uncommitted files and current server changes first: SQLcl export with -force deletes and recreates the app-alias directory. Protect uncommitted and non-export files, and keep the Git root at least one directory above it. APEXlang source upgrade
Existing AI services also need inspection. During an upgrade or legacy application import, OpenAI services can move to the Responses API and Google Gemini services to the Interactions API when custom Additional Attributes and HTTP Headers are absent. Test the configured endpoint, model, tool calls, and output. Reasoning Effort support varies by provider, API, and model, so compare representative results before increasing it. Provider API and reasoning guidance
5 Run the Oracle APEX 26.2 upgrade checklist
- Capture the baseline. Record source and target versions, application IDs, parsing schemas, Compatibility Mode, theme, plug-ins, and integrations. Preserve the original export and the platform configuration needed for recovery.
- Rehearse the deployment. Upgrade development and QA before production. Import the intended artifact into an isolated target, review dependencies and logs, and keep the exact revision used for testing.
- Repeat business transactions. Use the same test users and inputs before and after. Check login, denied access, form saves, validation, report filters, exports, and controlled integration calls. Record expected and actual results.
- Exercise changed components. Retest custom JavaScript and CSS, hidden charts, region refreshes, saved reports, and workflows you use. For new AI or security features, use synthetic data and include failed requests or denied actions.
- Rehearse recovery. Name the owner, recovery trigger, protected data, and expected interruption. Keep application definitions, business-data recovery, and platform recovery in the plan. Agree how integrations and scheduled work will resume.
Changing Compatibility Mode deserves explicit regression testing. For the release-specific procedure and application test guidance, consult Oracle’s documentation. Upgrade guidance
Short answers before production
Can I upgrade while staying on 19c?
Yes, when the documented database and toolchain requirements are met. Features with additional prerequisites still need a separate eligibility check.
Does a clean import prove compatibility?
No. It does not exercise application authorization, transactions, custom code, integrations, or recovery. Keep those results visible in the release record.
Should I refresh Universal Theme immediately?
Plan the refresh and test your customizations. Oracle supports the current and previous theme versions for this release; record which version your application actually uses.
Before approving your Oracle APEX 26.2 upgrade for production, review the current known issues and unresolved test failures. For work targeting the earlier release, use the separate 26.1 checklist. Oracle 26.2 known issues; Oracle APEX 26.1 upgrade checklist
