ESIC Initialize Fails With ORA-00001: unique constraint (EXT_BATCH_RUN_ID_MAPPING_PK) Errors
(Doc ID 2470038.1)
Last updated on JANUARY 05, 2024
Applies to:
Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.6 and laterInformation in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Enterprise Performance Management (EPM)
External Scheduler Interface Component (ESIC)
Symptoms
When trying to run batches using ESIC, the initialize is failing with Exit status of "-4". Upon reviewing the log it is found that the INSERT into EXT_BATCH_RUN_ID_MAPPING is failing because of a primary key violation. The following error is thrown in the iccserver.log:
ERROR
[06-11-18 17:01:21,277 GMT PM] [DEBUG] [APP] [ICC] Writing to native socket: ##ICC##I##-1##-29##Exception initializing tables for run: Error executing queries. Error: Error while executing Batch :Failed Executing Batch: error occurred during batching: ORA-00001: unique constraint (EXT_BATCH_RUN_ID_MAPPING_PK) violated## with padding
Additionally the ESIC log shows the same error:
ERROR
INFO::SocketClientImpl::Read : More than Zero bytes
##ICC##I##-1##-29##Exception initializing tables for run: Error executing queries. Error: Error while executing Batch :Failed Executing Batch: error occurred during batching: ORA-00001: unique constraint (CONFIG.EXT_BATCH_RUN_ID_MAPPING_PK) violated##
INFORM::clsIccInterface::ProcessReturnDataMessage received from ICC
##ICC##I##-1##-29##Exception initializing tables for run: Error executing queries. Error: Error while executing Batch :Failed Executing Batch: error occurred during batching: ORA-00001: unique constraint (CONFIG.EXT_BATCH_RUN_ID_MAPPING_PK) violated##
The issue can be reproduced at will with the following steps:
1. Issue the following ESIC command:
esic -JI -U<user_id> -P<encrypted pasword> -ROFSAA_FSI_D_INVESTMENTS_FROM_STG -IOFSAA -BFSI_D_INVESTMENTS_FROM_STG -D20180731 -F/tmp
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 |