This content has been marked as final. Show 21 replies
In my alert log, I noticed this warning
WARNING: inbound connection timed out (ORA-3136) but thats a minute ago, not sure if thats a part of the problem thats causing ORA 03135
I checked the page and I do not know what kind of information I should look for in the v$Session and V$Process. The 2nd point highlighted in the page is about timeout parameters, is it only for idle connections or are there parameters also for active connections?
Please enlighten me on this.
Thanks a lot.
For ORA-3136 thisthread will be helpful
I will keep an eye on that error and see if it repeats. The error is to do with the connection time.
But, now, I desperately need to fix the developers' problem in using the database itself for development.
Could someone help me
Here is my sqlnet.ora (after including new parameters)
and I have turned on tracing and still I dont see any changes.
SQLNET.AUTHENTICATION_SERVICES = (NTS) SQLNET.EXPIRE_TIME = 4 SQLNET.INBOUND_CONNECT_TIMEOUT = 300 SQLNET.SEND_TIMEOUT = 300 SQLNET.RECV_TIMEOUT = 300 NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)
Its getting disconnected and nothing is being logged in alert log, trace files, and in listener.log, sqlnet.log
I think you may have more details if you enable tracing.
To do that you may add the following parameters on the sqlnet.ora from the Client of your Developers:
The link below will explain you the steps to follow:
trace_level_client=16 trace_file_client=cli trace_directory_client=C:\temp # Or a known directory trace_unique_client=true # Add '_pid' to trace filename
Then, when the error occurs you may check the trace file.
There's a tool to check the trace file ( trcasst ):
You may report here the result of this investigation or open a Service Request and send them the traces files with all the details about the error message you got.
Also, it's important to understand. Did it work before ? If yes which change in your information system happened (New PL/SQL code ? New Network component or configuration ? ).
Hope this help.
I am making the amendments as per your suggestion.
No, it has never worked before, we had a different web based system to work with the database server all this while but today its down so, we wanted to work using our client from the pc but we couldn't and we had the problem earlier but we were not so bothered as we had alternative ways.
Edited by: user645399 on May 26, 2011 5:24 PM