Symptom
- An "infected with signal 11" error with the address in the module yylex() appears in the ASE errorlog:
kernel Current process (0x6de1014e) infected with signal 11 (SIGSEGV)
kernel Address 0x00000000019c9404 (yylex+0xaa34), siginfo (code, address) = (1, 0x0000002000000008)
- A user process (spid) which caused the signal 11 is reported as a zombie task in the ASE errorlog:
kernel task 1843462478 is zombie
- ASE unexpectedly shuts down.
- The executing SQL contains large amounts of whitespace between SQL keywords in a stored procedure or execute immediate statement.
- A stack trace following the error may include functions:
yylex
yyparse
sqlpars
internal_sql
s_execute
Note: A complete stack trace is available under Attachments.
- This problem can also be seen in the form of multiple errors, followed by a stack trace.
-
Error: 718, Severity: 20, State: 1
Memory allocation from process private memory is being performed by an incorrect process. Current Spid: 'xxx'. Owning Spid: '0'. Memory: '0xxxxxxxxx'. This is an Adaptive Server internal error. Please contact SAP Tech Support. - Error: 719, Severity: 20, State: 1
The last prochdr value is not available for the prochdr '0x10000207800'. This is an Adaptive Server internal error. Please contact Sybase Tech Support.
-
Error: 706, Severity: 20, State: 3
Process xxx tried to remove PROC_HDR 0xxxxxxxxx that it does not hold in Pss. - A stack trace following the error message may include the following functions:
rm_prochdr
memfree
pars_release_resources
pars_hdl
memalloc
yylex
yyparse
sqlpars
internal_sql
s_readparseProcText
Read more...
Environment
- SAP Adaptive Server Enterprise (ASE) 16.0 SP03 PL04 and SP03 PL05
- SAP Adaptive Server Enterprise (ASE) 15.7 SP140
Product
Keywords
kisignal, stacktrace, registers, crash, crashes, ueshutdown, CR816352, CR#816352, 816352, SEGV, segmentation, storage, access, violation, fault, segfault , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , 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.