This content has been marked as final. Show 2 replies
What value did you set for QueryThreshold? How long did the query actually run for? Had you set any non-default values for SQLQueryTimeout or TTC_TIMEOUT?
For client/server connections (but not for direct connections) there is a relationship between QueryThreshold, SQLQueryTimeout and TTC_TIMEOUT. Essentially, you must ensure that TTC_TIMEOUT is set larger than QueryThreshold / SQLQueryTimeout or that tTC_TIMEOUT is set to 0 (no timeout). By default (i.e. if not overridden), TTC_TIMEOUT=60 seconds and SQLQueryTimeout=59 seconds.
Thge mesage you received (6111) is as a result of SQLQueryTimeout and TTC_TIMEOUT firing.
Note that QueryThreshold does not control the execution time of a query - it simply logs a message and/or generates an SNMPO trap if any application query exceeds this limit. If you want to place an actual limit on the time a SQL operation (not just a query) may execute for then use SQLQueryTimeout and ensure that TTC_TIMEOUT is set sifgnificantly higher than the value used for SQLQueryTimeout since there is some 'fuzziness' around the firing of SQLQueryTimeout (e.g. if you set it to 59 then it may not fire until a query has run for 60 or even 61 seconds, maybe longer).
I find where I mistake!
TTC_Timeout parameter raise this error )))