Symptom
- Application is sending a large amount of statements in a language batch with parameters.
- Eventually this causes Signal 11 in the module res_insert() followed by a stack trace:
Current Process is running on Engine 0
Address 0x0x0000000002d8a7a5 (res_insert+0x819), siginfo (code, address) = (1, 0x(nil)) - SQL causing error is a batch of multiple INDERTs into a #temp table:
SQL Text: insert into #temp_xxxxxx_xxxxxx values (@p131236,@p131237) insert into #temp_xxxxxx_xxxxxx values (@p131238,@p131239) insert into #temp_xxxxxx_xxxxxx values (@p131240,@p131241) insert into #temp_xxxxxx_xxxxxx values (@p131242,@p131243) insert into #temp_xxxxxx_xxxxxx values (@p131244,@p131245) insert into #temp_xxxxxx_xxxxxx values (@p131246,@p131247) insert into #temp_xxxxxx_xxxxxx values (@p131248,@p131249) in ... - Stack trace (on Solaris) contains these functions:
res_insert
yyparse
sqlpars
tdsrecv_language
Read more...
Environment
- SAP Adaptive Server Enterprise 15.7
- SAP Adaptive Server Enterprise 16.0
Product
SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0
Keywords
CR 825302, CR 825302, CR 825302, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Known Error
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