SAP Knowledge Base Article - Preview

2734951 - Unable to kill a blocked process on mixed data and log tempdb when it is full - SAP ASE

Symptom

  • A mixed data and log tempdb log space filled up.
  • One or more of processes blocked by a spid.
  • The blocking spid cannot be killed.
  • The "dbcc stacktrace" command show the following stacks for the blocking spid:
     
    upsleepgeneric
    uppause
    pg_test_allocator
    pg__deallpage
    pg_deallpage
    bt__pgdealloc
    bt__shrinkleaf
    bt__shrink
    bt__maybeshrink
    bt__handle_pagedone
    bt_getnext
    dol_bt_getnext
    getnext
    ups_deadlock_getnext
    stio_deletescan
    st_deletestatistics
    dropo
    drop_with_retry
    tmp_alldrop
  • The stack trace reported by "dbcc stacktrace" may vary leading up to pg_test_allocator. The key pattern is the top of the stack has pg_test_allocator, uppause, upsleepgeneric.


Read more...

Environment

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

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

CR817697, CR#817697, 817697, 1105, log full , KBA , 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 for Me (Login required).

Search for additional results

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