Task <task_id> (appl. <appl_id> on <appl_node>) is waiting for lock '<lock_mode>' on table <table_name>
since <duration>s, locked '<lock_mode>' from task <task_id> (appl. <appl_id> on <appl_node>, state <task_state>)
If a user task is waiting for a lock, especially in dialog operation, this causes long response times which seem to be performance problems. Nevertheless, if access to the same data is necessary, then it is normal database behaviour to set locks to make sure that transaction consistency is maintained.
If a lot of such messages occur, it should be checked from application side if the time for holding the lock can be reduced. This can be reached by additional COMMITs.
Relevant DB-Analyzer Files
Helpful with ...
|1243937 - FAQ: SAP MaxDB/liveCache SQL and object locks||Find general information about SQL/object lock mechanisms and how to influence the behaviour.|
Content / Helpful with ...
|Session 12: Analysis of SQL Locking Situations||Find more information how deadlocks may arise and how to prevent them.|