Re: Help: How to find the bad query

From: Orna Berlinsky <ornab_at_amdocs.com>
Date: 13 Jul 2001 23:47:16 -0700
Message-ID: <4e2fb3ee.0107132247.78e5e7c6@posting.google.com>

You should use a tool that will 'drill down' into the shared pool and dig out the problematic statements.

We have been using 'Precise' for that - and its quite good. You can see all the statements in the shared pool of your prodection DB and select the problematic ones ( according to duration , CPU usage and many more ), you can analyze the statements and re-tune them

There are other tools that can give you that ( SQL Patrol is another one )

Of course - you can always turn the SQL_TRACE for a day and go through the TKPROF file that was generated, but consider that this will probably slow the production DB even more that day.

Hope it helped
Orna Received on Sat Jul 14 2001 - 01:47:16 CDT