Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Fatal NI connect error 12170 issue

zephyr223Jun 1 2010 — edited Jun 10 2010
Hi guys,
I posted this issue a while back, but go no response, so just hoping for some more feedback. In my alert log, I constantly receive this error:

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: 26-MAY-2010 13:05:04
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.168.X.XX)(PORT=2504))

One of metalinks suggestions is to set DIAG_ADR_ENABLED =OFF. My question is, will that really help and what really is the effect to turning that parameter off????

I usually have 150 users connected at a time to the database, and i am hearing there are a lot of time outs out there in the field...Not sure how to go about diagnosing this......The users are connecting via webservers and dmz so also not sure if i should be looking into setting up Connection Manager. Any help will be appreciated...
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 8 2010
Added on Jun 1 2010
10 comments
1,906 views