Re: Time outs which may not be SQL

Your explanation regarding the 6 hour vs 12h20m test is a little confusing,
but I'll still offer up my past experience. This was on a HP-UX Itanium box.

I had connections to one database (several others on the same box with no
problems) die at exactly the same time early every morning. Some basic
trouble shooting proved that it was only connections made through SQLNET
that died (i.e. a sqlplus connection on the local box would stay alive). I
was all over both the network and SA teams but they swore they held no
grudges against that particular database. Eventually it turned out that the
app was generating so many connections (dozens in a 10 second time span)
that somehow between the OS and Oracle these connections should die. After
working with the app team to reduce the number of connections made to the
database (it was an app bug) the problem went away.

Check your listener.log file to see if you have a similar situation.

Good luck.

Finn



On 4/30/08, Mark Brinsmead <pythianbrinsmead@xxxxxxxxx> wrote:
>
> Can we see the SQLNET.ORA for the database server and client, please.
>
>
> On Wed, Apr 30, 2008 at 9:12 AM, Kline.Michael <Michael.Kline@xxxxxxxxxxxx>
> wrote:
>
> >     We have a large test running for a client. It appears ALL DB
> > connects time out in 12 hours and 20 minutes. There isn't any sqlnet.ora
> > file on the database server.
> >
> >
> >
> > What we have:
> >
> >
> >
> > HP/UX B.11.11 U 9000/800
> >
> >
> >
> > Connected to:
> >
> > Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit
> > Production
> >
> > With the Partitioning, OLAP and Data Mining options
> >
> > This is on the GA016d99 server as the database server. The application
> > server is GA016A0G1.
> >
> >
> >
> > We have connections timing out in roughly 12 hours 20 minutes.
> >
> >
> >
> > So to further clarify the situation, we had nohup sql routines that
> > would sleep for 5 minutes and request something. We also had 6 hours and
> > rerun to test that, and one that would wait for the 12 hours and 20 minutes
> > and rerun.
> >
> >
> >
> > We expected it to only time out the one over 12 hours, but ALL of them
> > got canceled.
> >
> >
> >
> > That makes me think it is probably the Unix, or the network that just
> > doesn't allow connections to exist over that period of time.
> >
> >
> >
> > Where do we start?
> >
> >
> >
> >
> >
> > Michael Kline
> > 804.261.9446
> >
> >
> >
> >
> >
> > LEGAL DISCLAIMER
> > The information transmitted is intended solely for the individual or
> > entity to which it is addressed and may contain confidential and/or
> > privileged material. Any review, retransmission, dissemination or other use
> > of or taking action in reliance upon this information by persons or entities
> > other than the intended recipient is prohibited. If you have received this
> > email in error please contact the sender and delete the material from any
> > computer.
> >
> > SunTrust and Seeing beyond money are federally registered service marks
> > of SunTrust Banks, Inc.
> > [ST:XCL]
> >
>
>
>
> --
> Cheers,
> -- Mark Brinsmead
> Senior DBA,
> The Pythian Group
> http://www.pythian.com/blogs

Other related posts: