SAP Knowledge Base Article - Preview

3082118 - Workload analyzer replay issue - deadlocks happening when there were none in capture - SAP ASE

Symptom

  • Why are there deadlocks on a replay when there are none reported in the capture for example:
    00:0011:00000:00978:20XX/07/06 17:01:30.33 server  Workload capture status: started, Stop reason: n/a, Elapsed time: 0 sec, Query time: 0 sec, Batches: 0, Packets: 0, Number of files: 10, Total File size: 240 bytes, Overhead: 0 sec, 0%, apture file under directory: /mydirectory/workload
    00:0013:00000:00986:20XX/07/06 17:36:13.24 server  Workload capture status: stopped, Stop reason: request, Elapsed time: 2082 sec, Query time: 7251 sec, Batches: 369353, Packets: 518926, Number of files: 10, Total File size: 208177359 bytes, Overhead: 0 sec, 0%, Capture file under directory: /mydirectory/workload


  • But the replay reports are showing many deadlocks:
Error NumberTotal CountRatioSeverityMessage Sample
1205200100.00%13Your server command (family id #0, process id #155) encountered a deadlock situation. Please re-run your command.


Read more...

Environment

  • SAP Adaptive Server Enterprise 15.7
  • SAP Adaptive Server Enterprise 16.0

Product

SAP Adaptive Server Enterprise 16.0

Keywords

KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.