Error status on outbound side

[Former Member]

Hi experts,

I am in JDBC to IDOC scenario and right now i face following error in SXI_MONITOR (black and white flag in status field BUT Red flag in outbound status😞

"Message has error status on outbound side"

This is a heavy interface (up to 8MB) but, in the past, we did not receive this error. I saw that there is an entry in SM58 from the PIAFUSER that says "Lock table overflow"

Thus, I set the parameter enque/tablesize up to 8192 MB but after restarting the system it did not work either, a new entry in SM58 is shown.

If i analyse the runtime tab of the response of the message i can see

<SAP:AdapterStatus>007</SAP:AdapterStatus> --> for an erroneous interface execution (payload=7,2MB)

<SAP:AdapterStatus>006</SAP:AdapterStatus> --> for a successful execution (payload 6.5 MB)

Can anyone plz, help me on this?

I cannot explain why we did not face this in the past.

Can you please explain how the lock table works? and what does the overflow means?

Thanks a lot in advance and best regards,

David

[Former Member · Accepted solution]

Hi David

Please check the following link

http://help.sap.com/saphelp_nw04/helpdata/en/37/a2e3ba344411d3acb00000e83539c3/frameset.htm

Thanks

Sai

[Former Member · Accepted solution]

Hi Sai,

Ive checked what you mentioned but cannot see the point there. Maybe you can help me:

Enqueue Operations 847

rejected 17

Error occured 0

Dequeue Operations 604

Error occured 0

Dequeue All Operations 661

Cleanup Operations 0

Backup Operations 1

Read Operations 21

Compress Operations 0

Verify Operations 0

Records written 58408

to the backup file 2

Maximum Number of Lock Owners 58406

Maximum Fill level 4

Current Fill Level 0

Maximum Number of Lock Arguments 58406

Maximum Fill level 14

Current Fill Level 0

Maximum Number of Lock Entries 58406

Maximum Fill level 14

Current Fill Level 0

Update; Fill Level at Maximum 1

Current Fill Level 0

Time in Lock Table /Seconds 0.073970s

Wait for Lock Table /Seconds 1.691441s

Time in Lock Server /Seconds 0.000000s

Besides, i dont think it is gonna be a matter of disk spaces as all of them have, at least, 3.0 Gb of free space.

Any other clue? I increased the enque/table_size up to 65 MB and the lock table overflow in SM58 still remains!!!

Thanks a lot and best regards,

David

[Former Member · Accepted solution]

Hi David

Please look at SAP notes 746138 and 896024.

Thanks

Sai

[Former Member · Accepted solution]

Hi there,

this issue got solved by setting the enque/table_size parameter in the SAP backend at which XI was trying to send the IDOCs.

Thanks for participating

best regards,

david

[Former Member]

Hii Domingo,

Can u please tell me where exactly this setting have been made.

As I m also faceing the same problem please guide me for this.

As our business stuck due to this.

Thanks,

Nitin

[Former Member]

Hi,

another point is that you have maybe not enough space on your hard disk of your XI server.

Eventually delete the temporary files, and content folders like old logs.

Mickael