Symptom
- When a query is performing GroupHashing,
- Error 632 is reported in the ASE errorlog:
Error: 632, Severity: 20, State: 2
Attempt to move memory with an incorrect length of 18216. Maximum allowed length is 16384.
- Or an "infected with signal 11" error in the module LeAlignedDataRow::readRow() followed by a stack trace is reported in the ASE errorlog:
Current process (0x350d0431) infected with signal 11 (SIGSEGV)
Address 0x0x000000000087970b (LeAlignedDataRow::readRow(unsigned char*, LeVtuple*, LeDRReadMode, int, int, int*)+0xa7), siginfo (code, address) = (128, 0x(nil))
- The stack trace that comes with Signal1 may include functions:
LeAlignedDataRow::readRow
LeHashBufferReader::GetNext
LeHashOFileOp::_LeOpNext
LeHashContext::GetNext
LeHashOp::_LeOpNext
Note: A sample of a complete stack trace is available under Attachments.
Read more...
Environment
SAP Adaptive Server Enterprise (ASE) 15.7 SP134
Product
Keywords
CR806999,CR#806999, 806999, corrupted, plan, group_hashing, group, hashing, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace, registers , 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.