Solution : https://service.sap.com/sap/support/notes/1702617 (SAP Service marketplace login required)
Summary :
During screen generation in SAP, DDFTX table entries are managed in the same transaction as the application, resulting in extended database locks and potential deadlocks when concurrent processes also attempt to write to DDFTX. The trace logs indicate timeouts and aborted transactions due to these locks. The solution involves applying a SAP kernel patch that handles DDFTX insertions in a separate transaction, immediately committing them to prevent deadlock conditions. This patch is compatible with multiple Basix Releases as a downward-compatible kernel (DCK), detailed in SAP Note 1629598.
Key words :
58 2012b log by4=> sql error -911 performing ins, log byo=> deadlock aborts transaction [dbsh#2 @ 1143] [dbsh 1143 ], [ibm][cli driver][db2/aix64] sql0911n, error => missing return code handler difunct#, sqlstate=40001 row=1bb sat mar 3 13, sqlstate=40001 row=1 [dbtrtab#2 @ 3914] [dbtrtab 3914 ], abap dictionary source tables, warning => big time diff 3600744687 [2519499261 1825276652], 54 2012y dyload /jad01/ut05r_b40 1000, constructiony dyload /jad01/ut05r_b40 1000
Related Notes :
| 1614802 | Mass activation hangs during INSERT in the table DDFTX |
| 1155807 | Database deadlock when executing DD_INT_UPDATE_DDFTX |