Our DBA will only allow a certain number of connections to the Oracle database.
In Toad Data Point, with no connections opened, no sessions are open.
One connection opened, one session is opened.
If that connection opens an editor, another session is opened.
It seems that one can close down all editors with only the connection open, and yet one cannot get back to only one session.
The lowest amount of sessions is two after launching an editor.
If subsequent editors are again launched, the numbers are incremented again properly.
If multiple editors are closed, the multiple sessions decrement to two open sessions.
Why are multiple sessions spawned and what’s the reasoning behind it?
Regarding the spawning of sessions, this is not a defect. Toad Data Point pools connections for optimization.
If sessions are being restricted, Toad Data Point advises users to have the ability to at least open three sessions.
If the user wants to reduce on connections, change to the Toad for Oracle configuration and then turn off the option shown below. It is on by default. (FYI: The navigation manager will be removed.)
NOTE: A message will appear, "Not using separate connections for each editor could cause problems if you run two scripts simultaneously from different editors that modify connection properties."
6. Click OK.
Below is a list of Toad Data Point utilities that will create their own connections:
Object Explorer
Data Grid
Editor
Query Builder
Export/Import
The connection count will climb as one uses these utilities. Once the connection is open, Toad Data Point leaves it open and if possible, tries to reuse it. There is no option to close and drop a connection after using it.
