Symptom
- SAP NetWeaver-based application (BW applications, Solution Manager) on SAP ASE systems are unresponsive and do not accept new connections.
- Existing connections fail with the following ST22 dumps:
Category Resource Shortage
Runtime Errors DBIF_REPO_SQL_ERROR
Date and Time 03.11.2017 09:20:05
Error Text of the Database: "[ASE Error SQL30046:08S01][SAP][ASE ODBC Driver]Connection to the server has been lost. Connection died while reading from socket. ERRNO returned 0. Check the server to determine the status of any open transactions."
Triggering SQL Statement: "CX_RS_SQL_ERROR_SILENT========CP "
- The developer trace shows the same error:
C dbdssyb: DBSL99 SQL30046
C [ASE Error SQL30046:08S01][SAP][ASE ODBC Driver]Connection to the server has been lost. Connection died while reading from socket
B ***LOG BY2=> sql error 30046 performing OPC [dbds 398]
B ***LOG BY0=> [ASE Error SQL30046:08S01][SAP][ASE ODBC Driver]Connection to the server has been lost. Connection died while readin
B ***LOG BY1=> sql error 30046 [dbacds 1843]
C ERROR: -1 in function StartSelect (execute) [line 22552]
C (30046) [08S01] [SAP][ASE ODBC Driver]Connection to the server has been lost. Connection died while reading from socket. ERRNO returned 0. Check the server to determine the sta..
- The ASE errorlog reports one or more corresponding errors accompanied by signal 11 stacktrace errors:
Error: 21, Severity: 20, State: 1
WARNING - Fatal Error 718 occurred at Nov 3 2017 9:20AM. Please note the error and time, and contact a user with System Administrator (SA) authorization.
Error: 718, Severity: 20, State: 1
Memory allocation from process private memory is being performed by an incorrect process. Current Spid: '96'. Owning Spid: '679'. Memory: '0x0x2fad75800'. This is an Adaptive Server internal error. Please contact SAP Tech Support.
Thread (spid=96) initiating parallel primary error processing.
Error: 21, Severity: 20, State: 1
WARNING - Fatal Error 719 occurred at Mar 13 2019 2:40PM. Please note the error and time, and contact a user with System Administrator (SA) authorization.
Error: 719, Severity: 20, State: 1
The last prochdr value is not available for the prochdr '0x0x315507000'. This is an Adaptive Server internal error. Please contact SAP Tech Support.
Thread (spid=161) initiating parallel primary error processing.
Current process (0xbb005e) infected with signal 11 (SIGSEGV)
Address 0x0x0000000001499c88 (LeHashContext::HB1stOpen(ExeCtxt&)+0x84), siginfo (code, address) = (1, 0x0x00000000000003f0)
Current process (0x617f0335) infected with signal 11 (SIGSEGV)
Address 0x0x0000000001f4c433 (LeHashContext::Open(ExeCtxt&)+0x373), siginfo (code, address) = (1, 0x(nil))
- The stack trace references the following functions:
memalloc
LeHashOp::LeHashOp
LeHashOp::_LeOpNext
LeHashContext::Open
LeHashPartition::AddBuffer
LeHashPartition::Flush
Note: Samples of errors with complete stack traces are available under Attachments.
- In some cases, preceding Error 540 is encountered on the offending Infocube (where queries fail with above 718, 719 errors):
Error: 540, Severity: 16, State: 1
Schema for database object '/BI0/FCUBE' has changed since compilation of this query. Please re-execute query.
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite
- SAP Business Warehouse - All versions
- SAP Solution Manager 7.x
- SAP NetWeaver - All versions
Product
Keywords
Fatal Error, 718, 719, parallel, plldegree, signal 11, CR804836, CR#804836, 804836, Resource Shortage, parallelism, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace , KBA , BW-SYS-DB-SYB , BW 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.