SAP Knowledge Base Article - Preview

3344429 - Information on IDLE process - SAP ASE

Symptom

  • We investigate a situation when idle processes (spids) in the "AWAITING COMMAND" state hold locks and cause blocking in ASE.
  • These idle processes seems to be left in ASE by a client application that doesn't properly close connections to the ASE server.
  • We plan to perform a test to simulate the idle process situation caused by the application.
  • Is there a server-level Trace Flag which can be enabled to capture information about an idle spid/connection that can be used to fix the issue on the application side?
  • Is there any other command/query to capture required details for IDLE processes?


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 16.0 SP03 PL09
  • .net client using ODBC driver

Product

SAP Adaptive Server Enterprise 16.0

Keywords


idle process, awaiting command, blocking issue, locks, client application, connection issue, server

  • level trace flag, MDA tables, monProcess, monProcessWaits, monWaitEventInfo, monProcessLookup, wait events
, 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 for Me (Login required).

Search for additional results

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