SAP Knowledge Base Article - Preview

3406532 - Signal 11 in getnext() while executing a UNION ALL query - SAP ASE

Symptom

  • The message, "Current process infected with signal 11 (SIGSEGV)", in the module 'getnext' together with a stack trace may be reported in the SAP ASE error log when a query with UNION ALL is executed.

Current process (0x2b8f32b1) infected with signal 11 (SIGSEGV)
Address 0x0000000102483668 (getnext.fdpr.chunk.51+0x2c8), siginfo (code, address) = (50, 0x353735001e440015)

  • The error is accompanied by a stacktrace referencing the functions:

kisignal.fdpr.chunk.2
getnext.fdpr.chunk.51
LeRestrictOp::_LeOpNext.fdpr.chunk.23
LeRestrictOp::_LeOpNext.fdpr.chunk.23
LeUniAllOp::_LeOpNext.fdpr.chunk.1
LeUniAllOp::_LeOpNext.fdpr.chunk.1
LeEmitSndOp::_LeOpNext.fdpr.chunk.13
LePlanNext
exec_lava
s_execute.fdpr.chunk.101
sequencer
execproc
s_execute.fdpr.chunk.95
sequencer
tdsrecv_language


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 16.0

Product

SAP Adaptive Server Enterprise 16.0

Keywords

getnext, 828804, CR#828804, CR828804, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace, 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 for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.