My Oracle Support Banner

C1-TXNVP Error Cascades To Other Transactions Within Chunk (Doc ID 2269158.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Financial Services Revenue Management and Billing - Version 2.4.0.1.0 and later
Information in this document applies to any platform.

Symptoms

On :ORMB 2.4.0.1.0 version, TFM

C1-TXNVP Error Cascades to Other Transactions Within Chunk

While processing transactions in TFM, user encountered an error in C1-TXNVP, under one of it's PL/SQL packages CISADM.PKG_RMB_PRICEASSIGN.

It was observed that the error on one transaction cascades to other transactions within the same chunk.

User believes this is incorrect and an error on one transaction should not be cascaded to other transactions.

ERROR
-----------------------
ERROR (org.hibernate.engine.jdbc.spi.SqlExceptionHelper) ORA-01427: single-row subquery returns more than one row
ORA-06512: at "CISADM.PKG_RMB_PRICEASSIGN", line 238
ORA-06512: at "CISADM.PKG_RMB_PRICEASSIGN", line 409

14:35:22,940 [DEFAULTWorker:0] ERROR (com.splwg.ccb.domain.banking.transactionFeed.transactionFeedAgg.TransactionAggregationBatch) Error Processing Records in VP
org.hibernate.exception.DataException: ORA-01427: single-row subquery returns more than one row
ORA-06512: at "CISADM.PKG_RMB_PRICEASSIGN", line 238
ORA-06512: at "CISADM.PKG_RMB_PRICEASSIGN", line 409

at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:134)
at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:49)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:125)
at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:110)
at org.hibernate.engine.jdbc.internal.proxy.AbstractStatementProxyHandler.continueInvocation(AbstractStatementProxyHandler.java:129)
at org.hibernate.engine.jdbc.internal.proxy.AbstractProxyHandler.invoke(AbstractProxyHandler.java:81)
at com.sun.proxy.$Proxy7.execute(Unknown Source)
at com.splwg.ccb.domain.banking.transactionFeed.transactionFeedAgg.Finalization.doPrcFinalization(Finalization.java:223)
at com.splwg.ccb.domain.banking.transactionFeed.transactionFeedAgg.TransactionAggregationBatch$Worker.executeStoredProcForPriceAssignment(TransactionAggregationBatch.java:528)
at com.splwg.ccb.domain.banking.transactionFeed.transactionFeedAgg.TransactionAggregationBatch$Worker.executeWorkUnit(TransactionAggregationBatch.java:371)
at com.splwg.base.api.batch.AbstractThreadWorker.executeWorkUnitDetailedResult(AbstractThreadWorker.java:193)
at com.splwg.base.api.batch.ThreadWorkUnitExecutable.executeAndAccumulateStats(ThreadWorkUnitExecutable.java:103)
at com.splwg.base.api.batch.ThreadWorkUnitExecutable.execute(ThreadWorkUnitExecutable.java:74)
at com.splwg.base.api.batch.AbstractCommitStrategy.executeWorkUntilCommitOrEnd(AbstractCommitStrategy.java:135)



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run TFM


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
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.