T2T Batch Fails With ORA-00001 and 'ORA-12801: error signaled in parallel query server' (Doc ID 2920309.1)

Last updated on APRIL 25, 2024

Applies to:

Symptoms

When executing a T2T batch, the T2T fails and the following error is output in the T2T log from /<ftpshare>/logs/<Mis Date>/<Infodom>/LOAD DATA/:

[07-12-22 08:42:12 GMT AM][INFO][BACKEND][OFSAA][T2TCPP] executing insert query
FAILED: ORA ERROR : ORA-12801: error signaled in parallel query server P004, instance xxxxxxxxxx:xxxxxxxxxx (1)
ORA-00001: unique constraint (<ATOMIC USER>.XAK1PREPAYMENT_CALCULATION_PARAMETER) violated

[07-12-22 08:42:12 GMT AM][SEVERE][BACKEND][OFSAA][T2TCPP] ClsUDBConnect::executeInsertQuery, Error, unable to execute the insert query. ERROR Message: ORA-12801: error signaled in parallel query server P004, instance xxxxxxxxxx:xxxxxxxxxx (1)
ORA-00001: unique constraint (<ATOMIC USER>.XAK1PREPAYMENT_CALCULATION_PARAMETER) violated

[07-12-22 08:42:12 GMT AM][INFO][BACKEND][OFSAA][T2TCPP] ClsUBatchLoader::Bulk, Error Messaage : ORA-12801: error signaled in parallel query server P004, instance xxxxxxxxxx:xxxxxxxxxx (1)
ORA-00001: unique constraint (<ATOMIC USER>.XAK1PREPAYMENT_CALCULATION_PARAMETER) violated

You expect the T2T to reject any rows already present in target table without the ORA-12801 error.

Cause

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