Re: global temporary table and connection pooling

http://asktom.oracle.com/pls/ask/f?p=4950:8:2524853494752269270::NO::F4950_P 8_DISPLAYID,F4950_P8_CRITERIA:4541826681375, Just because it is a multipart query doesn't mean you have to "on commit preserve rows". Do your multipart using the same session/connection and rows from the first query will still be there.

Change the table to on commit delete, and make sure your session gets committed or rolled back after use.

"Barnoit" <jbarney_ca_at_yahoo.ca> wrote in message news:cd2c60c8.0403050904.3988e24c_at_posting.google.com...
> The environment I'm running is apache/tomcat and oracle 816. I'm using
> global temporary tablespaces in certain cases( they were created using
> on commit preserve rows option as it is a multipart query), and then
> the table is truncated after the last query has executed. I've noticed
> that occasionally if I run two independent queries using 2 different
> sessions, and the second query accesses the temp table before the
> first session has truncated it, I'm seeing results from the first
> session. I thought that the global temporary tables were supposed to
> be restricted to the session. Does this have anything to do with
> connection pooling? Any help/ideas would be greatly appreciated.
Received on Fri Mar 05 2004 - 11:45:44 CST