OraFAQ Forum: Networking and Gateways » ORA-3136 freequently in oracle db alert log file

Home » RDBMS Server » Networking and Gateways » ORA-3136 freequently in oracle db alert log file (oracle 11g , Windows)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

ORA-3136 freequently in oracle db alert log file [message #487853]

Sun, 02 January 2011 23:05

pradies
Messages: 250
Registered: May 2008

Senior Member

Hi,

I am facing below error so freequently in alert log file

Fatal NI connect error 12170.

VERSION INFORMATION:
TNS for 64-bit Windows: Version 11.1.0.6.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.1.0.6.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.1.0.6.0 - Production
Time: 03-JAN-2011 02:00:00
Tracing not turned on.
Tns error struct:
ns main err code: 12535

TNS-12535: TNS:operation timed out
ns secondary err code: 12606
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.2.45.169)(PORT=3824))
WARNING: inbound connection timed out (ORA-3136)

How to Resolve this error ??

Regards

Pradeep

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #487855 is a reply to message #487853]

Sun, 02 January 2011 23:19

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

>How to Resolve this error ??

Is any type of Operating System Virtualization installed on this system.

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #487858 is a reply to message #487855]

Sun, 02 January 2011 23:56

pradies
Messages: 250
Registered: May 2008

Senior Member

Hi,

There is not any Operating System Virtualization. There is only one host OS/ Base OS on which the oracle 11g Database is running.

OS is Windows 2003 Server
Oracle 11g Database

Regards

Pradeep

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #487860 is a reply to message #487858]

Mon, 03 January 2011 00:04

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

>How to Resolve this error ??

When was last when all was OK?
What has changed since then?

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #487862 is a reply to message #487860]

Mon, 03 January 2011 00:15

pradies
Messages: 250
Registered: May 2008

Senior Member

Hi,

According to Current Situation I am looking this error in alert log file from last week. and before the last week we have only reorgnized the db in terms of tablespaces and objects

Nothing Else at db level. and application as per the preformatted running in currently.

Regards

Pradeep

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #487980 is a reply to message #487862]

Mon, 03 January 2011 23:25

ramoradba
Messages: 2457
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...

Senior Member

1) Any changes to the following at server side ?

listener.ora: INBOUND_CONNECT_TIMEOUT_listenername
sqlnet.ora: SQLNET.INBOUND_CONNECT_TIMEOUT

2) Are you able to ping your server(host)?

Sriram

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #487982 is a reply to message #487980]

Tue, 04 January 2011 00:01

pradies
Messages: 250
Registered: May 2008

Senior Member

Hi Sriram,

When I saw this error first time then I placed a parameter SQLNET.INBOUND_CONNECT_TIMEOUT=120 in sqlnet.ora file.

Yes I am able to ping host using hostname and ipaddress also from outside and inside.

Regards

Pradeep

Attachment: sqlnet.ora
(Size: 0.49KB, Downloaded 2466 times)

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #487992 is a reply to message #487982]

Tue, 04 January 2011 00:40

ramoradba
Messages: 2457
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...

Senior Member

