Troubleshoot-Adapter engine:Error Setting the message status to DLNG failed

[Former Member]

Dear Experts,

We use SAP RFC- PI-JDBC(MSSQL). here the Data(message) successfully transfered to mssql table but the status is been set to DLNG failed, And it finally shown as SYSTEM ERROR.

QoS required: ExactlyOnce , here The Message has got inserted in that particular table and in PI adapter the status turned to DLNG faild and the service again tries to send the same message which is not possible becoz the data is set for primary value.

2010-09-15 09:59:48 Success Message successfully received by messaging system. Profile: XI URL: http://XXXXX:50000/MessagingSystem/receive/AFW/XI Credential (User): YYYY

2010-09-15 09:59:48 Success Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

2010-09-15 09:59:48 Success Message successfully put into the queue.

2010-09-15 09:59:48 Success The message was successfully retrieved from the receive queue.

2010-09-15 09:59:48 Error Setting the message status to TBDL failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Error updating status..

2010-09-15 09:59:48 Success Delivering to channel: CCR_JDBC_ZZZZZ

2010-09-15 09:59:48 Success MP: Entering module processor

2010-09-15 09:59:48 Success MP: Processing local module localejbs/CallSapAdapter

2010-09-15 09:59:48 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce

2010-09-15 09:59:48 Success JDBC adapter receiver channel CCR_JDBC_ZZZZZ : processing started; party , service BS_BCP_IMPLOG_ZZZZZ

2010-09-15 09:59:49 Success Database request processed successfully

2010-09-15 09:59:49 Success MP: Leaving module processor

2010-09-15 09:59:49 Success The message was successfully delivered to the application using connection JDBC_http://sap.com/xi/XI/System.

2010-09-15 09:59:49 Error Setting the message status to DLNG failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Error updating status..

2010-09-15 10:37:01 Success The message was successfully retrieved from the receive queue.

2010-09-15 10:37:01 Success The message status set to DLNG.

2010-09-15 10:37:01 Success Delivering to channel: CCR_JDBC_ZZZZZ

2010-09-15 10:37:01 Success MP: Entering module processor

2010-09-15 10:37:01 Success MP: Processing local module localejbs/CallSapAdapter

2010-09-15 10:37:01 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce

2010-09-15 10:37:01 Success JDBC adapter receiver channel CCR_JDBC_ZZZZZ : processing started; party , service BS_BCP_IMPLOG_ZZZZZ

2010-09-15 10:37:01 Error Unable to execute statement for table or stored procedure. 'imp_log' (Structure 'STATEMENT') due to com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.

2010-09-15 10:37:01 Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'imp_log' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.

Thanks in advance for your valuable answer.

[Former Member]

Hi Vinaygam,

2010-09-15 10:37:01 Error Unable to execute statement for table or stored procedure. 'imp_log' (Structure 'STATEMENT') due to com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.

2010-09-15 10:37:01 Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'imp_log' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.

See above error, It cannot the Duplicate Key in your log table. Duplicate means repeated as a same data.So kindly check once your data.

-

---

IF,I assume your scenario is Synchronous, If you are using any sender JDBC adapter just check with your Quality of Service and set it to "Exactly once".

so kindly do it.

Thank you,

Sateesh

Edited by: sateesh kumar .N on Sep 17, 2010 8:17 AM

[Former Member]

The ICM time is increased then also the problem remain same.

Exact problem: The data is transfered to the destination system and then also the status DLNG failed is taken.

Please advise what might be the exact problem.

2010-09-16 15:58:06 Success The message was successfully delivered to the application using connection JDBC_http://sap.com/xi/XI/System.

2010-09-16 15:58:06 Error Setting the message status to DLNG failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Error updating

So again it tries to send the message to destination system which will not be succed becoz of primary key set in the destination system.

[Former Member]

Dear Vinayagam,

Because you are saying 1. that the message is successfully delivered,

2. you are not getting this error all the time, and

3.You also get the prmiary key violation error, I suspect that you are sending duplicate rows.

If you are using INSERT statement, use UPDATE_INSERT instead.

Then you need to think about why duplicate rows are sent.It could be really a duplicate or something has changed and that's why it is selected again.

Cheers.

Raju

[Former Member]

It can be the HTTP timeout issue if the data is huge in size.

Try to increase the timeout value in ICM and check.

-Supriya.

[stefan_grube]

This could be an issue with JDBC library.

Make sure that MS SQL version and JDBC librarie are consistent.

[Former Member]

And this issue is not happening all that time...

[stefan_grube]

Is the payload huge? It could be a timeout issue.