Fatal NI connect error 12170
Hi Everyone,
Recently my users have been complaining about lots of TNS-12535: TNS:operation timed out or TNS-00505: Operation timed out. In checking the alert log, there are tons of timeouts occuring per day.
We have an application that is written using .net. This application connects from the "outside world" passing through a DMZ to the database. In doing some reading, i have come to the conclusion that i may need to setup connection manager, but not absolutely sure. Here is the error that is thrown on the timeouts found in the 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: 16-FEB-2010 12:21:22
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: 60
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.xxx.x.xx)(PORT=2046)) (the host ip address is the webserver ip address)
What i'm really looking for is some direction as to how to help with this problem or has anyone out there experienced this before and found a fix. Any help will be welcomed. Thanks in advance.