SAP Knowledge Base Article - Preview

2198080 - Stored Procedure caught Signal 11 during INSERT - SAP ASE


  • A signal 11 is raised during an INSERT that is executed from a stored procedure:

Current process (0x42430ad9) infected with signal 11 (SIGSEGV)
Address 0x0x0000000000d3f2ac (bufclaimcache+0x33c), siginfo (code, address) = (128, 0x(nil))

  • Stack trace includes the followind modules:


  • A portion of the stored procedure and a SELECT INTO statement active at the point of failure:

SQL Text: sp_get_proddata
  @ct = 'universal'
, @oid = NULL
, @sio = NULL
Executing procedure: sp_get_proddata
Subordinate SQL Text:

SELECT  t.tik, t.tix, l.ce
INTO #hold
FROM abc t
    LEFT JOIN unit tt    ON tt.tik = t.tik
    LEFT JOIN lg l       ON t.lid = l.lid
WHERE t.oio = @oio
    AND sid = @sio
    AND tt.Token LIKE @ct + '.%'



SAP Adaptive Server Enterprise (ASE) 15.7 


SAP Adaptive Server Enterprise 15.7


CR787286, CR#787286, 787286, SEGV, segment, storage, access, violation, fault, segfault, kisignal, stacktrace, stack , KBA , 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 ONE Support launchpad (Login required).

Search for additional results

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