1955411 - Deadlock detected - SAP ASE

Although you have increased the row lock promotions HWM (High-Water Mark) and LWM (Low-Water Mark), you see deadlocks reported in the server errorlog (<SID>.log) like:

Deadlock Id 1 detected
Deadlock Id 1 detected. 1 deadlock chain(s) involved.

Deadlock Id 1: Process (Familyid 0, Spid 21, Suid 6) was executing a UPDATE command at line 1.
Deadlock Id 1: Process 21 was involved in application ....
Deadlock Id 1: Process 21 was involved on host name ....
Deadlock Id 1: Process 21 was involved in transaction '$chained_transaction'.
Executing procedure: *...*
SQL Text: SQL Statment spid 21
Deadlock Id 1: Process (Familyid 0, Spid 160, Suid 6) was executing a UPDATE command at line 1.
Deadlock Id 1: Process 160 was involved in application ....
Deadlock Id 1: Process 160 was involved on host name ....
Deadlock Id 1: Process 160 was involved in transaction '$chained_transaction'.
Executing procedure: *...*
SQL Text: SQL Statment spid 160
Deadlock Id 1: Process (Familyid 0, Spid 160) was waiting for a 'update row' lock on row 18 page 4409852 of the ... table in database '<SID>' but process (Familyid 0, Spid 21) already held a 'exclusive row' lock on it.
Deadlock Id 1: Process (Familyid 0, Spid 21) was waiting for a 'update row' lock on row 1 page 4443188 of the ... table in database '<SID>' but process (Familyid 0, Spid 160) already held a 'exclusive row' lock on it.

Deadlock Id 1: Process (Familyid 0, Spid 21) was chosen as the victim.
Victim process host = ..., user = `SAPSR3' program name = ....

End of deadlock information.

• SAP Adaptive Server Enterprise (ASE) 15.7 
• SAP Adaptive Server Enterprise (ASE) 16.0

blocking, table scan, queries, table lock, query plan, statistics, sp_recompile, BI , CMS, 42, 4.2, 4.1, 4.x, BusinessIntelligence, Business, Intelligence, Event Viewer, message, logs, messages, BOE, SBOP, Enterprise, , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To