RE: tracking down hidden SQL???

From: Jonathan Lewis <>
Date: Wed, 16 Oct 2013 19:42:50 +0000
Message-ID: <CE70217733273F49A8A162EE074F64D901DC5DC7_at_exmbx05.thus.corp>

Just throwing in a wild guess here - Dan't suggestion is the smart thing to do - but if the prev_sql_id is always for "select silly_thing from dual" which you're sure is just a connection pool test then it's possible that the invisible statement is just a "rollback" (or "rollback;" or "Rollback" or ... ).

Jonathan Lewis

From: [] on behalf of Adric Norris [] Sent: 16 October 2013 20:15
To: Chris Taylor
Cc: oracle-l
Subject: Re: tracking down hidden SQL???

On Wed, Oct 16, 2013 at 2:05 PM, Chris Taylor <> wrote:
> Did you try querying [g]v$session PREV_SQL_ID as well for those sessions
> that are showing the SQL_ID you're interested in? (Kerry mentioned it in
> that blog post). The prev_sql_id might give you a clue about why this
> sql_id is showing up as the current one?

The previous PREV_SQL_ID is always identical, but is unfortunately just a connection pool session-test query.

select 2+2 from dual

I appreciate the suggestion!

Received on Wed Oct 16 2013 - 21:42:50 CEST

Original text of this message