SAP Knowledge Base Article - Preview

2936447 - Signal 11 in ubffreef() when RepAgent is scanning syslogs during SUM upgrade - SAP ASE

Symptom

  • The SUM upgrade failed due to an "Infected with signal 11" error in the module ubffreef() with a stack trace hit by RepAgent:

Current process (0x51d0024) infected with signal 11 (SIGSEGV)
Address 0x0x00000000016e05d2 (ubffreef+0xe2), siginfo (code, address) = (128, 0x(nil))

  • The stack trace shows the following functions:

ubffreef 
ra_free_mempool 
ra__schema_dealloc_obj 
ra_schema_dealloc 
ra_invalidate_schema 
ra__process_xobjinfo 
ra_process_lr
ra__ci_scanner_scan
ra__ci_scanner_scan_and_distribute
ra__ci_scanner_execute
ra_ci_scanner_thread

  Note: A complete stack trace is available under Attachments.

  • The ASE server crashed as a result of the RAMEM_SPIN spinlock unreleased by a terminated RepAgent process (spid):

Spinlocks held by kpid 85786660
Spinlock RAMEM_SPIN at address 0x000000014399ba00 owned by 85786660


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7 and 16.0
  • SAP Replication Server (SRS) 15.7

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0 ; SAP Replication Server 15.7

Keywords

SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stack, registers, CR807722, CR#807722, 807722, rs_marker, CR763637, CR#763637, 763637 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-REP , Sybase Replication Server (standalone) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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.