SAP Knowledge Base Article - Preview

2944143 - Signal 11 in apl__startscan() when LOAD DATABASE runs for a db dump with IMRS data - SAP ASE 16.0

Symptom

  • When LOAD DATABASE is run for a database dump that contains IMRS data,
  • An "infected with signal 11" error or a storage access violation exception in the module apl__startscan() followed by a stack trace may be reported in the ASE errorlog:

    • on UNIX /Linux

      Current process (0x35001b) infected with signal 11 (SIGSEGV)                                               

      Address 0x0x0000000001531e36 (apl__startscan+0x6d13), siginfo (code, address) = (1, 0x0x0000000000000092) 
       
    • on Windows
       
      Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation.
      ...
      pc: 0x00000000005C13C3 apl__startscan+...
  • The stack trace includes functions:

apl__startscan
startptnscan
xsc__sysimrslogs_setscan
xls_startscan
imrslogrec_redo_log
recovery
lddb_main

  Note: A sample of a complete stack trace is available under Attachments.


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 16.0
  • In-Memory Row Storage (IMRS)

Product

SAP Adaptive Server Enterprise 16.0

Keywords

CR809392, CR#809392, 809392, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace, registers, CR#809624, CR809624, 809624 , 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.