Skip to Content
0
Former Member
Nov 03, 2011 at 08:37 PM

During BOP processing , row lock on table TTSTR is held for very long time

471 Views

Dear Friends,

Given the fact that we have a large number of sales order line items to process, we have numerous BOP batch jobs that are running at the sametime.

Our issue is that when one of our BOP batch jobs are running, it appears to lock table TTSTR (lock object name = ETSTRID) for a long period of time. The BOP job has to complete before the lock is released. And it appears that it is the same Time Stream Id (SAPxxxxxxx) that is causing this lock. The other BOP jobs will then wait for the TTSTR table to be released. If these other BOP jobs cannot access table TTSTR within 10 minutes, they start to abend with a 913.

Any reason why this particular Time Stream would cause the TTSTR row to be locked for a long time?

I am not sure how to check for INVALIDATE situation with this particular Time Stream.

I looked at OSS Note 311258 but since we are onSAP_Basis 7.0, that note was for lower versions.

If anyone has any suggestions, it would be greatly appreciated.

Thank you.

Michael Tylisz