SAP Knowledge Base Article - Preview

2630662 - Signal 11 in memmove() or __milli_memcpy() - SAP ASE 16.0

Symptom

  • After ASE is upgraded to ASE16.0 SP03 PL03.

  • A client session is terminated with an "Infected with signal 11" error in the module memmove() or __milli_memcpy(), for example:

    • on Linux:

      Current process (0x39001d) infected with signal 11 (SIGSEGV)
      Address 0x0x000000394e8838e7 (memmove+0xa7), siginfo (code, address) = (1, 0x(nil)) 
    • on HP-UX:
       
      Current process (0x3f330223) infected with signal 11 (SIGSEGV)
      Address 0x400000000755ab60 (__milli_memcpy+0x100)

  • The stack trace may include the following modules:

__milli_memcpy
LeAlignedDataRow::readRow
LeCacheRow::freeReadBuf
LeCacheRow:writeRow
LeSQCache::LeCacheInsert

  Note: Samples of complete stack traces are available under Attachments.

  • The problematic SQL has 'outer join' and the 'replicate' function.


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 16.0 SP03

Product

SAP Adaptive Server Enterprise 16.0

Keywords

SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace,  registers, 814478, CR814478, CR#814478, REPLICATE, traceflag, flag, 510 , 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 for Me (Login required).

Search for additional results

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