Re: How to trace this error?

OK, well looks like you'll have to turn tracing on then to see what's going on.

You didn't mention a version (I wish people would!), but check out this link:

http://download-west.oracle.com/docs/cd/B10500_01/network.920/a96580/trouble s.htm#452480

(Watch for wrapping).

Although that's 9i specific, I can't think that anything's changed very much since 8i.

Tracing is enabled by editing sqlnet.ora, because your problem is clearly not related to the Listener (so modifying listener.ora is not called for) and you don't mention (but I doubt) whether you're using names server or connection manager.

You'll need to set the trace directory (although there is a default) and switch on tracing at an appropriate level until something useful pops up. I suggest you go for the 'admin' level.

Regards
HJR "Terry Mu" <terry_mu_at_yahoo.com> wrote in message news:6%4M9.6712$F2h1.2265_at_news01.bloor.is.net.cable.rogers.com...
> NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)
>
> the application run on the same machine with Oracle server.
>
> "Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message
> news:0E4M9.5907$jM5.17033_at_newsfeeds.bigpond.com...
> > What's your sqlnet.ora look like?
> >
> > HJR
> >
> > "Terry Mu" <terry_mu_at_yahoo.com> wrote in message
> > news:vy4M9.6147$opk.5684_at_news02.bloor.is.net.cable.rogers.com...
> > > The instance is still alive and nobody shut it down. I'm running a
test
> > > application in the instance. I guess that's the problem. Strange thing
> is
> > > that it seems ok if I keep working on it, but after an idle time,
> whatever
> > I
> > > will do it tells the error and I have to reconnect. So I have to
trace
> > it.
> > >
> > > Thanks.
> > >
> > > "Howard J. Rogers" <howardjr2000_at_yahoo.com.au> wrote in message
> > > news:o14M9.5901$jM5.16645_at_newsfeeds.bigpond.com...
> > > > Nothing to do with your specific question, but that error is usually
> par
> > > for
> > > > the course when you're connected to an instance in one session, and
> the
> > > DBA
> > > > does a shutdown abort of that instance somewhere else (or if the
> > instance
> > > > otherwise dies, blows up, starts pining for the fjords etc).
> > > >
> > > > Your session throws a wobbly next time you try and do anything,
> because
> > it
> > > > expects to still be connected, but discovers to its horror that it's
> had
> > > the
> > > > carpet pulled out from underneath its feet.
> > > >
> > > > If, having received that error, you can immediate issue a new
'connect
> > > > user/password', then find out if the instance died (or was killed).
> Only
> > > if
> > > > that's not the issue would I start worrying about why your client
> > suddenly
> > > > loses touch with the instance (which is essentially the problem
here).
> > > >
> > > > Regards
> > > > HJR
> > > >
> > > > "Terry Mu" <terry_mu_at_yahoo.com> wrote in message
> > > > news:804M9.1002$yW.392_at_news04.bloor.is.net.cable.rogers.com...
> > > > > I got this error in my session frequently,
> > > > >
> > > > > ORA-12571: TNS:packet writer failur
> > > > >
> > > > > oerr tells me to enable trace. How to do that and what to trace?
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
Received on Wed Dec 18 2002 - 14:57:23 CST