OraFAQ Forum: Server Administration

Home » RDBMS Server » Server Administration » Lost ASH report (Oracle, 11g R2, solaris 5.10)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Lost ASH report [message #629561]

Wed, 10 December 2014 23:11

Tlg13team
Messages: 100
Registered: June 2008
Location: MGL

Senior Member

Hi all,

I received below error message in the alert log several times. after that I cannot connect to my database. database cannot allow new connections.

Quote:

Fatal NI connect error 12170.

VERSION INFORMATION:
TNS for Solaris: Version 11.2.0.3.0 - Production
Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - Production
TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.3.0 - Production
Time: 08-DEC-2014 13:06:09
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=172.30.14.137)(PORT=51191))
WARNING: inbound connection timed out (ORA-3136)

I did reboot the server then database was up.
I try to find root case of this failure then execute AWR report but same period of log lost on the server.
You can show below.

Quote:

21756 08 Dec 2014 09:00 1
21757 08 Dec 2014 10:00 1
21758 08 Dec 2014 11:00 1

21760 08 Dec 2014 17:09 1
21761 08 Dec 2014 18:00 1
21762 08 Dec 2014 19:00 1

I found above period of active session history data from a trace file.
I loaded this data to a table but cannot show report by user friendly like AWR html format.

How to know what operation executed on the server then block new connections on the server?

Report message to a moderator

Re: Lost ASH report [message #629562 is a reply to message #629561]

Wed, 10 December 2014 23:21

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

03136, 00000, "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.

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

Report message to a moderator

Re: Lost ASH report [message #629563 is a reply to message #629562]

Thu, 11 December 2014 00:30

Tlg13team
Messages: 100
Registered: June 2008
Location: MGL

Senior Member

I did not configured SQL NET on the server. I did not change anytime on the server side.

Report message to a moderator

Previous Topic:	SMTP
Next Topic:	utlrp - many invokes different results :/

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Mar 04 20:26:08 CST 2025