Advantage of createEnvironment in Shared mode

Question

Hi,
Am looking for more information on what is shared when an environment is created in Shared mode.
We have a connection pool. For every task, a connection is made, statement is executed, statement is terminated and the connection is terminated. Next time the same task is executed, will there be any caching benefits from the previous execution?
Guessing that when you close the connection, all state is wiped out, hence there will be no advantage to the next guy?
Does creating an environment in shared mode keep some sort of statement cache?
Thanks much,
Nilofer

Answer 1

>>Am assuming I still need to do setStmtCacheSize(cacheSz).
All the Connections from a pool will inherit the statement cache size from the pool level setting. Everytime you get a session from a pool, it will have the stmt cache size set at the pool level. If you override that value by setting the stmt cache size on that Connection explicitly, tag that connection before you release it back to the pool, so that the stmt cache size value on that Connection is retained.
>>Do I also have to tag the statements? If I just do a terminateStatement(), since I have a statement cache, will the statement be automatically cached?
Yes. Tagging is not mandatory. It is useful for faster search.
>> On the same lines, if I do a createStatement(sql), will it return to me a statement matching the sql even though I don't provide the tag? (the documentation at http://download-west.oracle.com/docs/cd/B14117_01/appdev.101/b10778/reference008.htm#i1069559 suggests so)
Yes.
>>When should one tag the statements in a cache? To improve the search performance?
Yes.