SAP Knowledge Base Article - Preview

3440143 - Blocking by HK CHORES after error 1295 during 'out of locks' - SAP ASE

Symptom

  • ASE server shows spids blocked on the HK CHORES system process
  • The ASE errorlog shows that error 1295 was encountered during a (prolonged) period of running out of locks:

    Error: 1204, Severity: 17, State: 2 occurred for User ...
    (many more)
    Error: 1204, Severity: 17, State: 2 occurred for User ...

    Error: 1295, Severity: 26, State: 1
    Unconditional lock request for table or page 123, dbid 1 was made while holding a latch.

    More 1204 ...

  • A check on syslocks shows the page mentioned in error 1295 is for syslogins (id = 33)
    In this example HK CHORES was spid 9, page 123:

    id     dbid    page  type    spid    class      
    ----  ------  --------  ------  ------  --------------------
    33      1       123    266      9       Non Cursor Lock

  • Checking the PSS for the HK CHORES spid, by collecting dbcc pss (0, #spid) where #spid is the HK CHORES spid
  • The 'error' section contains error 1204, which can be seen long after 1204 issue was resolved

    **** Printing errors starting from most recent one: ****
    ...
    [2] error=3602 (SYSTEM, SYS_XACTABORT) severity=25 (EXC_CONTROL) state=73945518
    ...
    [1] error=1204 (LOCKM) severity=17 (EX_RESOURCE) state=2


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 16.0 SP03 & SP04

Product

SAP Adaptive Server Enterprise 16.0

Keywords

hk_relinquish , hk_chores_proc , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Known Error

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.