fatal ni connect error 12170 oracle что это

�����, �� ��� ����������,
�� � ������-�� �����, ��� � ������������ ������� ����������� ������,
� �� ����� ������������� ���������� � ��������

Fatal NI connect error 12170.

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=192.168.11.34)(PORT=2679))
WARNING: inbound connection timed out (ORA-3136)
Wed Apr 04 10:05:02 2012

Fatal NI connect error 12170.

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=192.168.11.33)(PORT=3125))
WARNING: inbound connection timed out (ORA-3136)
Wed Apr 04 10:07:23 2012

Fatal NI connect error 12170.

Источник

Fatal NI connect error 12547/12170

I am stakk with connection problem on customer Oracle server. Oracle database is installed on Microsoft Windows Server 2012 Standard. Version of Oracle DB is 11.2.0.4 Standard One Edition.

Oracle database works fine on server. I had no problems/errors while installing (as admin). My user is memer of Local Admin Group. I am also able to connect to it with sqlplus (sqlplus username/ [email protected] _alias) and SQL Developer.

Content of tnsnames, listener og sqlnet files are following:

tnsnames.ora

ORACLR_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) )
(CONNECT_DATA = (SID = CLRExtProc) (PRESENTATION = RO) ) )

SALES =
(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.9)(PORT = 1521))
(CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sales.company.se)))

listener.ora

SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc) (ORACLE_HOME = \oracle\product\11.2.0\dbhome_1)
(PROGRAM = extproc) (ENVS = «EXTPROC_DLLS=ONLY:D:\oracle\product\11.2.0\dbhome_1\bin\oraclr11.dll») ) )

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = servername.company.se)(PORT = 1521))

(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))))

ADR_BASE_LISTENER = \oracle

sqlnet.ora

ADR_BASE = \oracle\product\11.2.0\dbhome_1\log

I am using VPN tunnel to connect to database from my client. I can ping server successfully. TNSPING to database works fine, but I am not able to connect to database. I get an error on client:

ORA-12537 connection closed error.

Alert log content is following:

Fatal NI connect error 12547, connecting to:
(LOCAL=NO)

TNS-12547: TNS:lost contact
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (88) as a result of ORA-609
2013-12-19 13:05:28.990000 +01:00

Fatal NI connect error 12170.

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:
opiodr aborting process unknown ospid (2384) as a result of ORA-609
2013-12-19 13:44:44.855000 +01:00
opiodr aborting process unknown ospid (1292) as a result of ORA-609
2013-12-19 14:30:34.351000 +01:00

I supposed that connection could use some more time so I set inbound_connection to 180 (3 minutes). Same error.

Then I turn on support trace. Here is analyzed content:

Trying to get IP client address results in error. Host IP is not correct.

[19-DEC-2013 13:42:35:692] nsgetclientaddress: Client address: «(ADDRESS=(PROTOCOL=tcp)(HOST=::1)(PORT=53749))»
[19-DEC-2013 13:42:35:692] nsgetclientaddress: exit
[19-DEC-2013 13:42:35:692] nszgclient: entry
[19-DEC-2013 13:42:35:692] nszgclient: using dedicated context
[19-DEC-2013 13:42:35:692] nazsgsnm: entry
[19-DEC-2013 13:42:35:692] nau_genm: entry
[19-DEC-2013 13:42:35:692] nau_genm: exit
[19-DEC-2013 13:42:35:692] nazsgsnm: failed with error 12630
[19-DEC-2013 13:42:35:692] nazsgsnm: exit
[19-DEC-2013 13:42:35:692] nszgclient: returning no username
[19-DEC-2013 13:42:35:692] nszgclient: returning no username
[19-DEC-2013 13:42:35:692] nszgclient: exit
[19-DEC-2013 13:42:35:692] nszgetuser: entry
[19-DEC-2013 13:42:35:692] nszgetuser: using dedicated context
[19-DEC-2013 13:42:35:692] nazsgunm: entry
[19-DEC-2013 13:42:35:692] nau_gnm: entry
[19-DEC-2013 13:42:35:692] nau_gnm: exit
[19-DEC-2013 13:42:35:692] nazsgunm: failed with error 12630

Getting package from client. And when reached to @ we get EOF (daflag=64)

