SAP Knowledge Base Article - Preview

3235230 - Signal 11 in open__byname() when executing a procedure and 'deferred name resolution' is enabled - SAP ASE 16.0

Symptom

  • After a minor version upgrade from SAP ASE 16.0 SP03 PL09 to SAP ASE 16.0 SP03 PL12,
  • Executing a stored procedure fails with an "infected with signal 11" error in the module open__byname() followed by a stack trace:

Address 0x0x0000000001c1f9e6 (open__byname+0xa6), siginfo (code, address) = (1, 0x(nil))                     
Current process (0x407f04c9) infected with signal 11 (SIGSEGV)  

  • Stack trace contains these functions:                                 

open__byname                                                                
open_user_table
proc_get
s_getTreeOrPlan
pre__replace_cpc
pre__substitute_fi_cpc
pre__substitute_fi_cpc
pre_current_qry_vcpc_fi
pre_subq_vcpc_fi
pre__process_vcpc_fi
s_preprocess
s_compile

   Note: The complete stack trace is available under Attachments.


Read more...

Environment

  • SAP Adaptive Server Enterprise 16.0 SP03 PL12
  • RedHat Linux 8.3 

Product

SAP Adaptive Server Enterprise 16.0

Keywords

CR827009, CR#827009, 827009, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace,  registers, CR 819667, 11080
, 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.