Home » RDBMS Server » Server Administration » Fatal NI connect error (11g, 11.2.0.4, aix)
Fatal NI connect error [message #647784] Mon, 08 February 2016 01:14 Go to next message
ashishkumarmahanta80
Messages: 231
Registered: October 2006
Location: kolkatta
Senior Member
Dear All,

Now a days, I am getting below error at production database's alert. Please let me know, whether it is purely related to networking issue?
Though, In awr report, it come at last Top 10 Foreground Events by Total Wait Time.

Mon Feb 08 12:40:03 2016
Thread 1 cannot allocate new log, sequence 67751
Checkpoint not complete
  Current log# 2 seq# 67750 mem# 0: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo02a.log
  Current log# 2 seq# 67750 mem# 1: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo02b.log
Mon Feb 08 12:40:08 2016


***********************************************************************

Fatal NI connect error 12170.

  VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
  Time: 08-FEB-2016 12:40:08
  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: 110
    nt OS err code: 0
  Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.16.102)(PORT=63557))
Mon Feb 08 12:40:14 2016
Thread 1 advanced to log sequence 67751 (LGWR switch)
  Current log# 5 seq# 67751 mem# 0: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo05a.log
  Current log# 5 seq# 67751 mem# 1: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo05b.log
Mon Feb 08 12:40:14 2016
Archived Log entry 68360 added for thread 1 sequence 67750 ID 0xf94a7787 dest 1:
Thread 1 cannot allocate new log, sequence 67752
Checkpoint not complete
  Current log# 5 seq# 67751 mem# 0: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo05a.log
  Current log# 5 seq# 67751 mem# 1: /database/oracle/app/oracle/oradata/XYZDB/XYZDB/redo05b.log


Waiting for your valuable inputs...

Regards,
Ashish Kumar Mahanta
Re: Fatal NI connect error [message #647785 is a reply to message #647784] Mon, 08 February 2016 01:34 Go to previous messageGo to next message
John Watson
Messages: 7673
Registered: January 2010
Location: Global Village
Senior Member
That Fatal NI message is not a problem, ignore it.

The checkpointing issue is because your logfile groups are too small and you do not have enough of them..
Re: Fatal NI connect error [message #647787 is a reply to message #647785] Mon, 08 February 2016 01:45 Go to previous messageGo to next message
ashishkumarmahanta80
Messages: 231
Registered: October 2006
Location: kolkatta
Senior Member
Dear John,

I know about the checkpoint issue. Some urgent work is going on during office hour instead on off-office hour. Only concerned is about


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: 110
    nt OS err code: 0


If it's not having problem, then I can ignore it....right??

Regards,
Ashish Kumar Mahanta
Re: Fatal NI connect error [message #647790 is a reply to message #647787] Mon, 08 February 2016 02:49 Go to previous messageGo to next message
Michel Cadot
Messages: 65988
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Quote:
If it's not having problem, then I can ignore it....right??


Yes.

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).

ORA-12535: TNS:operation timed out
 *Cause: The requested operation could not be completed within the time out
 period.
 *Action: Look at the documentation on the secondary errors for possible
 remedy. See SQLNET.LOG to find secondary error if not provided explicitly.
 Turn on tracing to gather more information.
Re: Fatal NI connect error [message #657341 is a reply to message #647790] Mon, 07 November 2016 03:09 Go to previous messageGo to next message
naveen_rc2000@yahoo.com
Messages: 7
Registered: November 2016
Location: India
Junior Member
Hi All,

Even I see the same error time again in the alert log.
Our Environment is ORACLE RAC 12c.
Any reason why this issue occurs.

Re: Fatal NI connect error [message #657343 is a reply to message #657341] Mon, 07 November 2016 03:10 Go to previous message
Michel Cadot
Messages: 65988
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Same question same answer.

Previous Topic: ORA-4031
Next Topic: Distributed Transactions
Goto Forum:
  


Current Time: Wed Nov 21 10:11:01 CST 2018