Symptom
- When BCP data OUT on Linux and BCP IN on AIX or BCP data OUT and BCP IN on the same platform,
- ASE errorlog reports an "infected with signal 11" error 11 in the module bt__check_insert_position() with a stack trace, for example:
Current process (0x1bf904e7) infected with signal 11 (SIGSEGV)
Address 0x0000000101c804a0 (bt__check_insert_position+0x4c), siginfo (code, address) = (50, 0x00041ed800041ed8)
- When BCP data OUT on Linux and BCP IN on AIX, the stack trace may include the following modules:
bt__check_insert_position
bt_insert
bulk_fast_idxupdate
bulk_fast_row
LeBulkOp::_LeOpOpenHelper
LeBulkOpOpenMain
- When BCP data OUT and BCP IN on the same platform, the stack trace may include the following modules:
bt__check_insert_position
bt__traverseandinsert
bt_insert
bulk_fast_idxupdate
bulk_fast_row
LeBulkOp::_LeOpOpenHelper
LeBulkOpOpen
LeEmittOp::_LeOpOpen
LePlanOpen
exec_lava
bulk_main
Read more...
Environment
SAP Adaptive Server Enterprise (ASE) 15.7 and 16.0
Product
Keywords
CR800520, CR#800520, 800520, stacktrace, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, sortorder, nocase, 12311, traceflag, trace, flag , 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.
SAP Knowledge Base Article - Preview