DuplicateMessageExc in Snder JDBC Adapter although succesfull in SXMB_MONI

[Former Member]

Hi Experts,

I am getting "com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 5b72a60b-b0e2-48f0-3701-cdb67ac1c5b2(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00149397) violated " as well as "Error during commit or rollback of database transaction: 'com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to commit transaction: The transaction has been rolled back: com.sap.engine.services.ts.transaction.TxRollbackException' in the Sender JDBC Adapter.

The message is processed successfully in ABAP stack . I have stopped and started the relevant Communication channel from RWB however the message is continually processed by the adapter with error. Please assist , how to cancel the message.

[Former Member]

hi,

its a error related to oracle database.

check this for help.

http://www.dba-oracle.com/sf_ora_00001_unique_constraint_violated.htm

http://www.cryer.co.uk/brian/oracle/ORA00001.htm

chirag

[Former Member]

Hi,

We have the same issue.

Any input, please? have you solved this problem?

thanks, in advance

Carme.

[robert_warde4]

This error relates to a JDBC sender adapter on a SAP PI 7.11 SP6 system.

We have identified a problem with this particular interface. CC_JDBC_Send_FrontOffice_RJ35_NFE_CREATE. A specific message, b72a60b-b0e2-48f0-3701-cdb67ac1c5b2, continues to be sent. SAP PI is then rejecting the message as its unable to commit the record processing to an internal table and rolling back the transaction.

When checking NWA Java logs we found the following error:

Module Exception 'com.sap.aii.af.lib.mp.module.ModuleException: senderChannel 'ce6444c858cb3a9baef6b39c35f79106': Catching exception calling messaging system' found, cause: com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 5b72a60b-b0e2-48f0-3701-cdb67ac1c5b2(OUTBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: ORA-00001: unique constraint (SAPSR3DB.SYS_C00149397) violated

So it appears that SAP PI attempts to update an internal table with the status of the message and fails due to duplicate records. In other words SAP PI knows its already processed the message. This message continues to be sent to the adapter for processing and continues to fail.

How can we stop this message being procesed?