SAP Knowledge Base Article - Preview

2156962 - When should kill spid with force be used? - ASE 15.7 SP121

Symptom

  • Would like clarification on the "kill spid with force" option?
  • A stack trace after the kill with force command is used may be reported. 

terminate_process
TreeLogPropsN::treeLogPropsCompute(const TreeLogProps*,const TreeLogProps*)
EqcN::EqcN(BmLight<VbmGtIdHidden>*,EquivClass*,EquivClass*,OptBlock*)
EqcN*EqcN::eqcGet(EquivClass*,EquivClass*)
SeHyPermStrat::_SeHyPsPlaceGtGrdyOrder(Node<Lop>*,CniSet*,short**)
SeHyPermStrat::_SeHyPsInitJoinOrder(Node<Lop>*,OptPool*,short,CniSet*,short**)
SeHyPermStrat::SeInit()
OptBlockSearchEngineException
SearchEngine::SeFindOptimalOptBlockPlan()
SearchEngine::_SeFindOptimal()
OptGlobal::_GblSearchEngine(int*)
PopBase*OptGlobal::GblOptimize(int*)


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 15.7 SP 121 and above

Product

SAP Adaptive Server Enterprise 15.7

Keywords

terminate task, zombie process, processes holding resources, kill command failed , KBA , zombie process , sp_who , phantom locks , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

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.