2435989 - Spid hung in 'remote i/o' with stack showing kctCheckAsync after kill - SAP ASE | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2435989 - Spid hung in 'remote i/o' with stack showing kctCheckAsync after kill - SAP ASE

Symptom

  • spid hangs showing sysprocesses 'status' = 'remote i/o'
  • or, after attempt to kill it, 'status' = 'runnable' and 'cmd' = 'MAINTENANCE TOKEN' :

select spid, status, cmd from master..sysprocesses
go

spid   status                                 cmd 
------  ----------------------------------  --------------
123   remote i/o                           COND 

123   MAINTENANCE TOKEN   runnable       -- after kill command

  • running dbcc stacktrace (spid#) on the problem will show stack including functions :
omni_ct_results
CtlibRemoteAccess::prepareResultSet
CtlibRemoteAccess::executeLanguage
RemoteAccess::prepareRemoteSQL

or after kill command

kctCheckAsync
ksct_startio
usctcancel
omni_ct_cancel
rdes_free
omnipss_free
dso_disconnect_handler
terminate_process

Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 15.7 SP13x
  • SAP Adaptive Server Enterprise (ASE) 16.0 SP02 PL0x

Product

SAP Adaptive Server Enterprise 15.7

Keywords

omni_ct_results+0x7e() , omni_ct_results+0x7e , CtlibRemoteAccess::prepareResultSet()+0x67() , CtlibRemoteAccess::prepareResultSet() , CtlibRemoteAccess::prepareResultSet()+0x67 ,
CtlibRemoteAccess::executeLanguage()+0x19a() , CtlibRemoteAccess::executeLanguage()+0x19a , CtlibRemoteAccess::executeLanguage() , RemoteAccess::prepareRemoteSQL(LeRemScanContext*, OmniSQL*)+0x133() , RemoteAccess::prepareRemoteSQL(LeRemScanContext*, OmniSQL*)+0x133() , (LeRemScanContext*, OmniSQL*) , LeRemScanContext*, OmniSQL* , kctCheckAsync+0x64 , ksct_startio+0xa0 , usctcancel+0xc , omni_ct_cancel+0x84 , rdes_free+0x1c , omnipss_free+0x164 , dso_disconnect_handler+0x4c , terminate_process+0x5f0 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , SAP Business Suite on Sybase ASE Database Platform , 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.