SAP Knowledge Base Article - Preview

2691726 - DB became unresponsive after Error:15403 happened - SAP ASE

Symptom

  • When the following error message happened , DB became unresponsive.
    Cannot allocate shared memory as 'max memory' limit of 'size' pages has been reached. Please increase configuration parameter 'max memory' to allow additional shared memory allocation. Total physical memory allocated so far 'size' pages.
    No memory for Encrypted Columns Frag bucket pool growth (size bytes)
  • After the message 'Cannot allocate shared memory~' happened, the following stacktrace also happened. The last error which caused this stacktrace is 15403.
    lasterror = 15403 preverror = 0 transtate = 1
    exc_raise
    en_init_glbctx
    pss_init
    wt__setpss
    uwconnect
    wt_connect
  • Even though Encrypted Columns Frag bucket pool was disabled, the same issue still happened.

Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 16.0 SP03 codeline (SP02 is unaffected)
  • Parallel processing

Product

SAP Adaptive Server Enterprise 16.0

Keywords

CR816538, CR#816538, 816538, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace,  stack, registers , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

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.