| ora-12571: tns packet writer failure. [message #290905] |
Wed, 02 January 2008 01:51  |
IBNHUSSAIN
Messages: 39
Registered: December 2007
Location: INDIA
|
Member |
|
|
Hi gurus,
I am getting the following error in the alert log file.
Errors in file >>>>>>>>>udump\orcl_ora_2956.trc:
ORA-12571: TNS:packet writer failure.
when i checked orcl_ora_2956.trc file i find.
ATAL ERROR IN TWO-TASK SERVER: error = 12152
*** 2007-11-05 14:50:39.510
ksedmp: internal or fatal error
ORA-12571: TNS:packet writer failure.
ORA-12571 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 re-execute the operation.
If error persists, contact Worldwide Customer Support.
But before going for any support i wanted make sure myself that i have utilised all alternatives.
Explanation:
This error occurs atleast once in a week and sometimes 3-4 times or more but database remains hang for some time then come back to normal. And I see these error in alertlog.
After searching on internet what I understood is that this
error may occur for following reasons.
1.If user abrobtly disconnected from his session e.g. clicking cross button.
(but in my case it is only one user which is an application and i find it is ok.
2.An antivirus software which prevents packets to pass.
3.Any spybot or spy adware.
May be many i don't know please teach me about those.
The solutions i came across are:
1.To comment all lines in sqlnet.ora
2. To Uninstall the antivirus software.
3. To Use spyware removal.
4. To Remove Two-task parameter.
And I am not sure which one is suitable in my situation and why it is used( what is the reason)
So Please I request you all to clarify my doubts.
[Updated on: Wed, 02 January 2008 01:56] Report message to a moderator |
|
|
|
|
|
|
|
|
|
| Re: ora-12571: tns packet writer failure. [message #357927 is a reply to message #290905] |
Fri, 07 November 2008 05:08  |
naiduva
Messages: 4
Registered: November 2008
Location: India - Chennai
|
Junior Member |
|
|
This is a BUG.
Refer Metalink NOTE:357557.1 for more details.
Cause:
The client application died (or dropped the connection) before the server process could send the break/reset message back, and that prevented the server process from exiting gracefully. This caused the server trace file to be dumped.
This issue has been reported and fixed via non-published bug:3816595
- Vasant
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
