Thank you. This was exactly what I wanted to hear.
Unfortunately, since we already have connection pooling enabled (this is Windows platform with multithreaded Apache, we're able to persist the temporary table contents between requests - of course, this means we've been forced to build a system that allows us to identify each session's contents in the temp tables as they are shared among all "sessions") I believe mod_plsql calls dbms_session.reset_package
On the bright side; things could be worse. At least it's mostly soft parses the application is performing - I had just started the server, so that is why I experienced this one hard parse in my test. Under normal circumstances I'd expect the query to be always present in the library cache.
Main Topics
Browse All Topics





by: sdstuberPosted on 2007-12-13 at 22:03:16ID: 20469983
Yes, your analysis is correct, and 1 hard and 4 soft parses.
And yes, by the nature of your web app, you will most likely see a higher parse rate than a traditional client-server app with longer lasting sessions.
You may be able to ameliorate this symptom with connection pooling