cancel
Showing results for 
Search instead for 
Did you mean: 

Integration Suite JDBC Duplicate Key error

ic3
Explorer
0 Kudos
583

Hello everyone,

on the Integration Suite we get the error "Duplicate Key error" when using the JDBC adapter and an update.
This interface already exists on the PI and works properly.

The test on the Integration Suite takes place with exactly the same payload, exported from the PI.
There is no mapping or special logic. The message is forwarded 1:1 from the source.

Error Message Integration Suite

Sent Message

Configuration on Integration Suite

The difference between SAP PI and Integration Suite are following settings which are not available on Integration Suite. And i think this could be the problem.

And like i said i can take the payload from the integration suite and successfully send it over the PI.

The DB is Microsoft on Premise.

Can you guys help with this problem?

Thanks very much!

Best regards

Igor

Accepted Solutions (1)

Accepted Solutions (1)

openrico
Participant

Hi Igor,

as a test: have you tried to implement a content modifier to modify the body to something plain like this:

Update table yyy set ... Where id=xx and pn=yy

Of course you need another content modifier to get the data from the xpath.

Greetings

Enrico

ic3
Explorer
0 Kudos

Thank you! The answer is correct.

Answers (1)

Answers (1)

VijayKonam
Active Contributor
0 Kudos

Did you change the key in the payload and tried again? Duplicate Key error is nothing to do with CPI or PO. It is the database system that is complaining.

ic3
Explorer
0 Kudos

Hello Vijay, thanks!

As I wrote, it is an update and therefore the key must be the same.
Likewise, I can successfully process the same payload with the same key via the PI again and again.
But of course I tried it with another key without success.

Do you have another idea?

Best regards

Igor

VijayKonam
Active Contributor
0 Kudos

Sorry. I missed that it was update and the error was no in English. It does look strange as you are saying the same statement is working fine from PI. Did you enable SQL Tracing on the target service and checked the actual SQL query that is being sent to the DB? That might give some idea of why it is throwing that error.