XI ERROR_UNKNOWN_PAYLOAD_FORMAT;0

[Former Member]

Hi Guys,

In an already live PI 7.0 environment we have several Proxy to JDBC XI interfaces that work fine and post data to an external SQL Database from SAP R/3. In one of them we get the following error in RWB Message Monitoring the last 2-3 weeks "JDBC message processing failed; reason ERROR_UNKNOWN_PAYLOAD_FORMAT;0"

That's really strange because the interface runs successfully most of the times that it is executed within the day except for a couple of times. To me it seems that it is a data format error. In SXI_MONITOR everything is ok, the error occurs on the JDBC adapter side. Even if I try to resend the message via Message Monitoring there is no luck, I cannot display the content of the messag/payload from the Audit Log that is posted to the SQL Database.

No upgrade took place on the PI system recently.

Any ideas?

[baskar_gopalakrishnan2 · Accepted solution]

You might want to check both these threads. Check the same channel is shared for other scenarios as Mark explained below.

http://scn.sap.com/thread/1871394

Also refer SAP note on this thread

http://scn.sap.com/thread/2017504

[Former Member · Accepted solution]

Hi Guys,

The issue has now been solved after a lot of effort and investigation. The Adapter Engine status was giving an error in RWB because the default delete job from adapter framework which deletes expired messages and log entries older than 20 days from the Adapter Engine was not running for the last 3 months. Therefore, I activated that again and had it run. Also, I relased all messages that are older than 20 days in the database. Then I executed a manual deletion of those messages that were kept in the Adapter Engine since then and had not been deleted as well as a reorganization of the message database via http:hostname:portNumber/MessagingSystem/archiving/reorgdb.jsp. Those messages are stored in tables XI_AF_MSG and XI_AF_MSG_AUDIT and are in the same tablespace. All the above were affecting negatively the performance of the JDBC adapter thus causing messages to fail.

[Former Member · Accepted solution]

Thank you.

Went back 2 years and cleared up all our old messages in error. Resolved our issue.

Excellent Post.