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.
TNS for 64-bit Windows: Version
188.8.131.52.0 - Production
Oracle Bequeath NT Protocol Adapter for
64-bit Windows: Version 184.108.40.206.0 - Production
Windows NT TCP/IP NT Protocol Adapter
for 64-bit Windows: Version 220.127.116.11.0 - Production
Time: 28-MAY-2012 19:20:02
Tracing not turned on.
Tns error struct:
ns main err code: 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
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.
the error occurred because of a slow network or system,
reconfigure one or all of the parameters
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
"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.