Solution : https://service.sap.com/sap/support/notes/175036 (SAP Service marketplace login required)
Key words :
start -> settings -> control panel -> system -> environment -> user variables, setenv db6_dbsl_trace_dir <tracepath>export db6_dbsl_trace_deadlock_time=<time>, hkey_local_machine\software\sap\<sapsid>\environmentuse, sap work process requires 5 mb, dbs/db6/dbsl_trace_dir = <tracepath>, individual sql statement exceeds, dbs/db6/dbsl_trace_dir activating, reasoncode 2using database functions, seconds>db6_dbsl_trace_dir = <path>depending, activated require additional memory
Related Notes :
| 851220 | DB6: Extended deadlock monitor (individual shipment) |
| 837115 | DB6: Collecting Data for a Detailed Deadlock Analysis |
| 513133 | DB6: SMP save time function |
| 486951 | DB6: Configuration of DB2 CLI trace |
| 327595 | Analysis of database lock situations using db6util |
| 132290 | DB2/CS: SQL0912 maximum number of lock requests |
| 31707 | DB6: DBSL trace for performance/error analysis |