[19-DEC-2013 13:42:35:724] nttfprd: exit
[19-DEC-2013 13:42:35:724] nsbasic_brc: type=6, plen=10
[19-DEC-2013 13:42:35:724] nsbasic_brc: what=1, tot =10
[19-DEC-2013 13:42:35:724] nsbasic_brc: packet dump
[19-DEC-2013 13:42:35:724] nsbasic_brc: 00 0A 00 00 06 00 00 00 |. |
[19-DEC-2013 13:42:35:724] nsbasic_brc: 00 40 |.@ |
[19-DEC-2013 13:42:35:724] nsbasic_brc: Got EOF (daflag=64).
[19-DEC-2013 13:42:35:724] nserror: entry
[19-DEC-2013 13:42:35:724] nsbasic_brc: exit: oln=0, dln=0, tot=10, rc=-1
[19-DEC-2013 13:42:35:724] nioqer: entry
[19-DEC-2013 13:42:35:724] nioqer: incoming err = 12151
[19-DEC-2013 13:42:35:724] nioqce: entry
[19-DEC-2013 13:42:35:724] nioqce: exit
[19-DEC-2013 13:42:35:724] nioqer: returning err = 3113
[19-DEC-2013 13:42:35:724] nioqer: exit
[19-DEC-2013 13:42:35:724] nioqrc: exit
[19-DEC-2013 13:42:35:724] nioqds: entry
[19-DEC-2013 13:42:35:724] nioqds: disconnecting.

Handshake never succeded. Client was trying to read from transport but never succeeded. I assume it is because of wrong or non Client address: «(ADDRESS=(PROTOCOL=tcp)(HOST=::1)(PORT=53749))»

After 180 sec Oracle net sends following message:

[19-DEC-2013 13:44:44:855] nsclose: normal exit
[19-DEC-2013 13:44:44:855] nserror: entry
[19-DEC-2013 13:44:44:855] nserror: nsres: op=73, ns=12535, ns2=12606; nt[0]=0, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
[19-DEC-2013 13:44:44:855] nsinherit: error exit
[19-DEC-2013 13:44:44:855] nioqper: error from nsinherit: failed.
[19-DEC-2013 13:44:44:855] nioqper: ns main err code: 12535
[19-DEC-2013 13:44:44:855] nioqper: ns (2) err code: 12606
[19-DEC-2013 13:44:44:855] nioqper: nt main err code: 0
[19-DEC-2013 13:44:44:855] nioqper: nt (2) err code: 0
[19-DEC-2013 13:44:44:855] nioqper: nt OS err code: 0
[19-DEC-2013 13:44:44:855] niotns: No broken-connection function available.
[19-DEC-2013 13:44:44:855] niomapnserror: entry
[19-DEC-2013 13:44:44:855] niqme: entry
[19-DEC-2013 13:44:44:855] niqme: reporting NS-12535 error as ORA-12535
[19-DEC-2013 13:44:44:855] niqme: exit
[19-DEC-2013 13:44:44:855] niomapnserror: exit
[19-DEC-2013 13:44:44:855] niotns: Couldn’t connect, returning 12170
[19-DEC-2013 13:44:44:855] nioqer: entry
[19-DEC-2013 13:44:44:855] nioqer: incoming err = 12170
[19-DEC-2013 13:44:44:855] nioqce: entry
[19-DEC-2013 13:44:44:855] nioqce: exit
[19-DEC-2013 13:44:44:855] nioqer: returning err = 3136

Firewall is off on Server. Network administrator says that there is no rules which could compromise communication/traffic on port 1521. I tried trcroute too and I get following conntent

1 27ms 22 ms 17ms 192.168.97.1

2 * * * request aborted

3 20 ms 18 ms 18 ms server.company.se (192.168.1.9)

Any suggestion, help or comments would be appriciated. I am running out of ideas.

Источник

fatal ni connect error 12170

Пользователи не могут подключиться к базе. Обычно при этом они получают ошибки: ORA-12547: TNS:lost contact или ORA-12637: Packet receive failed.

В sqlnet.log на сервере сообщения об ошибке ORA-12170: TNS:Connect timeout. Еще для версий 10g и выше, в alert.log могут быть сообщения WARNING: inbound connection timed out (ORA-3136).

VERSION INFORMATION:
TNS for 64-bit Windows: Version 10.2.0.4.0 — Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 10.2.0.4.0 — Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 10.2.0.4.0 — Production
Time: 13-FEB-2013 13:47:12
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=10.77.116.47)(PORT=2971))
***********************************************************************

Для разных ОС, параметр ‘nt secondary err code‘ может быть разным

For the Solaris system: nt secondary err code: 145:
ETIMEDOUT 145 /* Connection timed out */
For the Linux operating system: nt secondary err code: 110
ETIMEDOUT 110 Connection timed out
For the HP-UX system: nt secondary err code: 238:
ETIMEDOUT 238 /* Connection timed out */
For AIX: nt secondary err code: 78:
ETIMEDOUT 78 /* Connection timed out */
For Windows based platforms: nt secondary err code: 60 (which translates to Winsock Error: 10060)

Выдержка из документации

