How to keep an Oracle session in TOAD 13, keep alive? Session Time Out

Toad for Oracle
1

TOAD version: 13.0.0.80

Database: Oracle 12.1.0.2 - RAC

Question: How to keep an Oracle session in TOAD 13, keep alive or avoid Session Time out?

Due to firewall, our session get disconnected frequently. I have 7 databases with lots of application, so it is a pain to log in every few minutes.

I have tired the “DBMS Output” - “Turn Output on” and that used to work before the version 13 but it does not work any longer. Not sure if it to do with TOAD version or something we need to check / change in TOAD Option

2

We don’t have any official timeout preventer, but there are places in Toad that run queries on regular intervals.

The Transactions window is one of them. It’s the button with the ? on the toolbar.

1 Like
3

Hello John,

Thank you for the response but I did not understand the solution. Please elaborate.

4

It’s not really a “solution” since we don’t want to provide a way to prevent timeouts (since they are there for a reason)…but…

If you open that window and leave it open, Toad will query run queries on whatever interval you set it to, so maybe you won’t get timeouts as often.

1 Like
5

Evening All.

For what it’s worth, I’m also stuck behind a timing out network setup.

I run my Toad 13 with separate sessions configured in the options. I usually have the session browser open (DBA option?) and on a 5 minute refresh as I’m invariably called on to ‘fix something’. Anyway, the editor sessions do still time out after 10 mins of inactivity but the session browser stays running, but, it too will eventually get dropped by the network and need a “session->test all sessions”. :frowning:

Basically, a keep alive doesn’t always work.

Cheers,

Norm. [TeamT]

–

Sent from my Android device with K-9 Mail. Please excuse my brevity.

6

The transactions window checks the main connection for a transaction, and if it doesn’t find a transaction, it will check background sessions. If it finds that a background connection is in transaction, it won’t continue checking background connections, for a given main connection, if there are any more.

-John

7

As a precaution, If I think (or know for sure) that it has been long enough for it to time out,I just always do (S)ession, (T)est Connections - Reconnect before I run anything. better safe than sorry.

On Fri, Jul 6, 2018 at 11:51 AM, Norm [TeamT] bounce-NormTeamT@toadworld.com wrote:

RE: How to keep an Oracle session in TOAD 13, keep alive? Session Time Out

Reply by Norm [TeamT]

Evening All.

For what it's worth, I'm also stuck behind a timing out network setup.

I run my Toad 13 with separate sessions configured in the options. I usually have the session browser open (DBA option?) and on a 5 minute refresh as I'm invariably called on to 'fix something'. Anyway, the editor sessions do still time out after 10 mins of inactivity but the session browser stays running, but, it too will eventually get dropped by the network and need a "session->test all sessions". :frowning:

Basically, a keep alive doesn't always work.

Cheers,

Norm. [TeamT]

--

Sent from my Android device with K-9 Mail. Please excuse my brevity.

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or Unsubscribe from Toad for Oracle Forum notifications altogether.

Toad for Oracle - Discussion Forum

Flag this post as spam/abuse.

--
Gene L. Bradley Jr.

Systems Analyst

Office of Information Technology

Jackson State University

1400 J R Lynch Street

P.O. Box 17750

Jackson, MS 39217

ph 601.979.1042

fax 601.371.9146

email gbradley@jsums.edu

*In God we trust; all others bring data. * ~W.E. Deming

CONFIDENTIALITY STATEMENT

This electronic transmission is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone (601) 979-1042. Thank you.

8

Wow - talk about making developers happy. I set a timer in the transaction refresh and I’m no longer cursing at Toad due to timeouts. Thank you!

1 Like