Re: Re: TNS timeouts logged on server overnight (12535 12170 12560)

1) Let the developers close there Toad sessions? Is there a reason to let
them open? You can define a job where all Toad sessions are closed in the
night if they are not listening, but noone would be glad with that.
2) Those type of messages goes to the alert log. No choice there.

Groetjes,
   Wim


2011/10/11 Frank Bell <[email protected]>

> **
>
>
> Message from: FrankB
>
>
> No-one? Sigh.
>
> _______________________________________
>
> Historical Messages
>
>
> Author: Frank Bell
> Date: Tue Oct 11 02:22:32 PDT 2011
> No-one? Sigh.
> __
>
> Author: Frank Bell
> Date: Wed Oct 05 03:02:10 PDT 2011
> Hi, We're getting a bunch of TNS timeouts logged in our server's alert log
> that appear to be caused by Toad for Oracle Base v10.6.1.3 sessions. e.g.,
> Fatal NI connect error 12170. VERSION INFORMATION: TNS for Linux: Version
> 11.2.0.1.0 - Production Oracle Bequeath NT Protocol Adapter for Linux:
> Version 11.2.0.1.0 - Production TCP/IP NT Protocol Adapter for Linux:
> Version 11.2.0.1.0 - Production Time: 04-OCT-2011 19:13:10 Tracing not
> turned on. Tns error struct: ns main err code: 12535 TNS-12535:
> TNS:operation timed out ns secondary err code: 12560 nt main err code: 505
> TNS-00505: Operation timed out nt secondary err code: 110 nt OS err code: 0
> Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=whatever)(PORT=whatever)) Can
> anyone suggest where I can either 1) disable the timeout (developers on the
> test machine leaving sessions overnight) or 2) disable these errors from
> cluttering up the alert log? Thanks in advance, Frank
> __
> _______________________________________
>
>  
>