Fog Creek Software
Discussion Board

getting ora 12571 error

I got this "ora 12571: tns packet writer failure", a week back when i tried to use SQLPLUS/TOAD.

my os was win 2000, when i got this error message. and found some resource which said that this problem happens becoz of some problem with tcp/ip maxtransmissionset(sorry, forgot the exact name). since i was able to ping to the database server i tried finding this entry in win 2000 registry but didnt find it. thou, i found someother equivalent entry, but even after changing i still got this error message.

Then my DBA said that u cant do much and asked me to format the drives and re-installed win 2000.

Now after this reinstallation i am able to work in sqlplus/toad.

Somebody, pls tell me
1. why this happened i.e the ora 12571 ?
2. how to come around this problem ?

thanks in anticipation

s p
Thursday, November 6, 2003

It's an Oracle connection time out error.

As such it can have a myriad of explanations - duplicate IP address on the network, database in the process of being shut down. loose SCSI cables and a myriad more.

If you want to research it just typ ora12571 into Google. But if you are not getting it any more I wouldn't bother.

Stephen Jones
Thursday, November 6, 2003

What bothers me out here is the typical DBA or System Administrator mentality i.e:

" If there is something on your machine which behaves differently than normal and if its not one of those 5 points in your troubleshooting guide-book, then * FORMAT * the machine"

Why don't these guys try and analyze / resolve the problem than start from scratch. Its just leaving poor users guessing as to what and how the error happened !!!

What's been your experience in dealing with such people ? Mine's been as listed above.....

Thursday, November 6, 2003

thanks shai and stephen jones, for your responses.

to stephen jones,
i checked the usual suspects(as u listed). but they were all working properly then. anyway, i went for format and now i am able to access the database instance properly.
But, really curious as to how it happened all of a sudden and how to solve it if it happens again.

to shai,
true. these dba or sys admin guys are really keen to pass the buck rather than solving it in a scientific way.

in fact i tried all over google, but didnt find the answer.
in metalink, the solution is limited to win 98 o s.

anyway, if someone gets to know the answer please post it here. it will really help a whole lot of ppl, who mite get hit by such problem.


s p
Thursday, November 6, 2003

I'm on the DBA's side on this. He is being scientific. If it still occurs after you have reinstalled Windows, (or better still a complete system restore) then the problem is hardware or network related or on the server. If it doesn't then it's something to do with your installation (or simply coincidence).

The error message here is impossibly wide; there are arguiments for taking time to find out exactly why something has gone wrong, but not with a catch-all error message such as this.

Stephen Jones
Thursday, November 6, 2003


I just started noticing those errors yesterday in my application's log...

Mark Hoffman
Thursday, November 6, 2003

I had a similar problem recently. Turned out to be an error with one of the recent XP updates (Sorry, I don't run 2000 anymore)...

Anyway, a fix was available in a couple days for this particular app.

Thursday, November 6, 2003

I got curious about this problem and did a little google fishing with the search expression:

    ora 12571 xp

High on the list of results was the following:

I'd like to claim credit for the solution, but better to pass it to the original author :)

Let us know if this resolves the situation.

Friday, November 7, 2003

Shai - I believe it is a DBA/SA's job to keep a system up and running. The most efficient way to do this is to keep users from getting to your system. If a problem like this arises, you tell the user to re-format and they buy it, you have just got yourself at least a few days without this user.

Brilliant strategy if you ask me!

Friday, November 7, 2003

*  Recent Topics

*  Fog Creek Home