Re: long logon times through sqlnet

From: Amar Kumar Padhi <>
Date: Tue, 31 Mar 2009 07:59:58 +0400 (GST)
Message-ID: <15597532.1961238472225555.JavaMail.seven_at_aomfe2p1>

some basic listener Qs -
Is the database and listener on the same server? Is the connect time always 30 secs, or it is intermittently happening? On the server itself, what happens if you log in as non-sys user with full alias (abc/abc_at_test), does it still take time? On one of the client pc, remove server name and put the server Ipaddress address in tnsnames.ora and try (to bypass DNS), does still take time?


-original message-
 Re: long logon times through sqlnet
From: "Mark Brinsmead" <> Date: 31-03-2009 06:58

30 seconds? Sounds a lot like a DNS timeout.

From the database server, are you able to reverse-lookup the IP of the server you are logging in from?

Of course, this is only a guess -- there are many other possible causes.

On Mon, Mar 30, 2009 at 9:38 AM, Dba DBA <>wrote:

> Oracle 10.1.latest patch
> OS: Tru 64
> oracle does not have 10.2 for tru 64.
> This just started to happen. We have not changed anything. If we login from
> the command line on the server and bypass sqlnet logon time is normal. If we
> go through the listener logon time is 30 seconds. We are not out of memory
> or at any resource limits. We have a ticket with Oracle but they are
> pointing all over the place.
> for some reason they have not asked for a sqlnet trace. I just got one and
> I don't see anything in it so I am sending it to support. I ran an AWR
> report and do not see any waits outside the norm. This tells me that the
> issue is happening before you get to the database. so it is a listener
> issue.
> is there any other type of trace I should run? OS level? Or log file to
> look at to help diagnose this?

-- Mark Brinsmead
  Senior DBA,
  The Pythian Group

Received on Mon Mar 30 2009 - 22:59:58 CDT

Original text of this message