My Oracle Support Banner

ADOP Patch Object FND_CONCURRENT_PROGRAMS Causes ORA-00001: Unique Constraint (Doc ID 2913648.1)

Last updated on FEBRUARY 22, 2023

Applies to:

Oracle Applications DBA - Version 12.2.10 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.10 version, Online Patching - OP

ADOP patch object FND_CONCURRENT_PROGRAMS causes ORA-00001: unique constraint



ERROR
-----------------------

The event is captured within the Conflict Resolution Manager log file as follows:

18-OCT-2022 11:01:39 : Initialize iprogs
ORA-00001: unique constraint (APPLSYS.FND_CONCURRENT_PROGRAMS_U2) violated
ORA-06512: at "APPS.FND_CONCURRENT_PROGRAMS>", line 123
ORA-04088: error during execution of trigger 'APPS.FND_CONCURRENT_PROGRAMS>'
update fnd_concurrent_programs set iprog_id=0 where application_id> -1 and concurrent_program_id> -1
An error occurred in routine rxcrm_iprog_init.
ORACLE error 1 in rxcrm_iprog_init


Cause:

rxcrm_iprog_init failed due to ORA-00001: unique constraint (APPLSYS.FND_CONCURRENT_PROGRAMS_U2) violated
ORA-06512: at "APPS.FND_CONCURRENT_PROGRAMS>", line 123
ORA-04088: error during execution of trigger 'APPS.FND_CONCURRENT_PROGRAMS>'.

Changes

 

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.