My Oracle Support Banner

New Application ID Ignored when Using "Copy An Existing Application." ORA-00001: unique constraint (APEX_050100.WWV_FLOW_LISTS_PK) violated (Doc ID 2266278.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Oracle Application Express (APEX) - Version 5.1.0 and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
*** Checked for relevance on Feb-20-2019 ****

Symptoms

1. Create a new application in APEX 5.1. Say its ID is 150
2. Create another application based on #1 using "Copy an existing Application".
3. Give the new application a new Application ID that does not conflict such as 200.
4. Create the application.
5. Export the newly created application and you will see that the export file still contains the ID of the application that it was copied from. In this example 150.

This does not occur in APEX 4.2.6.

Note: Because of this, importing the application can cause a PK violation such as:



Changes

 Upgraded from APEX 4.2 to APEX 5.1.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.