Symptom
- ASE errorlog shows Error 701 for several processes:
Error: 701, Severity: 17, State: 3
There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure ASE with more procedure cache.
- One of the processes hitting error 701 then fails with an "infected with signal 11" in the module curs_close:
Current process (0x93004a) infected with signal 11 (SIGSEGV)
Address 0x0x0000000002046bcc (curs_close+0x1cc) ...
- While handling the signal 11, a fatal exception is reported, which may cause ASE to go down:
FATAL UNHANDLED EXCEPTION: signal 1047607760 hit while handling a previously hit signal. The server cannot continue and will shut down.
- The stack trace for the signal 11 includes functions:
curs_close
css_deallocate
- A second, different pattern has been observed where there is no error 701
- This second pattern shows "infected with signal 11" in the module curs_release and similar stack functions as above
- The fatal exception is also reported:
Current process (0x5c570466) infected with signal 11 (SIGSEGV)
Address 0x0000000080fece54 (curs_release+0xc4) ....
curs_release
curs_close
css_deallocate
lava_last_chance_cleanup
Read more...
Environment
- SAP Enterprise Resource Planning (ERP) 6.0
- SAP Adaptive Server Enterprise (ASE) 16.0
Product
SAP Adaptive Server Enterprise 16.0
Keywords
CR827332, CR#827332, 827332, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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.