ORA-12170: TNS:Connect timeout occurred
Cause: The server shut down because connection establishment or communication with a client failed to complete within the allotted time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the server.
Action: If the error occurred because of a slow network or system, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If a malicious client is suspected, use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (e.g. in TCP/IP).

Смысл этой ошибки в том что соединение не может быть установлено в течение отведенного интервала времени. А вот причин по которым это происходит может быть великое множество.

Как видно, основная рекомендация — увеличить параметры SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT и SQLNET.RECV_TIMEOUT. Можно попробовать сделать это, но это может не помочь. Поэтому лучше попробовать разобраться в корне проблемы.

Несколько основных причин ошибки и способы их решения

1) Серверные ресурсы перегружены.

Проверить насколько загружен сервер (процессор, диски, сеть). Выявить причину утечки ресурсов и устранить её. Большая загрузка сети может косвенно указывать на DoS. Если вы обнаружили высокую нагрузку сервера, но она оказалась полезной — то это указывает на нехватку мощности сервера и пора задуматься об его обновлении или замене.
©Bobrovsky Dmitry
2) Проблемы сети.
©Bobrovsky Dmitry
Если есть возможность проверить сетевой канал от клиента до сервера с помощью специализированых аппаратных или программных средств. Если нет, то можно запуститесь ping на некоторое время и посмотреть, какое время отклика и нет ли потерь пакетов.

3) База данных и Listener не функционируют.

Проверить что сама база данных и Listener запущены и работают нормально, что к ним можно подключиться локально или с других компьютеров сети.
Dmitry Bobrovsky
4) Проблемы из-за антивируса или firewall.
Dmitry Bobrovsky
Отключить или даже полностью деинсталировать антивирус или firewall.

5) Проблемы с DNS.

Либо прописать соответствующие записи в файл host либо во всех конфигурационных файлах oracle net использовать вместо имен — ip-адреса.
Запись fatal ni connect error 12170 ns main err code 12535 впервые появилась Dmitry Bobrovsky Blog

I am getting error ORA-12170 while connecting from C# application to Oracle database. I searched and found somewhere that the error description can be found in sqlnet.log file. What I am pasting is the sqlnet.log content. How can I overcome this problem?

Fatal NI connect error 12170.

VERSION INFORMATION: TNS for 32-bit Windows: Version 10.2.0.1.0 — Production Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 10.2.0.1.0 — Production Time: 08-JUN-2016 18:49: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:

Question: Below error getting in alert log file every day, but database is working fine
What are the reason for this Fatal ni connect error 12170?

Fatal NI connect error 12170.

VERSION INFORMATION:
TNS for 64-bit Windows: Version 11.2.0.1.0 — Production
Oracle Bequeath NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 — Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 11.2.0.1.0 — Production
Time: 28-MAY-2012 19:20:02
Tracing not turned on.
Tns error struct:
ns main err code: 12535

TNS-12535: TNS:operation timed out
ns secondary err code: 12560

Answer: The fatal ni connect error 12170 is related to the ORA-12170 error:

ORA-12170: TNS:Connect timeout occurred

Cause: The client failed to establish a connection and complete authentication in the time specified by the SQLNET.INBOUND_CONNECT_TIMEOUT parameter in the sqlnet.ora file. This error may be a result of network or system delays, or it may indicate that a malicious client is trying to cause a denial-of-service attack on the database server.

The server shut down because connection establishment or communication with a client failed to complete within the allotted time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the server.

Action: If the error occurred because of a slow network or system, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If a malicious client is suspected, use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (e.g. in TCP/IP).

See Also:
«Configuring the Listener and the Oracle Database To Limit Resource Consumption By Unauthorized Users» for further information about setting the SQLNET.INBOUND_CONNECT_TIMEOUT parameter

Action: If the error occurred due to system or network delays that are normal for the particular environment, then perform this steps:

Turn on tracing to determine where clients are timing out.

Burleson is the American Team

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata? Oracle technology is changing and we strive to update our BC Oracle support information. If you find an error or have a suggestion for improving our content, we would appreciate your feedback. Just e-mail:

and include the URL for the page.

The Oracle of Database Support

Copyright © 1996 — 2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Источник

Вам также может понравиться

Урок мудрости: почему грязного и вода не очистит, чистый в огне не сгорит

Привет, друзья! Сегодня мы с вами поговорим о замечательной

Поговорка ‘Кто не работает, тот и не ест’: Зачем нужно учиться и трудиться

Привет, дорогие дети! Сегодня я хочу рассказать вам

Загадочная поговорка: Имеющий дойную корову всегда будет иметь сметану

Дорогие дети, сегодня мы поговорим о загадочной поговорке «

Поговорим о поговорке: почему давшему быка на убой не дали для поджарки и легкого

Привет, дорогие дети! Сегодня мы поговорим о забавной