omcat Users List
Subject: RE: Tomcat/JDBC Thin Client and Oracle SQL Parsing
Thanks for the reply. I'm pretty sure we pinpointed the reason why
oracle was using the wrong indexes. Stats for the indexes weren't
updated since the 12th of January and when oracle re-parsed the query it
chose the
From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
Sent: Tuesday, January 26, 2010 11:55 AM
To: Tomcat Users List
Subject: RE: Tomcat/JDBC Thin Client and Oracle SQL Parsing
Dan -
I'd look into why Oracle took an "improper" index (whatever that means).
There is nothing in Tomcat/JD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
On 1/26/2010 12:40 PM, Dan Denton wrote:
> While it's possible there's something we missed, I would like to know
> if anyone out there knows why a webapp restart would cause the
> database to reparse and choose a new execution plan.
If the JDBC
2010/1/26 Dan Denton :
>
> Can anyone point out any instances they've had where Tomcat or Tomcat with
> the Oracle JDBC driver has exhibited similar behavior?
Is your JDBC driver up-to-date, or as old as the Tomcat version that
you are using? I once solved a thing by updating the driver.
Best re
Dan -
I'd look into why Oracle took an "improper" index (whatever that means).
There is nothing in Tomcat/JDK that would mess with your queries that
I'm aware of.
I'd also investigate all the standard reasons why Oracle recomputes
explain plans for queries - most of which are related to the query.
