Symptom
- ASE errorlog reports (many) Error 632 with a stack trace:
Error: 632, Severity: 20, State: 2
Attempt to move memory with an incorrect length of 25640. Maximum allowed length is 16384.
- Stack traces can include memmove(), memmove_error() and/or txcomp__getplaintxt(), for example:
memmove_error
txcomp__getplaintxt
sendimgblks
text_handler
sendtext
LeSendRow::_sendColsToClient
LeSendRow::sendRowToClient
LeEmitSndOp::_LeEoRouteResults
LeEmitSndOp::_LeOpNext
Note: Full example of errors and stack traces in attached file KBA_632_Stacks_Example.txt
- In some cases, Error 632 may be followed by a signal 11 at address kbfalloc() or ubffreef():
Current process (0x442b0118) infected with signal 11 (SIGSEGV)
Address 0x0x0000000002212e8d (kbfalloc+0x80d), siginfo (code, address) = (128, 0x(nil))
-
The respective stack traces for these Signal 11 errors include:
kbfalloc
ubfallocf
createpool_n_alloc
memallocheap
txcomp__init_cpct
txcp_const_to_txpgs
inserttext
updatetext
updtext
ubffreef
txcomp__cleanup
text_handler
sendtext
- These signal 11 may in turn crash the ASE server when hitting secondary signal failure :
FATAL UNHANDLED EXCEPTION: signal 11 hit while handling a previously hit signal. The server cannot continue and will shut down.
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite
- SAP Enterprise Resource Planning (ERP) 6.0
Product
Keywords
632, memmove, txcomp__getplaintxt, sendtext, LeSendRow::_sendColsToClient, LOB, CR#823684, CR 823684, CR823684, 823684 , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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