SAP Knowledge Base Article - Preview

2276464 - ASE spids hung in "latch sleep", hanging "dump tran", Errors 2630 / 871 - SAP ASE

Symptom

  • You are running applications on SAP ASE database.
  • On high-concurrency INSERT/DELETE environments, you notice one of the following to occur and subsequently, hang the ASE server :
    • One or more hanging spids are seen in sysprocesses or sp_who output with status 'latch sleep'. These spids cannot be killed.
    • 'dump database' or 'dump transaction' process gets stuck and cannot be killed. The spid is shown in master..syslogshold table with name $dmpxact.
    • the hanging 'dump tran' event may or may not be preceded by Error 2630 in the ASE errorlog: Error: 2630, Severity: 21, State: 1 In database 'SID', page 111370512 is linked backward to page 111370515, but that page is linked forward to page 121286312. Please report this internal error to Sybase Technical Support.
    • backupserver and future backups do not take place, as a result
    • ASE errorlog reports stack trace errors accompanied by Error 871 in some cases. The functions in the stacktrace:

bt__pgdealloc
bt__shrinkleaf
bt__shrink
bt__ps_shrinkpg
bt_shrink_post


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7 SP136
  • SAP Adaptive Server Enterprise (ASE) 16.0 SP01
  • SAP Adaptive Server Enterprise (ASE) 16.0 SP02
  • SAP Adaptive Server Enterprise (ASE) 15.7 SP136 for Business Suite
  • SAP Adaptive Server Enterprise (ASE) 16.0 SP01 for Business Suite
  • SAP Adaptive Server Enterprise (ASE) 16.0 SP02 for Business Suite

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

"dump tran", latch, hang, CR 767494, CR 792164, CR 797184, CR 797186, CR 798255, CR 797550, hung, hanging, HK GC, 2630, post-commit shrink, housekeeper garbage collection, Traceflag 3993, dump process stuck, BT_SHRINK, internal error , KBA , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed

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.