Hello,
We have recently upgraded from APEX 19.1 to 19.2, and now are unable to import an app into our UAT environment with an app export from our Dev environment, within the same workspace (workspace "A"). An ORA-00001: unique constraint (APEX_190200.WWV_FLOW_LISTS_PK) violated error is raised during import. I don't believe this has anything to do with shared component lists though, as we did not have this issue prior to upgrade. Each of our environments (same schema and workspace names) is on a separate database. Strangely, in another workspace (workspace "B", different app owner schema but on same databases), we have been able to move up apps to higher environments using export/import without error. What could have gotten corrupted/out of sync on workspace "A" that is now causing issue? Is it an application "offset" issue? ...how to correct?
One work around I came up with is as follows:
- Import the app (original app id 100 from Dev) into a new app (app id 101) in UAT.
- Export the new app (app id 101) out of UAT.
- Import the app 101 export file to replace the existing app 100 in UAT. No error this time!
- Delete app 101 in UAT
However, if I then try to export a single page from App 100 in Dev, and import into App 100 in UAT, I get an ORA-02291: integrity constraint (APEX_190200.WWV_FLOW_STEP_UI_FK) violated - parent key not found error. I don't understand why because the entire app was imported, and I attempted to export a single (unchanged) page that exists in both environments.
I have seen older posts mentioning similar issues occurring after upgrades in older APEX versions, but often the solution is to import into a new application ID. This is not a good solution for us since we have URL redirect rules setup to point to a specific application ID's for various APEX apps.
APEX version: APEX 19.2.0.00.18
DB version: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0
Browser version: Chrome 83.0.4103.61