Consultor Eletrônico



Kbase P60540: Ora -12571 . TNS:Packet writer failure (1252)
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   29/03/2004
Status: Unverified

FACT(s) (Environment):

Progress 9.x

SYMPTOM(s):

Ora -12571 . TNS:Packet writer failure (1252)

CAUSE:

Oracle error indication a network problem for sqlnet connectivity

FIX:

Information provided by Oracle to solve the problem:

Please contact Oracle to get tnsping to work first.

Check for possible network or network related equipment problems, such a bad
router card.
Check for any duplicate ip address in your configuration files, TNSNAMES.ORA
and LISTENER.ORA

1.. The server should be up and running.
The ORA-12571:TNS:packet writer failure is a natural error raised and reported
by the applications that are connected to the database
when the database is brought down while they are connected. SQL*PLUS will
raise ORA-12571 when it is connected the the Oracle Server and
the Server is shutdown (i.e: issuing shutdown or shutdown immediate commands
to database server from svrmgrl utiltiy.)

2.. Check for network problems. Check for installed service packs.
Search for possible network or network related equipment problems such
as a bad router card. Faulty network equipment is also likely to cause this
error.Also check if the NT interface driver is functioning
correctly.

3.. Check the SQLNET.ORA file on the client and the server and remove the
following entry(if exisits) from the $ORACLE_HOME/NETWORK/ADMIN/SQLNET.ORA file on both the client and server:
SQLNET.EXPIRE_TIME=0

for fact: MS Windows 2000
fact: Oracle 8.1.6 client
symptom: Tnsping Fails With TNS-12571 Tns Packet Writer Failure
symptom: Sql*Net client had worked before
symptom: Sygate Personal Firewall had been recently installed
cause: The Sygate Personal Firewall software has component(s) that prevent
sqlnet from connecting to an Oracle database.

the fix is:

Remove the Sygate Personal Firewall Software. Disabling the software will not
fix the problem, only completely removing it will restore sqlnet connectivity.