If I export an application using the split option
lb genobject -type apex -applicationid 303 -expOriginalIds -split -dir /lb
I'm unable to import it into the next environment due to a variety of errors, depending on the circumstances.
lb update -changelog controller.xml
This was from a completely new application, where the workspace between environments was different.
ORA-20987: APEX - Can not delete application 303, it is installed in a different workspace! - Contact your application administrator.
Subsequent errors in the import include
ORA-20001: Application ID and current security group ID are not consistent.
If I omit the -split option during export, the import works fine.
If I try between environments where the workspace ID is consistent, then I receive a different error when the application does not already exist.
Error starting at line : 2 in command -
begin
-- Manifest
-- FLOW: 303
-- Manifest End
wwv_flow_api.component_begin (
...
ORA-02291: integrity constraint (APEX_200200.WWV_FLOWS_FK) violated - parent key not found
....
ORA-20001: ERR-1014 Application not found.
ORA-06512: at "APEX_200200.WWV_FLOW_API", line 561
ORA-06512: at "APEX_200200.WWV_FLOW_API", line 12909
ORA-06512: at "APEX_200200.WWV_FLOW_API", line 13786
ORA-06512: at line 28
If I first installed the application myself, then re-attempted the lb import, there were no errors, but a new page I created to test the lb import was not installed.
This was not resolved with omitting the split option.
Attempted on SQLcl 21.4
This is one many hurdles to making this functionality work with APEX applications, and we haven't begun to overcome logistical issues with DDL scripts. Hopefully we'll have some success with PL/SQL packages.