Hi,
Is there any further development on the prevention of Toad from timing out connections from inactivity in Editor sessions?
I don’t think I’ve had this problem until v. 12.
I don’t see anything like a KEEPALIVE that would do the trick. I hate to have to leave Session Manager running all the time with constant refreshes.
Thx,
Dan
Afternoon Dan,
On 22/08/13 15:55, dmcgarve wrote:
Is there any further development on the prevention of Toad from timing
out connections from inactivity in Editor sessions?
Toad doesn't have a keep alive, not - as far as I'm aware - will it ever have one. This has always been the "problem" and as Bert will no doubt confirm - Hi Bert - Toad will never allow something to be done that may subvert security policies in the work place.
So, if you get cut off after inactivity, it's not Toad that's doing it, but the database. I suspect your DBA has either decided to incorporate a profile for your user that dumps you out after a certain period of inactivity.
I don't think I've had this problem until v. 12.
No, it has always been a "problem", much reported on the old mailing lists.
I don't see anything like a KEEPALIVE that would do the trick. I hate
to have to leave Session Manager running all the time with constant
refreshes.
You could ask your dba to set you up with a profile that has unlimited idle time? You can see what's whate if you run this, but you need to be able to access the DBA views:
select profile, resource_name, limit
from dba_profiles
where profile = (select profile from dba_users
where username = 'YOUR_USER_HERE')
order by resource_name;
You are looking for idle_time.
HTH
-- Cheers,
Norm. [TeamT]
Thanks Norm – I guess I’ve become a bit predictable – update stats and no keep alive.
My wife always says I’m set in my ways and inflexible – maybe she’s right
J
Bert
From: Norm [TeamT] [mailto:bounce-NormTeamT@toadworld.com]
Sent: Thursday, August 22, 2013 10:49 AM
Subject: Re: [Toad for Oracle - Discussion Forum] toad 12 disconnecting
Reply by Norm [TeamT]
Afternoon Dan,
On 22/08/13 15:55, dmcgarve wrote:
Is there any further development on the prevention of Toad from timing
out connections from inactivity in Editor sessions?
Toad doesn't have a keep alive, not - as far as I'm aware - will it ever
have one. This has always been the "problem" and as Bert will no doubt
confirm - Hi Bert - Toad will never allow something to be done that may
subvert security policies in the work place.
So, if you get cut off after inactivity, it's not Toad that's doing it,
but the database. I suspect your DBA has either decided to incorporate a
profile for your user that dumps you out after a certain period of
inactivity.
I don't think I've had this problem until v. 12.
No, it has always been a "problem", much reported on the old mailing lists.
I don't see anything like a KEEPALIVE that would do the trick. I hate
to have to leave Session Manager running all the time with constant
refreshes.
You could ask your dba to set you up with a profile that has unlimited
idle time? You can see what's whate if you run this, but you need to be
able to access the DBA views:
select profile, resource_name, limit
from dba_profiles
where profile = (select profile from dba_users
where username = 'YOUR_USER_HERE')
order by resource_name;
You are looking for idle_time.
HTH
--
Cheers,
Norm. [TeamT]
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - General notifications altogether.
Toad for Oracle - Discussion Forum
Flag
this post as spam/abuse.
I lost the office pool. I said you'd respond in < 45 min.
On Aug 22, 2013, at 1:08 PM, "Bert Scalzo" bounce-Bert_Scalzo@toadworld.com wrote:
Reply by Bert Scalzo
Thanks Norm – I guess I’ve become a bit predictable – update stats and no keep alive.
My wife always says I’m set in my ways and inflexible – maybe she’s right
J
Bert
From: Norm [TeamT] [mailto:bounce-NormTeamT@toadworld.com]
Sent: Thursday, August 22, 2013 10:49 AM
Subject: Re: [Toad for Oracle - Discussion Forum] toad 12 disconnecting
Reply by Norm [TeamT]
Afternoon Dan,
On 22/08/13 15:55, dmcgarve wrote:
Is there any further development on the prevention of Toad from timing
out connections from inactivity in Editor sessions?
Toad doesn't have a keep alive, not - as far as I'm aware - will it ever
have one. This has always been the "problem" and as Bert will no doubt
confirm - Hi Bert - Toad will never allow something to be done that may
subvert security policies in the work place.
So, if you get cut off after inactivity, it's not Toad that's doing it,
but the database. I suspect your DBA has either decided to incorporate a
profile for your user that dumps you out after a certain period of
inactivity.
I don't think I've had this problem until v. 12.
No, it has always been a "problem", much reported on the old mailing lists.
I don't see anything like a KEEPALIVE that would do the trick. I hate
to have to leave Session Manager running all the time with constant
refreshes.
You could ask your dba to set you up with a profile that has unlimited
idle time? You can see what's whate if you run this, but you need to be
able to access the DBA views:
select profile, resource_name, limit
from dba_profiles
where profile = (select profile from dba_users
where username = 'YOUR_USER_HERE')
order by resource_name;
You are looking for idle_time.
HTH
--
Cheers,
Norm. [TeamT]
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - General notifications altogether.Toad for Oracle - Discussion Forum
Flag
this post as spam/abuse.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - General notifications altogether.Toad for Oracle - Discussion Forum
Flag
this post as spam/abuse.
I missed the pool. Today is a good pool day though.
On 22/08/13 18:08, Bert Scalzo wrote:
Thanks Norm – I guess I’ve become a bit predictable – update stats and
no keep alive.
My wife always says I’m set in my ways and inflexible – maybe she’s right J
Bert
Nothing wrong in a bit of predictability Bert! And I bet you knew I would say that!
At least I was paying attention when you said your piece on keep-alive and updating stats!
-- Cheers,
Norm. [TeamT]
I can cope with connections timing out after a while - if that's how the database is set up - and wouldn't expect TOAD to implement a "keep alive" function to subvert it.
But given that it's possible for connections to be dropped, is there any chance TOAD could react to that gracefully, without producing bizarre display-related errors? For example, I've just queried across a dropped connection, and now I have a big grey area across the bottom of TOAD that I won't be able to get rid of without restarting.
This is one of the more benign bugs - sometimes it makes tabs invisible or makes menu dropdowns unusable. Sometimes it works fine. If there were just an option to repaint the screen from scratch, it might make it possible to clear some of these bugs without a restart.
[added] Not that it's actually possible to restart Toad after such an error without killing it off through Task Manager.
I guess the tough question – and I’m asking here, not trying to be smart – do you really want “every” piece of code throughout Toad to before talking to the
database to retest the connection before doing its thing. This really isn’t feasible from the coding side – but suppose for a moment it was. Do you really want to slow down the app orders of magnitude to retest the connection before every potential database
request?
I get your frustration – but would you not be more frustrated by things being much, much slower across the board to prevent this from occurring every now and
then ???
From: chris_4134 [mailto:bounce-chris_4134@toadworld.com]
Sent: Tuesday, August 27, 2013 6:52 AM
Subject: RE: [Toad for Oracle - Discussion Forum] toad 12 disconnecting
Reply by chris_4134
I can cope with connections timing out after a while - if that’s how the database is set up - and wouldn’t expect TOAD to implement a “keep alive” function to subvert it.
But given that it’s possible for connections to be dropped, is there any chance TOAD could react to that gracefully, without producing bizarre display-related errors? For example, I’ve just
queried across a dropped connection, and now I have a big grey area across the bottom of TOAD that I won’t be able to get rid of without restarting.
This is one of the more benign bugs - sometimes it makes tabs invisible or makes menu dropdowns unusable. Sometimes it works fine. If there were just an option to repaint the screen from scratch,
it might make it possible to clear some of these bugs without a restart.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - General notifications altogether.
Toad for Oracle - Discussion Forum
Flag
this post as spam/abuse.
I’m not frustrated by Toad’s not testing the connection before each query, I’m frustrated by the panoply of bizarre and annoying error behaviours it can display when a connection does go down.
Hi,
Disconnection has nothing with Toad but your network settings. Try the same with sqlplus, you’ll get the same disconnect results.
I have local database and leave Toad 12.x open for 10 hours and connection is still alive without any problems.
Brg
Damir Vadas
I’m well aware that it is the network settings that are shutting down the connection. The shutdown is nothing to do with Toad, and I don’t expect it to “fix” it.
What I do expect is for Toad to cope gracefully with a connection going down, without the panoply of bizarre error behaviours that can occur after a connection is lost. Just report the ORA-3114 and have done with it (maybe offering to reconnect while you’re at it). Don’t display big blank areas at the bottom of the window, cause icons to disappear, refuse to shutdown without recourse to File Manager, etc… Is that too much to ask?
I also encounterd this problem and found a solution. At Startup of Toad the Session Browser also has to be open all the time to keep the connection Alive. You can do this automatically by setting the Auto Open checkbox on. You do this in menu View/Toad Options/Windows and then to scroll down and find the Session browser and turn the Auto open checkbox on. 
