Issue with Commit Work and Wait.

[amit_khare]

Hi All,

None of the programs are working in my system which are calling BAPI BAPI_TRANSACTION_COMMIT.

On COMMIT WORK AND WAIT statement, the process is going into indefinite loop. Everything was fine till last Thursday and there are no updates or patch level change or notes applied in the system.

Please advice.

[Former Member]

A silly comment, but just in case...

I'm assuming you have checked SM14 and updates are active in your system...

If yes, then maybe a look at the process overview in SM50 (per application server) and your update processes help. Are update processes available or are they all busy and hanging on something? Also, you could do some update debugging of a process to get some further information if necessary.

[amit_khare]

Hi Harald,

Thanks for replying. I checked the mention tcodes and not able to find any stuck queue.

Please advice.

Regards,

Amit

[Former Member]

Hi Amit,

The issue may be because your dispatcher is waiting for work processes which are already busy or may be due to the unavailablity of buffer.

Can you forcefully do an application server restart, you can use transaction sm51 to perform a "restart after error."

A restart of the application server means that all SAP buffers on the affected application server are lost.

Please also discuss with your BASIS colleagues, who can help you more.

Regards,

Antony Thomas

[amit_khare]

Hi Antony,

We tried everything but still the issue is there. We have also raised the message to SAP for the same.

If anyone has any inputs on the issue please suggest.

Regards,

Amit

[Former Member]

<div style="text-align:left">We tried everything but still the issue is there.</div>

Normally it's much easier to get help if you try to be as detailed as possible when explaining the problem and what exactly you have tried. No offense, but tried everything most likely translates into almost everything...

Some information/checks I'd be looking for:

<ul style="list-style:square!important">

<li>What functions are (or coding is) involved? Are they all standard or custom?</li>

<li>Have you tried update debugging and/or the usual traces (runtime analysis, SQL trace, etc.)?</li>

<li>What do you see in the process overview?</li>

<li>What about system log, developer trace, database logs/alerts, etc.?</li>

</ul>

Obviously my list is much too short and incomplete - yours must be longer. If you share your results (including your exchange with SAP) I suspect you have a better chance (though of course no guarantee) of somebody providing a valuable clue.

Not sure if it's just me, but the part that sounds so odd and suspicious is that you only mention commits via BAPI_TRANSACTION_COMMIT. As this is just a wrapper around a COMMIT WORK I'm tempted to think it's the functionality that's invoked before (i.e. linked to the registered update functions/modules). Without any additional knowledge though, my first shot was for general update problems (which you ruled out).

[amit_khare]

Hi Herald,

Thanks for the details. We checked all this thing.

I think we are able to recover this. BASIS is working on it and might be resolved after refreshing all update locks.

Will update the post.

Regards,

Amit

[amit_khare]

Solved by BASIS by deleting Locked Queues.