SAP Knowledge Base Article - Preview

3194320 - REP: infected with 11 at lt_notify_flush - SAP ASE


SEGV in lt_notify_flush and due to spinlock being held, ASE crashed.
Stack trace:
no significant errors prior to this only login failures.
Current process (0x6fdd03f6) infected with signal 11 (SIGSEGV) Current Process is running on Engine 8 server is using elf symbols for stack decoding (125557 symbols found) Address 0x0x0000000000bd29de (lt_notify_flush+0x14f), siginfo (code, address) = (1, 0x0x0000000000000004) Spinlocks held by kpid 1876755446 Spinlock Dbt->dbt_repl_context.repl_spinlock at address 0x00000001488cfa80 owned by 1876755446 ******** End of stack trace, spid 166, kpid 1876755446, suid 254 End of spinlock display. ... kisignal+0x87e() lt_notify_flush+0x14f() xls_flush+0x339() syslogs_flushlog+0x35() finishlog+0x175() xact__endxact+0x177() xact__commitxact+0x234() xact__commit_local+0x130() xact_commit+0x75() s_execute+0x1bfd() ... end of stack trace, spid 166, kpid 1876755446, suid 254 ueshutdown: exiting



Adaptive Server Enterprise 16.0 SP03 & SP04


SAP Adaptive Server Enterprise 16.0


CR826427, CR#826427, 826427, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace,  stack, registers , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BW-SYS-DB-SYB , BW on Adaptive Server Enterprise , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Problem

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.