Symptom
- ASE errorlog reports a signal 11 in function open_range, optimize or tabvar_release
- When running a query that uses a table variable, for example:
INSERT INTO @tabvar (xxxxxxx) SELECT yyyyyyyyy FROM tb01 - ASE may crash as a result of the subsequent error handling
- The pattern is usually in 2 stages :
- A signal 11 at one of the above functions, for example
Current process (...) infected with signal 11 (SIGSEGV)
Address 0x0x000000000xxxxxxx (open_range+0x111) ... or
Address 0x0x0000000000849890 (tabvar_release+0x81)... or
Address 0x0x000000000yyyyyyy (Optimize+0x11f) ...
followed by a stack trace that may include
open_range
open_one_side
s_preprocess
tmp_alldrop
s_free
s_pop - A second signal 11 is reported while error handling the first. This is usually seen on tabvar_release function
Address 0x0x00000000001111e (tabvar_release+0x78) ... - Depending on the setting for 'secondary signal handling
ASE can crash reporting
FATAL UNHANDLED EXCEPTION: signal 11 hit while handling a previously hit signal. The server cannot continue and will shut down.
or it reports a zombie spid
Task is made zombie due to unsuccessful clean up during its termination, kpid 11111111, state 1. This task may have resources allocated to it.
Read more...
Environment
SAP Adaptive Server Enterprise (ASE) 16.0
Product
SAP Adaptive Server Enterprise 16.0
Keywords
select table, tabvar_release, variable 828237, CR 828237, CR828237, CR#828237, tabvar, variable table, declare table, kisignal, open_range, open_one_side, s_preprocess, s_compile, sequencer , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , 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