Home » RDBMS Server » Networking and Gateways » alert log error Fatal NI connect error 12170 (HPUX: Version 11.2.0.2.0 )
alert log error Fatal NI connect error 12170 [message #518992] Mon, 08 August 2011 13:02 Go to next message
dba_7722
Messages: 197
Registered: August 2010
Location: Delhi
Senior Member

Hello,

with last upgrade on 11.2.0.2.0, we are getting one error.


Fatal NI connect error 12170.

  VERSION INFORMATION:
	TNS for HPUX: Version 11.2.0.2.0 - Production
	Oracle Bequeath NT Protocol Adapter for HPUX: Version 11.2.0.2.0 - Production
	TCP/IP NT Protocol Adapter for HPUX: Version 11.2.0.2.0 - Production
  Time: 08-AUG-2011 10:10:39
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12535
    
TNS-12535: TNS:operation timed out
    ns secondary err code: 12560
    nt main err code: 505
    
TNS-00505: Operation timed out
    nt secondary err code: 238
    nt OS err code: 0
  Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.25.55.73)(PORT=2338)) 


Doing so many Google, i din't have any right information for the error. Humbly request you to please focus on the error.
Re: alert log error Fatal NI connect error 12170 [message #518993 is a reply to message #518992] Mon, 08 August 2011 13:09 Go to previous messageGo to next message
BlackSwan
Messages: 23150
Registered: January 2009
Senior Member
OK, you have error.

When was last time SQL*Net worked without error?
What has changed?
What is done that throws these errors?
Does any SQL*Net operations succeed? if so, which?

>TNS-12535: TNS:operation timed out
can be caused by FireWall.
Does FireWall exist between client & DB?
Re: alert log error Fatal NI connect error 12170 [message #518996 is a reply to message #518993] Mon, 08 August 2011 13:40 Go to previous messageGo to next message
dba_7722
Messages: 197
Registered: August 2010
Location: Delhi
Senior Member

SQL *NET works for normal operation but at some moment of time, connection stop for the database. This is we have traced as got ticket from the client.

Database is recently given to our team, so not much knowledge for last time change happen. For firewall, i need to check with the other team.

Regards,
Jay vardhan
Re: alert log error Fatal NI connect error 12170 [message #518998 is a reply to message #518996] Mon, 08 August 2011 13:49 Go to previous message
BlackSwan
Messages: 23150
Registered: January 2009
Senior Member
You have a mystery & we have no clues.

use WireShark or Ethereal to packet sniff to learn where root cause of failure exists
Previous Topic: select for update - how to kill old locks
Next Topic: connectivity of sql server into oracle through heterogenius services
Goto Forum:
  


Current Time: Fri Dec 19 19:56:56 CST 2014

Total time taken to generate the page: 0.08590 seconds