RE: Troubles with parses

Ciao Roberto

>I found an information that in JDBC 3.0 there is a "statement pool" =
concept.
>They try to use the JDBC 3.0 but the problem ( many soft parses that
>consume too much cpu)
>persists.

Do you mean "statement caching"? If yes, did you enable it with = setImplicitCachingEnabled()?=20
(in 9iR2 the statement caching interface has been changed, the "old" is = deprecated)

>Is there any way to resolve this problem?

>From the information you gave it's not possible to understand if the 208 =
parses are performed on with a single connection (i.e. each time you get = a connection you parse 208 times) or with multiple connections (i.e. = each time you get a connection you parse once).=20

If the former applies, you have to parse (prepare) a statement only once = and execute in many times. To workaround the problem "statement caching" = is a possibility.
=20
>There is a lot of "SQL*Net message to/from client" WAITS? Is this =
correlated
>with the many parses problems?

I see no relation.

HTH
Chris

--
http://www.freelists.org/webpage/oracle-l