Symptom
- When running sp_sysmon or sp_monitor, a storage access violation error with a stack trace occurs, for example:
On Unix/Linux:
Current process (0x51c303da) infected with signal 11 (SIGSEGV)
Address 0x4000000002496aa0 (ind__get_sysindrow+0x400), siginfo (code, address) = (2, 0x0000000000000000)
On Windows:
Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation.
- The stack trace includes modules:
get_resrow_size
LopInsert::_lopCodeGen
Lop::lopCodeGen
GenLava
s_compile_stmt
Note: A complete stack trace is available under Attachments.
Read more...
Environment
SAP Adaptive Server Enterprise (ASE) 16.0
Product
Keywords
stacktrace, CR814910, CR#814910, 814910, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, registers, deferred, compilation, Light Weight Procedure, LWP , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , 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 for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.