ORA-03135: in 11gR1
Rajeshwaran, Jeyabal, September 08, 2010 - 12:27 pm UTC
Tom:
We are using 11gR1 (11.1.0.6.0) client to connect with Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 server.
When connecting to the server from my machine, I am facing this below error if my connection is idle for 7 min's
rajesh@10GR2> select * from dual;
select * from dual
*
ERROR at line 1:
ORA-03135: connection lost contact
Process ID: 0
Session ID: 130 Serial number: 21071
ERROR:
ORA-03114: not connected to ORACLE
But however the same is not happening with my colleague machine connecting to the same Oracle server using the same 11gR1 (11.1.0.6.0) client and idle for even more than 1 hour. Is that some improper configuration with my machine Tom?
ORA-03135: in 11gR1
Rajeshwaran Jeyabal, November 22, 2010 - 11:22 am UTC
Tom:
Do you have any solution to this problem? I am still facing this issue, because of this i am unable to run long-running Transactions in database. Please help.
November 23, 2010 - 1:05 pm UTC
the only time I've seen this is because of a network policy that forced a connection closed after some period of time or some period of inactivity.
If you call a stored procedure that runs for a long time - you will appear "inactive" on your network.
contact your network administrator, I believe you'll find a "time out" policy in place
(or just open a sqlplus session and let it sit for a while - it should time out as well - without doing anything)
did you try the suggestion above? the original answer I gave? you don't say what you have or have not done
ORA-03135: in 11gR1
Rajeshwaran Jeyabal, November 24, 2010 - 1:46 am UTC
Tom:
Basically the DBA is not intrested in setting expire_time in the sqlnet.ora. Since this problem exists only in my machine ( Windows XP professional verson 2002 Service Pack 3) and not with others. I fell that this is a network issue in my machine and working with network Guys.
I believe you'll find a "time out" policy in place
Do you have any idea on how to control this "time out" policy. If yes please help.
November 24, 2010 - 9:02 am UTC
I'm not a windows person, especially not on such old software. You have a firewall or some network rule in place that is timing you out - problem is *not* in the oracle software - it is in your network setup somewhere. That would be a place I'm not really qualified in - especially not on an 8 year old windows install.
llll
A reader, November 09, 2017 - 4:20 am UTC
kkk
Khaled, May 29, 2025 - 5:44 pm UTC
Hi,
We have the same situation, we did timeout in firewall for 24h, but my session is closed after 1H, I changed to add expire_time in my sqlnet, now it works, but is it the best solution, or should i investigate more of the issue source?
June 03, 2025 - 1:36 am UTC
Thanks Connor for the answer
Khaled, June 03, 2025 - 12:27 pm UTC
Thanks Connor for your reply