Home » RDBMS Server » Networking and Gateways » Fatal NI connect error 12547 (Oracle, 11g, windows 2008R2)
Fatal NI connect error 12547 [message #619535] Wed, 23 July 2014 04:30 Go to next message
Subbu19
Messages: 9
Registered: July 2014
Location: Chennai
Junior Member
Hi,
Following message occurs on alert.log file

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

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: 23-JUL-2014 04:18:15
Tracing not turned on.
Tns error struct:
ns main err code: 12547

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 (12900) as a result of ORA-609
Re: Fatal NI connect error 12547 [message #619544 is a reply to message #619535] Wed, 23 July 2014 05:11 Go to previous messageGo to next message
Michel Cadot
Messages: 59203
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

ORA-12547: TNS:lost contact
 *Cause: Partner has unexpectedly gone away, usually during process
 startup.
 *Action: Investigate partner application for abnormal termination. On an
 Interchange, this can happen if the machine is overloaded.
Re: Fatal NI connect error 12547 [message #619548 is a reply to message #619544] Wed, 23 July 2014 05:53 Go to previous messageGo to next message
Subbu19
Messages: 9
Registered: July 2014
Location: Chennai
Junior Member
Hi Michel,
Now i am getting a different error code from alert.log file

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: 23-JUL-2014 05:24:17
Tracing not turned on.
Tns error struct:
ns main err code: 12535

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=10.122.161.90)(PORT=50611))
WARNING: inbound connection timed out (ORA-3136)
Re: Fatal NI connect error 12547 [message #619556 is a reply to message #619548] Wed, 23 July 2014 06:43 Go to previous messageGo to next message
Michel Cadot
Messages: 59203
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

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.
ORA-03136: inbound connection timed out
 *Cause:  Inbound connection was timed out by the server because
          user authentication was not completed within the given time
          specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value
 *Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections.
          2) Configure SQL*NET with a proper inbound connect timeout value
             if necessary.

Can you ping the host?
Can tnsping the service?

Re: Fatal NI connect error 12547 [message #619568 is a reply to message #619556] Wed, 23 July 2014 07:25 Go to previous messageGo to next message
Subbu19
Messages: 9
Registered: July 2014
Location: Chennai
Junior Member
Yes, can do a tnsping and hostname
Re: Fatal NI connect error 12547 [message #619571 is a reply to message #619568] Wed, 23 July 2014 07:54 Go to previous messageGo to next message
Subbu19
Messages: 9
Registered: July 2014
Location: Chennai
Junior Member
can you guide me, where to set SQLNET.INBOUND_CONNECT_TIMEOUT
Re: Fatal NI connect error 12547 [message #619572 is a reply to message #619571] Wed, 23 July 2014 08:03 Go to previous messageGo to next message
BlackSwan
Messages: 22810
Registered: January 2009
Senior Member
http://www.oracle.com/pls/db112/search?remark=quick_search&word=SQLNET.INBOUND_CONNECT_TIMEOUT
Re: Fatal NI connect error 12547 [message #619574 is a reply to message #619568] Wed, 23 July 2014 08:26 Go to previous messageGo to next message
Michel Cadot
Messages: 59203
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Subbu19 wrote on Wed, 23 July 2014 14:25
Yes, can do a tnsping and hostname


Don't just tell, show us.
Post, from the client platform that received this error, the tnsnames.ora entry and the result of:
ping <the server in this entry>
tnsping <the entry name>
sqlplus xxx/yyy@<the entry name>


[Updated on: Wed, 23 July 2014 10:32]

Report message to a moderator

Re: Fatal NI connect error 12547 [message #619577 is a reply to message #619574] Wed, 23 July 2014 08:40 Go to previous messageGo to next message
BlackSwan
Messages: 22810
Registered: January 2009
Senior Member
A common cause for SQL*Net timeout is a FireWall exists on or between client and DBServer

When was last time SQL*Net worked without error?
What changed since then?
Re: Fatal NI connect error 12547 [message #619583 is a reply to message #619577] Wed, 23 July 2014 10:34 Go to previous messageGo to next message
Michel Cadot
Messages: 59203
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Yes, this is what I have in mind and why I asked for these operations.

@OP, note: replace "client platform" by "application server" if client that receives the error uses a 3-tier application.

Re: Fatal NI connect error 12547 [message #619656 is a reply to message #619583] Thu, 24 July 2014 01:26 Go to previous messageGo to next message
Subbu19
Messages: 9
Registered: July 2014
Location: Chennai
Junior Member
./fa/12067/0/
Hi All,
Following is the ping status from the client machine(Application server)

C:\Users\peowcproe>ping peo-pwc-02 (Database server)

Pinging peo-pwc-02.XXXXXX.com [10.122.161.91] with 32 bytes of data:
Reply from 10.122.161.91: bytes=32 time<1ms TTL=128
Reply from 10.122.161.91: bytes=32 time<1ms TTL=128
Reply from 10.122.161.91: bytes=32 time<1ms TTL=128
Reply from 10.122.161.91: bytes=32 time<1ms TTL=128

Ping statistics for 10.122.161.91:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms


Then i can able to do telnet peo-pwc-02 1521 (Database Server machine name with port number)

Can't able to do tnsping, because no oracle client is installed. Our Application software automatically connects with JDBC driver connection
  • Attachment: 1.png
    (Size: 11.24KB, Downloaded 60 times)

[Updated on: Thu, 24 July 2014 01:29]

Report message to a moderator

Re: Fatal NI connect error 12547 [message #619657 is a reply to message #619656] Thu, 24 July 2014 01:31 Go to previous messageGo to next message
Michel Cadot
Messages: 59203
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

What is the JDBC connect string?

Re: Fatal NI connect error 12547 [message #619693 is a reply to message #619657] Thu, 24 July 2014 08:00 Go to previous message
BlackSwan
Messages: 22810
Registered: January 2009
Senior Member
A common cause for SQL*Net timeout is a FireWall exists on or between client and DBServer

When was last time SQL*Net worked without error?
What changed since then?

BTW - success of tnsping does "prove" anything regarding existence or not of any FireWall on or between client & DBServer
Previous Topic: " Tracing not turned on" SQLNET.ora
Next Topic: Listener status
Goto Forum:
  


Current Time: Tue Sep 23 21:34:42 CDT 2014

Total time taken to generate the page: 0.10458 seconds