| Temporary TBS : Connection Pooling Clarification [message #59857] |
Tue, 30 December 2003 02:55  |
Vinny75
Messages: 44
Registered: October 2003
|
Member |
|
|
Folks,
We have application users who establish connection to the database via weblogic servers. None of the app users have database accounts. They get authenticated through the application (Web based) and once that is done, the weblogic spawns connection to the DB. But it also maintains the connection to the DB even after the ap user closes the browser based application (Caching purposes). Weblogic uses a standard DB account to make the connection and that account is shielded from user.
In this architecture, can some one explain how temp tables that are created during such sessions gets maintained? Since Temp Tables are available until the duration of the session, in my case the session is kept open even though the actual user closed the application. Since the actual DB connection is closed only when the weblogic servers are restarted, does this mean until then the temp objects are retained?
Thanks
|
|
|
|
| Re: Temporary TBS : Connection Pooling Clarification [message #59859 is a reply to message #59857] |
Tue, 30 December 2003 04:33  |
Thiru
Messages: 1089
Registered: May 2002
|
Senior Member |
|
|
depending on how your 'global temporary tables' are defined(ie transaction or session) ,they retain data until the transaction commits or until the session is terminated(in your case when the Weblogic servers are bounced).
In either case ,its Oracle session specific and is not aware of whats going on the front end.
-Thiru
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