Why you need that SQLNET.INBOUND_CONNECT_TIMEOUT?
what about INBOUND_CONNECT_TIMEOUT_listenername?
and if you don`t need them then make it to 0 .

sriram

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #487997 is a reply to message #487992]

Tue, 04 January 2011 01:04

pradies
Messages: 250
Registered: May 2008

Senior Member

Hi,

According to metalink note id 793259.1 I placed the same SQLNET.INBOUND_CONNECT_TIMEOUT parameter in sqlnet.ora.

But I placed this parameter when I got the same error in alert log file. not before then.

and I didn't placed the parameter INBOUND_CONNECT_TIMEOUT_listenername in listener.ora. Confirm If I can place this parameter in listener.ora?

Regards

Pradeep

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #488002 is a reply to message #487997]

Tue, 04 January 2011 01:17

ramoradba
Messages: 2457
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...

Senior Member

http://download.oracle.com/docs/cd/B28359_01/network.111/b28317/sqlnet.htm#CIHCCCHD

The time specified should depend on the speed of your Network/System.

Inbound connection error occurs only when the clients failed to connect in the specified time.
And along with that check your Firewall changes too.

Good luck
sriram

[Updated on: Tue, 04 January 2011 01:19]

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #488156 is a reply to message #488002]

Wed, 05 January 2011 05:43

pradies
Messages: 250
Registered: May 2008

Senior Member

Hi,

According to link provided by you I have changed the Parameter and added one parameter in listener.ora. parameters are

INBOUND_CONNECT_TIMEOUT_LISTENER = 20
SQLNET.INBOUND_CONNECT_TIMEOUT = 30

I will be back again if the same problem persist.

Regards

pradeep

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #488157 is a reply to message #488156]

Wed, 05 January 2011 05:49

ramoradba
Messages: 2457
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...

Senior Member

Quote:

I will be back again if the same problem persist.

Quote:

The time specified should depend on the speed of your Network/System.

Think about it..You are On Your Own.

Sriram

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #488174 is a reply to message #488157]

Wed, 05 January 2011 07:34

pradies
Messages: 250
Registered: May 2008

Senior Member

Hi,

Kindly tell me how can I measure the value to be set for both parameters.

Regards

Pradeep

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #488205 is a reply to message #488174]

Wed, 05 January 2011 11:34

ramoradba
Messages: 2457
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...

Senior Member

Quote:

Inbound connection error occurs only when the clients failed to connect in the specified time.
And along with that check your Firewall changes too.

You said..at server side(I guess)
Quote:

SQLNET.INBOUND_CONNECT_TIMEOUT=120 in sqlnet.ora file.

So Your client request are taking more than 120 sec.If you decrease it you may get more no of errors again.If you really dont want to get the errors and dont want the in bound configuration parameters then remove it or make/set it to 0.

SO what you have to do is..
1) check whether if there is any firewall behind it causing the (slow) issues..
or any network issues..
2) Consult your DBA because we are not working on "your" environment.
MAx we can do is giving suggestions/hints.

Good luck
Sriram

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #488256 is a reply to message #488205]

Wed, 05 January 2011 22:21

pradies
Messages: 250
Registered: May 2008

Senior Member

Hi Sriram,

Thanks for suggesations ,

One more thing If I am changing sqlnet parameter SQLNET.INBOUND_CONNECT_TIMEOUT to 0 then what should be the value for INBOUND_CONNECT_TIMEOUT_LISTENER or should we remove the parameter from listener.ora file.

Regards

Pradeep

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #488273 is a reply to message #488256]

Thu, 06 January 2011 00:58

ramoradba
Messages: 2457
Registered: January 2009
Location: AndhraPradesh,Hyderabad,I...

Senior Member

Quote:

One more thing If I am changing sqlnet parameter SQLNET.INBOUND_CONNECT_TIMEOUT to 0 then what should be the value for INBOUND_CONNECT_TIMEOUT_LISTENER or should we remove the parameter from listener.ora file

If you don`t have any reason to specify/hold those parameters
1) Either you can delete/remove them(both) completely
or
2) Quote:

2) Consult your DBA

Sriram

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #488280 is a reply to message #488273]

Thu, 06 January 2011 02:12

pradies
Messages: 250
Registered: May 2008

Senior Member

Hi,

Okie I will check after removing both the parameters from files.

thank you
Pradeep

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #488767 is a reply to message #488280]

Tue, 11 January 2011 02:11

pradies
Messages: 250
Registered: May 2008

Senior Member

Hi,

After removing the both parameter Still the errors coming in alert log file. According to my post http://www.orafaq.com/forum/m/488579/124309/#msg_488579 I have already tries with parameter DIAG_ADR_ENABLED setting in sqlnet.ora file. But the still problem same.

pradeep

Report message to a moderator

Re: ORA-3136 freequently in oracle db alert log file [message #488840 is a reply to message #488767]

Tue, 11 January 2011 09:00

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

does error occur upon initial connection request?
Is connection requested & successfully completed & then error occurs at a later time?

Report message to a moderator

Previous Topic:	Listener issue
Next Topic:	TNS-12537: TNS:connection closed on client side

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Jan 04 17:40:36 CST 2025