Package State Retained After Session Released To Homogeneous Session Pool
(Doc ID 260388.1)
Last updated on APRIL 09, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
We are using homogeneous session pooling __WITHOUT__ tagging.
Testing demonstrates when a session is released to the pool unchanged. In other words, all outstanding transactions and package state
(global variables in packages) are still visible when the session is reacquired.
At this point the result is 1, not 0.
A similar thing could be done for package variables. We have to make a call to
rollback() to rollback any outstanding changes and a call to
dbms_session.reset_package() to reset package state.
The documentation states session pools yield stateless sessions.
Testing indicates session pool instances are extremely stateful.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!