Hi APEX Team,
We are currently testing an upgrade to Oracle APEX 26.1, and I found one ( of 20+ ) production applications that I cannot export in APEXLANG format. But this is a critical one.
The application is:
Workspace: CLA_PUBLIC
Application ID: 1968
Application Name: Clay Lacy Aviation
The application itself exists, opens normally, and appears to work normally.
Before APEX 26.1 ( in 24.1 and 24.2) , we were exporting this application to YAML, and that worked normally.
In APEX 26.1, this specific application fails when exported as APEXLANG. Exporting the same application as SQL still works.
Version information
This environment is currently on APEX 26.1.0, with no APEX patches applied:
select comp_id, version
from dba_registry
where comp_id = 'APEX';
COMP_ID VERSION
------------------------------ ------------------------------
APEX 26.1.0
select patch_version, installed_on
from apex_patches;
no rows selected
I looked through the list of bugs allegedly fixed in APEX 26.1.1, and I did not see anything that looked similar to the issue I am experiencing.
What I tried:
1. SQLcl 26.1 export with -exptype APEXLANG
apex export -api 1968 -exptype APEXLANG -debug
This fails with:
ORA-01403: no data found
ORA-06512: at "APEX_260100.WWV_FLOW_EXPORT_INT", line 2691
ORA-06512: at "APEX_260100.WWV_META_META_DATA", line 5240
ORA-06512: at "APEX_260100.WWV_META_META_DATA", line 2179
ORA-06512: at "APEX_260100.WWV_META_META_DATA", line 4505
ORA-06512: at "APEX_260100.WWV_META_META_DATA", line 5187
ORA-06512: at "APEX_260100.WWV_FLOW_EXPORT_INT", line 2634
ORA-06512: at "APEX_260100.WWV_FLOW_EXPORT_INT", line 2825
ORA-06512: at "APEX_260100.WWV_FLOW_EXPORT_API", line 110
ORA-06512: at line 3
2. SQLcl export without APEXLANG / default SQL export
apex export -api 1968 -debug
This works and creates the SQL export file:
File f1968.sql created
3. Calling APEX_EXPORT directly from SQL Developer
I also tried calling the export API directly from SQL Developer:
select apex_export.zip (
p_source_files => apex_export.get_application (
p_application_id => 1968,
p_type => 'APEXLANG'
)
)
from dual;
For application 1968, this fails with a different error:
ORA-06531: Reference to uninitialized collection
ORA-06512: at "APEX_260100.WWV_FLOW_EXPORT_INT", line 3374
ORA-06512: at "APEX_260100.WWV_FLOW_EXPORT_INT", line 3402
ORA-06512: at "APEX_260100.WWV_FLOW_EXPORT_API", line 205
ORA-06512: at line 1
4. Same APEXLANG export for another application
For comparison, exporting another application in the same workspace works correctly:
apex export -api 199 -exptype APEXLANG -debug
Result:
File lacy199\application.apx created
The direct SQL Developer call also works for application 199. It returns a BLOB column, which I saved locally and opened as a valid ZIP file.
So the problem seems to be specific to application 1968, not a general SQLcl/APEXLANG/export setup issue.
5. Export from APEX Builder GUI
Exporting application 1968 from the APEX Builder GUI also does not produce a valid export.
It creates a file with what looks like a proper ZIP filename, but the file is not a ZIP archive. It appears to be an HTML file instead and looks like it's a HMTL output for,page 4900 of app 4000. I will attach it.
Summary
So far, the behavior is:
Application 1968 SQL export: works
Application 1968 APEXLANG export via SQLcl: fails with ORA-01403
Application 1968 APEXLANG export via API: fails with ORA-06531
Application 1968 GUI export: produces non-ZIP / HTML output
Application 199 APEXLANG export via SQLcl: works
Application 199 APEXLANG export via API: returns valid ZIP BLOB
Application 1968 runtime: works normally
Pre-26.1 YAML export for application 1968: worked previously
APEX 26.1 APEXLANG export for application 1968: fails
I have attached the detailed SQLcl debug output with the commands and results.
Could you please advise how to proceed?
I would be happy to provide the application export privately through an SR, but I cannot attach the production application or related files publicly on the forum.
Thanks,
Alex
apexlang_export_problem.txt