By The Oracle APEX 26.2 import issue tracked as bug 40091133 affects workflows that import application.apx on its own. Check the documented behavior before your next deployment. Oracle reports that this operation unexpectedly changes the application alias and removes the application’s current theme. The documented recovery is a full APEXlang import. Oracle known issues.
Oracle released APEX 26.2 on October 6, 2026, and re-released its download files on October 9. As checked on October 12, the downloads notice does not say that the re-release fixes this issue, and the bug remains on the known-issues page. Treat the download date and the bug’s resolution status as separate checks. Oracle downloads.
Understand the Oracle APEX 26.2 import issue
Record the actual import command or selected file when investigating a change. Match it against the operation identified in Oracle’s notice before choosing a recovery path.
File-level APEXlang import is new in 26.2. It is available through Oracle SQL Developer for VS Code and SQLcl, rather than App Builder. Oracle’s release notes limit this option to development environments and direct production deployments to use a full application import. APEX 26.2 release notes.
The target application must already exist for file-level import. Oracle also excludes themes, templates, plug-ins, and workspace components from this import mode. Those boundaries matter when deciding whether a selected file contains everything your change needs. Oracle file-level import guide.
Prepare before importing
For a development rehearsal, record the target workspace, application ID, alias, current theme, source revision, and import method. Keep the complete intended APEXlang source available, and preserve current server-side changes before replacing anything.
Review the deployment configuration alongside the source. APEX 26.2 deployment files can supply environment-specific values, including application and workspace settings. Check the selected deployment file and any explicit overrides so the recovery goes to the intended application. Oracle deployment-file documentation.
If colleagues also edit the application in App Builder, compare their current changes with your local source before importing. Oracle describes a compare-and-pull workflow in SQL Developer for VS Code 26.3 and later. Resolve differences before choosing the revision to deploy. Oracle file-level import guide.
Recover with the complete application
If the alias or current theme changes after deploying application.apx alone, first preserve the import output and the exact source revision. Then use Oracle’s documented full APEXlang import remedy with a reviewed, complete application revision. Oracle known issues.
Before that import, reconcile any legitimate changes made since the recovery source was captured. Oracle warns that importing with the same application ID overwrites changes on the APEX server, and recommends backing up the current application. Rehearse the replacement in an isolated development target when possible. Oracle source-upgrade guidance.
A full-directory SQLcl import has this documented form: Oracle source-upgrade guidance.
apex import -input path/to/reviewed-applicationReplace path/to/reviewed-application with the complete APEXlang application directory. Confirm the database connection, workspace, application ID, and deployment configuration first. This is an illustrative command shape; it has not been executed for this article.
Verify the result
Use these recommended checks after recovery:
- Compare the application alias and current theme with the recorded intended values.
- Open the application through its expected URL and inspect representative pages, navigation, and theme styling.
- Repeat a critical business workflow, including a save or submit where relevant, using safe test data.
- Record the imported source revision, target version, import result, and any behavior still untested.
Before another deployment, recheck Oracle’s known-issues page for a changed workaround or confirmed fix for this Oracle APEX 26.2 import issue. A successful import should be followed by the application checks your release process requires.
For broader migration planning, see the Oracle APEX 26.1 upgrade checklist. That article remains specific to 26.1; use this advisory and the linked 26.2 documentation for this release’s file-level import behavior.
This Oracle APEX 26.2 import issue advisory is based on Oracle documentation checked on October 12, 2026. No runtime or recovery test results are claimed.
