Symptom
- Query time governor doesn't work as expected.
- In spite of setting MAX_QUERY_TIME to 45, many CURSOR sessions still run exceeding 45 minutes
- Example output:
- At 15:20, two old cursor sessions, Txnid =101635024& 101636597, were beyond MAX_QUERY_TIME.
There was no cancelled message in *.iqmsgl.
- At 15:20, two old cursor sessions, Txnid =101635024& 101636597, were beyond MAX_QUERY_TIME.
sp_iqconnection output ( 19/Oct 15:20 ) =>
ConnOrCursor,ConnHandle,...TxnID, ConnOrCurCreateTime, ... IQGovernPriority,CmdLine, ...
CONNECTION 61764 ... 101634982, Oct 19 2016 2:12:41. ... No command ....
CURSOR 61764 ... 101636597, Oct 19 2016 2:31:45. ... Running select ...
CURSOR 61764 ... 101635024, Oct 19 2016 2:20:46. ... Running select ...
Read more...
Environment
SAP IQ
Product
SAP IQ all versions
Keywords
"MAX_QUETY_TIME" , "ActiveReq", , KBA , BC-SYB-IQ , Sybase IQ , How To
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