ORA-3135 Fixed by PC Restart

From: Charlotte Hammond <charlottejanehammond_at_yahoo.com>
Date: Wed, 2 Oct 2013 12:07:42 -0700 (PDT)
Message-ID: <1380740862.4037.YahooMailNeo_at_web140006.mail.bf1.yahoo.com>

Hi All,

I've got a problem with a Windows 7 PC client ( which after a period of time (days/hours) starts throwing ORA-03135 (after a hang of about 20 seconds) when I try to connect to a particular database (   Restarting the PC always fixes the problem for a while but is not a convenient workaround.

It only happens on this one PC and against one target database.  (i.e. other PC's can connect to the problem DB, and also this PC can connect happily to other databases).  I've traced the client and listener but not seen anything helpful yet- just a 20 second gap in times on the client side before it fails, and a listener trace that stops dead on the disconnect.  I've tried changing the CONNECT_TIMEOUT to no avail and gone through the Oracle MOS doc on ORA-03135 troubleshooting.

Just wondering if this sounded familiar to anyone?   Just seems the fact that rebooting the PC fixes things suggests the problem lies there.  Both PC and Server are very, very lightly loaded. (A bit vague, I know, but just looking for guidance on where to look:  the client or the server?  Could it be a firewall issue? - there is a firewall in the path - but don't know why it would be intermittently failing to connect and the network guys aren't very interested so I'd need something more than a vague guess to get traction from them.  It's quite difficult to diagnose/fix when the problem is not readily reproducible).

Many thanks,
Received on Wed Oct 02 2013 - 21:07:42 CEST

Original text of this message