SAP Knowledge Base Article - Preview

3035352 - Signal 11 on ord_getrowbounds - SAP ASE

Symptom

Zombie process after process being aborted due stack trace with signal 11 on ord_getrowbounds:

=====

kisignal
ord_getrowbounds
ord_rowformat
ord_lockscheme
r_mktarglist
opt_reformat
decision
optimize_cmd
s_optimizecmds
decision_subq
decision_all
optimize_cmd
s_optimizecmds
s_ap_compat_gen
ApPlan::_apGenCompatibilityAp
ApPlan::_apGenBasicOptimizationAp
ApPlan::ApGreedyApply
OptGlobal::_GblSearchEngine
PopBase*OptGlobal::GblOptimize
Optimize
s_compile_stmt
s_compile
sequencer
0x0000000080738158 execproc
s_execute
sequencer

=====

In the stack trace we can see the functions related to compatibility mode which indicates the old optimizer is being Invoked:

=====

s_ap_compat_gen
ApPlan::_apGenCompatibilityAp

====

We can see this function in the stack trace: ApPlan::ApGreedyApply

Alternative greedy algorithm is being used. Compatibility mode optimizer has been used by default for queries joining more than six tables.


Read more...

Environment

SAP ASE 16.0 SP03 PL08

Product

SAP Adaptive Server Enterprise 16.0

Keywords

ord_getrowbounds ord_rowformat ord_lockscheme r_mktarglist opt_reformat s_ap_compat_gen ApPlan::_apGenCompatibilityAp ApPlan::_apGenBasicOptimizationAp ApPlan::ApGreedyApply CR 824355 CR824355 CR#824355 , 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 ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.