Symptom
A process was in "latch sleep" status since was waiting to get a buffer latch. Tried to kill it, but it could not be killed:
======
Killing spid: XXXX will not be immediate because it is waiting for a latch held by spid: YYYY.
======
Process that was holding the latch didn't exist. It was a phantom process. There are not errors related to this process on ASE's log.
The stack for process waiting to get the buffer latch:
======
kpsuspend
upsleepgeneric
buf_get_latch
bufsearch_cache_getlatch
getpage_with_validation
pg__fetch_lock_validate
pg_getdatapage_forinsert
dol_data_insert
dol_insert
ins_insert
insert_all
.....
.....
.....
=======
Read more...
Environment
SAP Adaptive Server Enterprise 16.0 SP03 PL15
Product
Keywords
killing,will not be immediate because it is waiting for a latch held by spid,latch sleep,buf_get_latch,bufsearch_cache_getlatch,getpage_with_validation,pg__fetch_lock_validate,pg_getdatapage_forinsert,830948, CR 830948 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , Problem
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.
SAP Knowledge Base Article - Preview