1 de julho de 2009 às 12:00 am #87630

Marcos Braga

Participante

Oi Rodrigo,

Nesse caso, muda um pouco de figura.

Um conselho, observe sempre o primeiro erro, pois este é o erro real, os erros subsequentes são decorrentes do primeiro erro. Muitas vezes corrigindo o primeiro, os outros são corrigidos.

Observe o conteúdo do DocId: 1013453.6, a respeito do erro reportado.

Problem Description:

An ORA-12203 error occurs when using SQL*Net for Windows.

Search words:
connect connecting netbios

Solution Description:

The ORA-12203/TNS-12203 error message means:

“TNS:unable to connect to destination”

This message can be displayed for a variety of reasons.

1) An invalid TNS service name was supplied in the connect string.

Verify that the TNS service name supplied in your connect string
exists in your TNSNAMES.ORA file. Also verify that the ADDRESS
information for that TNS service name is valid.

a) Is the HOST or SERVICE name correct? 
b) Is the PORT specified correct?

2) The destination system’s listener is not listening.

Verify that the remote system’s SQL*Net listener is running.

3) This error can also occur because of underlying network transport
problems.

Verify with utilities supplied with the networking protocol being
used that the protocol itself is functional. For esample, with TCP/IP,
try PINGing the remote system.

4) TNSNAMES.ORA file is not located in the %ORACLE_HOME%NETWORKADMIN
directory.

Make sure the Windows workstation has its TNSNAMES.ORA file located in
the directory specified by: %ORACLE_HOME%NETWORKADMIN

The %ORACLE_HOME% string should be replaced with the value that is
present in your workstation’s ORACLE.INI parameter named ORACLE_HOME.

If your workstation’s ORACLE.INI file has a parameter named TNS_ADMIN,
make sure that the TNSNAMES.ORA file is located in the directory
pointed to by the TNS_ADMIN parameter.

5) Make sure the Oracle Protocol adapter for the selected networking
protocol is installed.

In the %ORACLE_HOME%BIN directory you should see the following
files for each protocol:

 TCP/IP:   NTT.DLL 
 SPX:      NTS.DLL 
 DECNET:   NTD.DLL

A missing protocol adapter driver will usually produce the following
errors in the SQLNET.LOG and or any client trace file:

  TNS-12203 
  TNS-12538 
  TNS-00508

6) Make sure any Oracle Interchanges (if any) used for this connection
are running.

7) Ensure that the (HOST=tcpiphostname) for TCP/IP and
(SERVICE=spxservicename) for SPX are the the same on the server and client
workstations.

This assumes a global knowledge and usage of the same TCP/IP hostname on
the server and client workstations.

For TCP/IP setups, make sure that the HOST parameter in the LISTENER.ORA
on the server and the TNSNAMES.ORA file on the client point to the same
name, or at least to names that are then translated to the same IP
address by each system. This is especially important for servers with
multiple IP addresses assigned to the various network interfaces on the
server.

For SPX setups, the name must be the same on the server and client
workstations.

8) When using the V2 APPC Adapter for Windows, the alias descriptor in the
tnsnames.ora file should have the value for PLU_LA always in upper case or
a TNS-12203 will result. This is irrespective of the case used in the
SIDEINFO.NSD file for the symbolic destination name. For example:

os2= 
   (DESCRIPTION= 
       (ADDRESS=(PROTOCOL=LU62) 
                (PLU_LA=os2)))   

will result in a TNS-12203 error. 


os2= 
   (DESCRIPTION= 
       (ADDRESS=(PROTOCOL=LU62) 
                (PLU_LA=OS2))) 
will connect fine; where os2 or OS2 is defined as the SYMBOLIC DESTINATION 
NAME in the SIDEINFO.NSD file.

9) When using the V2 NETBIOS Adapter 2.1.4.1.3 for Windows, and getting
either an ORA-12203 or ORA-12224, reference BUG #301274 and #302380 for
the following patch:

Patch 378:  NETBIOS Protocol Adapter V2.1.4.1.4 Windows.  This  
            patch will fix BUGS # 301274 and 302380.

10) Make sure that a ping of the host returns the same IP as the target host.
This may occur using RAS (Remote Access Server) on Windows NT. Upgrade NT
v4.0 to service pack 3.

[]s