Fatal NI connect error 12170

Hi,

I got ” Fatal NI connect error 12170 ” error in Oracle.

 

Details of error are as follows.

Fatal NI connect error 12170.

VERSION INFORMATION:
TNS for 64-bit Windows: Version 11.2.0.3.0 - Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.3.0 - Production
Time: 22-FEB-2014 12:45:09
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.63.34)(PORT=45679))

 

 

This error is related with the firewall exists between the client and the database server.

 

The fatal ni connect error 12170 is related with the ORA-12170 error, you can read the related post as follows.

TNS-12170: TNS: Connect timeout occurred

 

To solve this error, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values.

 

Add the following line to the sqlnet.ora file on the server.

SQLNET.EXPIRE_TIME=10

 

 

To revert to Oracle Net Server tracing/logging, set following parameter in the server’s sqlnet.ora :

DIAG_ADR_ENABLED = OFF

Also, to back out the ADR diag for the Listener component, set following parameter in the server’s listener.ora:

DIAG_ADR_ENABLED_<listenername> = OFF

Where the <listenername> would be replaced with the actual name of the configured listener(s) in the listener.ora configuration file.  For example, if the listener name is ‘LISTENER’, the parameter would read:

DIAG_ADR_ENABLED_LISTENER = OFF

 

Reload or restart the TNS Listener for the parameter change to take effect.

 

 

Do you want to learn Oracle SQL, then read the following articles.

Oracle SQL Tutorials For Beginners – Learn Oracle SQL from scratch with Oracle SQL Online Course