SAP Knowledge Base Article - Preview

3678152 - Issue a kill command does not terminate a transaction's spid immediately - SAP ASE

Symptom

  • A long-running transaction completely filled up the transaction log segment.
  • Attempts to terminate the transaction using the "kill" command were unsuccessful, as the process continued to show as "running".
  • Kill not terminate the "spid"
  • Attempts to terminate a spid using "kill with force" also does not terminate the spid either
  • Why would a kill command does not terminate a long running transaction? 


Read more...

Environment

  • SAP Adaptive Server Enterprise 16.0
  • SAP Adaptive Server Enterprise 16.1

Product

SAP Adaptive Server Enterprise 16.0 ; SAP Adaptive Server Enterprise 16.1

Keywords

long-running transaction, kill command, sp_lock, error 1105, log segment full, transaction rollback, restart the server, transaction termination, uncommitted transaction, database locks, transaction log space  , 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.