A good dicussion at freelist.ora

http://www.freelists.org/archives/oracle-l/08-2005/msg01627.html

In 10gR2, SQLNET.INBOUND_CONNECT_TIMEOUT the parameters were set to have a default of 60 (seconds).

Set the parameters SQLNET.INBOUND_CONNECT_TIMEOUT and INBOUND_CONNECT_TIMEOUT_listenername to 0 (indefinite).

Jaffar

What the error is telling you is that a connection attempt was made, but the session authentication was not provided before SQLNET.INBOUND_CONNECT_TIMEOUT seconds.

As far as adverse effects in the long run, you have a user or process that is unable to connect to the database. So someone is unhappy about the database/application.

Before setting SQLNET.INBOUND_CONNECT_TIMEOUT, verify that there is not a firewall or Network Address Translation (NAT) between the client and server. Those are common cause for ORA-3136.

The parameter is to be added in sqlnet.ora on the server, so wont require a shutdown.

Hi This is prasant.I'm new in database administration.I'm facing the same problem in my database.In the server i don't find sqlnet.ora file. but in the client m/c where my web apllication is installed and oracle client is installed i find sqlnet.ora file there.should i make the change in this file?

pls advise


Regards
prasant

installed and oracle client is installed i find
sqlnet.ora file there.should i make the change in this file?

You need to make change in server side , to over come this error.
If sqlnet.ora is not there on server side , then one can create it.


ORA-03136: inbound connection timed out

Cause: Inbound connection was timed out by the server because user authentication was not completed within the given time specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value

Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections. 2) Configure SQL*NET with a proper inbound connect timeout value if necessary.

WHEN this error occurs in a DATAGUARD environment, normally you don't have to worry about it. It happens, when connection between primary and standby side is lost temporarily or not yet established. Of course it should not happen too often.

Werner

I have tnsnames.ora in sever side and in proper location. but don't have sqlnet.ora. is it must i have to create this file at server die? should i have to do any configuration or register after making this file.?

That error also occures when remote user unable to login because of bad password and sqlnet.inbound_connect_timeout value reaches.

Hi

I have been tuning this parameter by setting different values, but all of a sudden since last week Im getting very frequent warning msgs. Is it possible which user or application is failed to authenticate itself towards the database. It will help a lot. Any clue which process is causing this error msg?

Thanks.

LSNRCTL> set help
The following operations are available after set
An asterisk (*) denotes a modifier or extended command:

password rawmode
displaymode trc_file
trc_directory trc_level
log_file log_directory
log_status current_listener
inbound_connect_timeout startup_waittime
save_config_on_stop dynamic_registration

LSNRCTL> set inbound_connect_timeout=0
NL-00853: undefined set command "inbound_connect_timeout=0". Try "help set"
LSNRCTL> set inbound_connect_timeout 0
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=SR253)(PORT=1521)))
LISTENER parameter "inbound_connect_timeout" set to 0
The command completed successfully
LSNRCTL>