Skip to Main Content
  • Questions
  • ORA-12571: TNS:packet writer failure

Breadcrumb

May 4th

Question and Answer

Connor McDonald

Thanks for the question, wallacel.

Asked: November 07, 2000 - 9:46 pm UTC

Last updated: November 25, 2004 - 10:15 am UTC

Version: 8.1.6

Viewed 10K+ times! This question is

You Asked

Tom:

I got this error very often recently.
when i go to Oracle8i error messages release 8.1.5 A67785-01
i found that error between 12495 and 12700 is missing.

i was wondering why, also why did i got this message?


Regards,

and Tom said...

Error: ORA-12571 / TNS-12571
Text: TNS:packet writer failure
---------------------------------------------------------------------------
Cause: An error occurred during a data send.
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Oracle Customer Support.



(the last part of that Action being perhaps the most important)...

As for the 'missing' messages -- I see them in

</code> http://docs.oracle.com/cd/F49540_01/DOC/server.815/a67785/tnsus.htm#1000527 <code>

those are TNS, not ORA, maybe you looked in the wrong section?

Rating

  (5 ratings)

Is this answer out of date? If it is, please let us know via a Comment

Comments

ora - 12571

apl, December 11, 2003 - 3:44 am UTC

i am getting this error
ora - 12571 tns:packet writer failure
i got this error only in one client machine. Rest of the client machines can connect to the server.
My client machine o/s is windows 2000. i can ping to the server. but i am not getting tnsping

thanking You




Tom Kyte
December 11, 2003 - 6:07 am UTC

please contact support for an issue like this.

A reader, December 11, 2003 - 1:46 pm UTC

I wish Oracle Support was as efficient/effective as Tom.

Maybe some info about this issue could help anyone...

Sven Bleckwedel, March 23, 2004 - 1:13 pm UTC

Hi,

"
symptom: Errors appear in alert file
symptom: FATAL ERROR IN TWO-TASK SERVER:
symptom: ERROR = 12571
symptom: trace file generated
symptom: Database operations continue successfully
cause: The most common cause for the above error is an ungraceful
disconnection of a session from the oracle db while the db is currently running
a dml statement issued by that session. The error is recorded when oracle
attempts to reply back to the session with the results of the dml and cannot
access the session. Overall database operations are usually not affected.

An ungraceful disconnection could cause by but is not limited to any of the
following:
- the client machine crashed
- the network connection crashed
- the user exited the session improperly (not issuing the 'exit' command)
- the user application allows the user to exit the application without properly
terminating the session.

The above can cause problems with corrupted rollback segments if occurring on a
regular basis and is not addressed. This would require db recovery and
possibly a db rebuild (not a light matter)

PMON will usually rollback most transactions in the rollback segments for a
session if it finds that the session has been ungracefully disconnected, but
there is always a chance that it cannot and this will lead to rollback segment
corruption.



fix:

The dml and the user that issued the dml can be determined from the trace file.
The current dml is in the tracefile header section. The user can be found in
the process state dump of the trace. The process state shows the machine,
o/suser, and user for the session.

The DBA can use this information to determine what the user was doing at the
time and if there was an ungraceful exit from the session the user was
utilizing.

The DBA should then address the cause of the ungraceful exit to reduce the
possibility of reoccurance.
"


Packet writer failure and sqlnet.ora parameters

Livio, November 25, 2004 - 10:15 am UTC

I wonder whether there is any link between such message and sqlnet.ora file parameters, namely SQLNET.AUTHENTICATION_SERVICES.

12571 FETCH OUT OF SEQUENCE

Michael Slifer, October 28, 2016 - 7:41 pm UTC

I RECEIVED 12571 PROCESSING A FETCH. THE OPEN CURSOR STATEMENTS WERE WITHIN CONDITIONS THAT WERE NOT MET SO NO OPEN WAS DONE.