Error:
while run the purg concurrent program
Error while Purg the concurrent request - ORA-0001 unique constraint %s.%s
Fix:
APPLIES TO:
Oracle Concurrent Processing - Version 12.1.3 and later
Information in this document applies to any platform.
SYMPTOMS
While running FNDCPPUR, it errors out the following:
APP-FND-01564: ORACLE error 1 in request
Cause: request failed due to ORA-00001: unique constraint (%s.%s) violated
CAUSE
Bug 13703211 - FNDCPPUR APP-FND-01564: ORA-00001 UNIQUE CONSTRAINT (%S.%S) VIOLATED
Issue happens when running FNDCPPUR with parameters MODE = COUNT and VALUE=1
SOLUTION
Base bug is from RDBMS and was still in progress when writing this note:
Bug 14013076 - LEN ATTRIBUTE OF VARCHAR STRUCTURE IS CORRUPTED IN BATCH FETCH OF ROWS
Workaround:
Two patches below are necessary for the workaround to work:
- Patch 10106197:R12.FND.B
- Patch 12747284:R12.FND.B
Then try to run with FNDCPPUR with same parameters, but with COUNT >= 2. Once completed, you should be able to run it as before with no issue. This is a workaround
because the issue may reappear later.
while run the purg concurrent program
Error while Purg the concurrent request - ORA-0001 unique constraint %s.%s
Fix:
APPLIES TO:
Oracle Concurrent Processing - Version 12.1.3 and later
Information in this document applies to any platform.
SYMPTOMS
While running FNDCPPUR, it errors out the following:
APP-FND-01564: ORACLE error 1 in request
Cause: request failed due to ORA-00001: unique constraint (%s.%s) violated
CAUSE
Bug 13703211 - FNDCPPUR APP-FND-01564: ORA-00001 UNIQUE CONSTRAINT (%S.%S) VIOLATED
Issue happens when running FNDCPPUR with parameters MODE = COUNT and VALUE=1
SOLUTION
Base bug is from RDBMS and was still in progress when writing this note:
Bug 14013076 - LEN ATTRIBUTE OF VARCHAR STRUCTURE IS CORRUPTED IN BATCH FETCH OF ROWS
Workaround:
Two patches below are necessary for the workaround to work:
- Patch 10106197:R12.FND.B
- Patch 12747284:R12.FND.B
Then try to run with FNDCPPUR with same parameters, but with COUNT >= 2. Once completed, you should be able to run it as before with no issue. This is a workaround
because the issue may reappear later.
No comments:
Post a Comment