Re: Find / Kill Sessions Running Duplicate SQL with Duplicate Bind Var. Values?
From: Stefan Koehler <contact_at_soocs.de>
Date: Sat, 20 Feb 2016 09:46:14 +0100 (CET)
Message-ID: <1395410827.69626.1455957974970.JavaMail.open-xchange_at_app02.ox.hosteurope.de>
Hi Jack,
you may have just missed my suggestion with an errorstack trace. It is not a simple SQL like "SELECT * FROM" … but it can be scripted completely (one query, several errostack trace calls, grep and compare). Is something wrong with this approach in your env?
Date: Sat, 20 Feb 2016 09:46:14 +0100 (CET)
Message-ID: <1395410827.69626.1455957974970.JavaMail.open-xchange_at_app02.ox.hosteurope.de>
Hi Jack,
you may have just missed my suggestion with an errorstack trace. It is not a simple SQL like "SELECT * FROM" … but it can be scripted completely (one query, several errostack trace calls, grep and compare). Is something wrong with this approach in your env?
"The currently used bind variables can be dumped with an errorstack trace as it includes cursor information. Afterwards you have to grep the binds and compare for all the corresponding processes which are running the particular SQL. This is how it would technically work, …"
Best Regards
Stefan Koehler
Freelance Oracle performance consultant and researcher
Homepage: http://www.soocs.de
Twitter: _at_OracleSK
> Jack Applewhite <jack.applewhite_at_austinisd.org> hat am 19. Februar 2016 um 22:33 geschrieben:
>
> Still looking...
>
> ----
> Jack C. Applewhite - Database Administrator
> Austin I.S.D. - MIS Department
> 512.414.9250 (wk)
>
-- http://www.freelists.org/webpage/oracle-lReceived on Sat Feb 20 2016 - 09:46:14 CET