Archives of the TeradataForum

Message Posted: Fri, 29 Oct 2010 @ 18:32:00 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Hi gurus,

I detected recently a strange thing in my DBQL table. The queries from 3rd-party applications (SAS and OBI to be precise) are logged twice in the DBQL table:

- once with no activity (CPU, Steps, Spool, IOs - everything is = 0). I will call this one a "ghost" query

- right after the "ghost" query, the real one is executed.

Moreover, the "ghost" query can take up to 50 minutes (eventhough it is only miliseconds most of the time). They both come from the same session and the real one has StartTime equal to LastRespTime of the "ghost".

Let me give you an example. I do not paste the querytext, but I do reassure you it is the same query and this occurs systematically, for each 3rd-party query.

     SessionID AppID       StartTime              FirstStepTime          LastRespTime            NumSteps TotalCPUTime   ErrorCode
     --------- ----------- ---------------------- ---------------------- -------- -------------- -------- -------------- ----------
        547959 NQSSERVER   2010-10-04 13:08:17.73 2010-10-04 13:58:18.04 2010-10-04 13:58:23.98         0          0.000          0
        547959 NQSSERVER   2010-10-04 13:58:23.98 2010-10-04 14:00:01.05 2010-10-04 14:46:18.80       197        859.683          0

As you can see, the elapsedtime of the ghost query would be around 50 minutes and it does not do anything. As I said, most of the time, it is only few miliseconds, but the principle is killing me. Any suggestions why I have systematically 2 lines in DBQL for 1 third-party request?

Thanks and regards,

Tomas Gorner

	<Prev	Next>		<<First	<Prev	Next>	Last>>