SAP Knowledge Base Article - Preview

2146288 - Signal 11 (SIGSEGV) in ubffreef() after error 1204 - SAP ASE 15.7

Symptom

  • ASE error log reports many instances of message 1204 'SQL Server has run out of LOCKS.'

Error: 1204, Severity: 17, State: 2 occurred for User 'SAPSR3'.
SQL Server has run out of LOCKS.
Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure SQL Server with more LOCKS.

  • The user session terminating
  • The ASE error log contains an infected with Signal 11 error in the module ubffreef ()and/or kmuxtskRun():

Current process (0x14dd0172) infected with signal 11 (SIGSEGV)
Address 0x0x00000000015bd712 (ubffreef+0xe2)
...
Address 0x0x000000000160054b (kmuxtskRun+0x75)

  • ASE may become unresponsive as a result.

Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 15.7

Product

SAP Adaptive Server Enterprise 15.7

Keywords

SEGV, segment violation, storage access, 'msg 1204', CR781585, CR#781585, 781585, segmentation, fault, segfault, kisignal, stacktrace,  stack, registers, exceptions, page locking, memory problems, heap memory, hung , KBA , signal 11 , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , BW-SYS-DB-SYB , BW on Sybase ASE Database Platform , 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.