Symptom
A customer seems that Query time governor doesn't work as expected.
In spite of setting MAX_QUERY_TIME to 45, many CURSOR sessions from COGNOS still run exceeding 45 minutes.
Following is sp_iqconnection output from customer server.
When the sp was called at 15:20, two old cursor sessions, Txnid =101635024& 101636597,
were still working by passing MAX_QUERY_TIME. There was no cancelled message in *.iqmsg at all.
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 16,
SAP IQ 15.4
Product
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.