2062009 - Undetected deadlock condition involving DUMP DATABASE and DUMP TRANSACTION - SAP ASE

• DUMP DATABASE command is executed
• DUMP TRANSACTION command is executed
• Execution of sp_who may show DUMP DATABASE blocked by DUMP TRANSACTION:

login   spid  enginenum status     suid program_name     cmd              cpu  physical_io  memusage  blocked  dbid  tran_name  time_blocked  loggedindatetime
sapsa 579   29        sleeping   4    JS Agent - sapsa DUMP TRANSACTION 1    2093         90        0        4     $dmpxact   null          8/7/2014 22:00
sapsa 990   16        lock sleep 4    JS Agent - sapsa DUMP TRANSACTION 1    0            27        579      4     $dmpxact   3401          8/7/2014 23:00
sapsa 1719  7         lock sleep 4    isql             DUMP DATABASE    487  2292         20        579      4     null       2790          8/7/2014 8:43

• A second DUMP TRANSACTION may also be shown
• The blocking process may have a status of "sleeping"
• ASE error 8213 may or may not appear in the ASE errorlog:

Error: 8213, Severity: 20, State: 3
Failed to acquire address lock on object mytable

• ASE configuration parameter "enable concurrent dump tran" set to '1'
• ASE is configured for two or more engines
• The above blocking condition remains static and does not clear itself
• KILL of the DUMP DATABASE process may clear the condition
• ASE reboot may be needed to clear the condition if KILL of the DUMP DATABASE process fails to clear the problem

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

KBA , cr768880 , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Bug Filed