Hana 2.0 SP04 - Lock wait situation caused by EarlyWatch-Statistic in ERP S/4Hana-1909-02 ?

[christoph_ostrop]

===

===

we got alert of lock waiting -

HanaDB Alert "Long-running blocking situations" (id 49) on database xyz

snapshot   : 2021-03-01 06:25:09.0000000
Alert Name : Long-running blocking situations
Rating     : Warning 1

Details    :
Transaction 83 on saplwawi10:30003 (write TID 1098682810) has been blocked by
transaction 87 (write TID 1098676401) for more than 15.67 minutes.

User Action: Investigate the blocking and blocked transactions and if appropriate cancel one of them.

update vbhdr . . .  running with user DDIC 

but there is no thread with connection id ( of the blocking thread ? )

in ERP in SM50 we can see UPD-wp with class = CL_SUSAGE_IMP_EWA_TCODE_WEBS05CP

any idea? search in support portal without result

[mail2sibashis27]

Hello,

Please refer to SAP Note 2182269 - Database locks on table SUSAGE block all work processes. The report SUSAGE_TOGGLE_ACTIVE can be used to deactivate the usage statistics.

The database lock may block all update processes, if the SM50 process is not handled in time.

[christoph_ostrop]

thanks a lot, (sorry for my late answer)

I have now disabled this feature

[christoph_ostrop]

today that lock-situation comes up again for 3 times

although the SUSage Report is currently is still shown as disabled ?

some day before, we had activated ESH (Enterprise Search) for Fiori FLP usage, it looks like this job now is causing again lock situation (although the SUSage is disabled) ?

any idea?

thanks, Christoph

[christoph_ostrop]

if your database table ACDOCA is very large, more than > 1.000.000.000 entries,

this may cause a DUMP and the SUSAGE statistic job is hanging and causing a db-lock in programm

CL_SUS_IMP_CUP_B_FIN_ACDOCA001CP

Short Text SQL error "SQL code: 131" occurred while accessing table "VBHDR".

TSV_TNEW_PAGE_ALLOC_FAILED <br>What happened?
    An attempt was made to add rows to an internal table. <br>There was no memory available for this however. 

this could be solved by installing corrections of sapnote

2942858 - SUA: Laufzeitfehler vom Typ SQL_CAUGHT_RABAX und TSV_TNEW_PAGE_ALLOC_FAILED

https://launchpad.support.sap.com/#/notes/2942858

=============================================================

additional info: the correction of that sapnote 2942858 did not fix all issues, but instead of two parallel LOCK-situation there is now (only) one LOCK-situation, but the issue still exists . . . 😞

=============================================================

additional info: (after installing sapnote corrections)

first run of that SUSAGE statistic job is hanging and causing a db-lock in programm,

but the next executiion of that SUSAGE statistic job, no more LOCK-situations, so with the second execution, the issue is solved.

so, install of sapnote helps to fix. => https://launchpad.support.sap.com/#/notes/2942858