Re: ORA-3135 Fixed by PC Restart
- From: Charlotte Hammond <charlottejanehammond@xxxxxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 2 Oct 2013 14:14:34 -0700 (PDT)
________________________________
From: Charlotte Hammond <charlottejanehammond@xxxxxxxxx>
To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Sent: Wednesday, October 2, 2013 10:12 PM
Subject: Fw: ORA-3135 Fixed by PC Restart
Hi Tim / List,
I'm getting ORA-03135 from JDBC (SQL*Developer v.3.0). Using SQL*Plus instead
returns (when it fails) ORA-01041: internal error hostdef extension doesn't
exist. The errors occur at the same time on SQL*Developer and SQL*Plus so
these appear to be different manifestations of the same problem.
I've discounted a load problem on the database as other PC clients are not
having this problem, the server is practically idle, and the session fails to
connect after just 20 seconds, not the CONNECT_TIMEOUT value I specified (of
several minutes). This, along with the fact that a PC restart fixes it, is
why I think the problem is on the client side. But equally the client can
still connect to all other databases fine while having a problem with just this
one. Which leaves me confused...!
Charlotte
----- Forwarded Message -----
From: Tim Gorman <tim@xxxxxxxxx>
>>To: oracle-l@xxxxxxxxxxxxx
>>Date: Wed, 02 Oct 2013 13:21:18 -0600
>>
>>
>>Charlotte,
>>
>>Is this ever happening when connecting using SQL*Plus from the PC in
>>question? Or is it only from an application? If so, what is the
>>application using for connectivity? Is it ODBC, JDBC, or a straight-out
>>Oracle OCI/TNS connection?
>>
>>The reason that the ORA-3135 happens is because there are a few
>>preliminary SQL statements that
execute before the database connection
>>is
considered "established", and delays in processing those SQL
>>statements might overrun the configured timeout. Some of the causes of
>>the ORA-3135 originate within the database, but there is no reason why
>>it couldn't also be the client-side PC that is not responding
>>appropriately and promptly. Hence the questions about the nature of the
>>client program.
>>
>>Thanks!
>>
>>
>>
>>________________________________
>> From: Charlotte Hammond <charlottejanehammond@xxxxxxxxx>
>>To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
>>Sent: Wednesday, October 2, 2013 8:07 PM
>>Subject: ORA-3135 Fixed by PC Restart
>>
>>
>>
>>Hi All,
>>
>>I've got a problem with a Windows 7 PC client (11.2.0.1) 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 (11.2.0.3).
>>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,
>>Charlotte
>>
>>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
