Re: Strange wait for what should be a fast query

I thought about that, and have asked to see the source code. However, the
timestamp from the FETCH to the WAIT shows a difference of 2906027257.
Doesn't that mean that it waited that long after the FETCH was issued? Or am
I interpreting that incorrectly?

And a bonus question: how do you decode the driver id? It is not hex.
Convert to hex from decimal?

On 12/19/06, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx> wrote:


 It looks like the query is fast - only .01 seconds, but Oracle was just
waiting for the application to issue the fetch call.  Is there something
delaying the fetch, like the user clicking on the [Next Record] button, or
something like that.

Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions
and other information in this message that do not relate to the official
business of this company shall be understood as neither given nor endorsed
by it.





--
Charles Schultz

Other related posts: