Home » RDBMS Server » Networking and Gateways » SQL NET LOG (Oracle 10g, Windows Server 2003 64bit)
SQL NET LOG [message #381324] Fri, 16 January 2009 06:22 Go to next message
rizimazhar
Messages: 34
Registered: August 2008
Location: Pakistan
Member

Following error is repeatedly shown over one of our main production servers.
Can anybody please tell me how can i track the UNKNOW Client Address information or how can i get to know the IP address of this Unknown client. And at the end, how can i get rid of this error.

Fatal NI connect error 12170.

VERSION INFORMATION:
TNS for 64-bit Windows: Version 10.2.0.1.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 64-bit Windows: Version 10.2.0.1.0 - Production
Time: 16-JAN-2009 15:50:10
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: <unknown>



Repective errors in alert log file are shown as:

Fri Jan 16 15:29:51 2009
Errors in file d:\oracle\product\10.2.0\admin\homw\bdump\homw_reco_652.trc:
ORA-12170: TNS:Connect timeout occurred
Re: SQL NET LOG [message #381328 is a reply to message #381324] Fri, 16 January 2009 06:38 Go to previous messageGo to next message
Michel Cadot
Messages: 64103
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
TNS-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.

TNS-00505: Operation timed out
 *Cause: The requested operation could not be completed within the timeout
 period.
 *Action: For further details, turn on tracing and reexecute the operation.

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

Regards
Michel
Re: SQL NET LOG [message #381363 is a reply to message #381324] Fri, 16 January 2009 08:16 Go to previous messageGo to next message
rizimazhar
Messages: 34
Registered: August 2008
Location: Pakistan
Member

we had a virus problem, but that has been fixed.

i am getting your points, but i am still confused with that unknow address log shown in the sql net log

where should i focus...

Re: SQL NET LOG [message #381364 is a reply to message #381363] Fri, 16 January 2009 08:18 Go to previous messageGo to next message
Michel Cadot
Messages: 64103
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
If connection timed out before any net rountrip occured then Oracle received no data and couldn't know any information about client.

Regards
Michel
Re: SQL NET LOG [message #381374 is a reply to message #381324] Fri, 16 January 2009 08:52 Go to previous messageGo to next message
rizimazhar
Messages: 34
Registered: August 2008
Location: Pakistan
Member

Can u plase guide me how to look into these details...
Re: SQL NET LOG [message #381376 is a reply to message #381374] Fri, 16 January 2009 09:00 Go to previous messageGo to next message
Michel Cadot
Messages: 64103
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Activate sqlnet trace: http://download.oracle.com/docs/cd/B19306_01/network.102/b14213/sqlnet.htm#sthref370 search for TRACE.

Regards
Michel
Re: SQL NET LOG [message #381503 is a reply to message #381324] Sat, 17 January 2009 08:01 Go to previous messageGo to next message
rizimazhar
Messages: 34
Registered: August 2008
Location: Pakistan
Member

i have set CLIENT_CONNECT_TIMEOUT in both LISTENER and SQLNET.

But continuous errors are is still there

I have dataguard implemented as well and it is working fine.
Others clients also have no problems.

Only problem for me is to diagnose the root cause that is generating so much log data without actually having a problem

Re: SQL NET LOG [message #381514 is a reply to message #381503] Sat, 17 January 2009 09:13 Go to previous message
Michel Cadot
Messages: 64103
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
So read my previous post.

Regards
Michel
Previous Topic: TNS-12518 and patch application (merged)
Next Topic: shared server configuration
Goto Forum:
  


Current Time: Sun Dec 04 04:54:02 CST 2016

Total time taken to generate the page: 0.08162 seconds