Archives of the TeradataForum

Message Posted: Fri, 11 Nov 2005 @ 14:40:02 GMT

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

Terry,

Yes I had this exact same thing happen and opened an incident with NCR.

First, they said we should ensure long queryid support is on. If you don't have this on, you can view Knowledge Article S11000F442E. (I had it on.)

After much discussion I received this reply from engineering:

"There are instances where DBQL does not capture the SQL. Stored Procedures, sometimes the EXEC command, BT, ET, among other cases. I don't know how to characterize specific instances to the customer without looking at the SQL that is being run. Basically, if the SQL is not in the request context when the query finishes, we do not currently display it.

In addition to some specific SQL statements, some applications may also cause this phenomenon.

What percentage of the data does not have QueryText?

What is the magnitude of the problem for the user and what are they using this information for that they are concerned with the missing SQL? Can they identify some of the 2000 cases? In my analysis, I usually look at the QueryText that is before and after the missing information to determine why it is missing. And usually there is a good reason for it!

By the way, in V2R6.2 I will put the QueryText into the DBQLogTbl for error conditions."

So, for me, it ended with "Well, we don't really know what or why some stuff isn't logged. That is just the way it is."

If you do open an incident, you can refer them to RECBQTP85 to help you get through some of the initial stuff.

Good luck.

Steve Woodrow

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