SAP Knowledge Base Article - Preview

2546130 - Signal 11 in startscan() when executing SELECT FOR UPDATE involving MVCC - SAP ASE 16.0

Symptom

  • A client connection is unexpectedly terminated while executing a SELECT FOR UPDATE query involving MVCC.
  • An infected with signal 11 error in the module startscan() followed by a stack trace is reported in the ASE errorlog:

Current process (0x7f0040) infected with signal 11 (SIGSEGV)
Address 0x0x0000000001b0462d (startscan+0xd), siginfo (code, address) = (1, 0x0x0000000000000044)

  • The stack trace includes the following functions:

LeWkTbl::rewindWkTbl
LeCache::LeCacheNext
LeScrContext::updCacheStat
LeInsScrOp::_LeOpOpen

  Note: A complete stack trace is available under Attachments.


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 16.0 SP03 
  • On-Disk Multiversion Concurrency Control (MVCC)

Product

SAP Adaptive Server Enterprise 16.0

Keywords

Sybase, SEGV, segment violation, storage access violation, kisignal, CR808784, CR#808784, 808784, stacktrace , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , 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.