Solution : https://service.sap.com/sap/support/notes/327595 (SAP Service marketplace login required)
Summary :
Lock wait and deadlock occurrences, resulting in system halts or process terminations with SQL error -911, arise due to prolonged database locks. The parameter settings DLCHKTIME and LOCKTIMEOUT govern these situations. Due to inadequate information post-resolution by the database, it becomes challenging to identify the involved processes or the last executed SQL statements. Utilizing the db6util tool, clearer snapshot data of active processes during a deadlock or lock wait can be obtained. Ensure database monitoring is enabled for effective data collection through db6util. The tool proves crucial in periodically capturing snapshot details for thorough analysis.
Key words :
<resultfile> ]ordb6util -sd [sleep time] [number, db6util -sl [sleep time] [number, default database monitor switchesbuffer pool, obtain clearer snapshot data, solution db6util -sldisplays information, formatted snapshot data, clp command 'db2, database manager configuration, database parameter dlchktime, symptom lock wait
Related Notes :
| 851220 | DB6: Extended deadlock monitor (individual shipment) |
| 837115 | DB6: Collecting Data for a Detailed Deadlock Analysis |
| 820473 | DB6: Snapshot function returns error or hangs |
| 700835 | DB6: db6util displays host names incorr. in lock situations |
| 646657 | DB6: SQL error after migration from DB2 V7 to DB2 V8 |
| 175036 | DB6: The DBSL deadlock trace |