Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: database connectivity/tnsping problem

Re: database connectivity/tnsping problem

From: B. Kloppt <b_kloppt_at_my-deja.com>
Date: 3 Feb 2003 15:54:28 -0800
Message-ID: <3717b54f.0302031554.656a3974@posting.google.com>


postbus_at_sybrandb.demon.nl (Sybrand Bakker) wrote in message news:<a20d28ee.0302030730.2849bc6e_at_posting.google.com>...
> b_kloppt_at_my-deja.com (B. Kloppt) wrote in message news:<3717b54f.0302030301.5d0c5343_at_posting.google.com>...
> > Hi everyone,
> >
> > i've got a problem which i haven't been able to solve.
> >
> > my company has two domains, which are connected using a vpn router.
> > my domain (domain.ny) has the ip range 192.168.1.x and the second
> > domain (domain.la) has the ip range 192.168.2.x
> > in both domains we've got an oracle server running under linux.
> > in both domains workstations can connect to databases in their own
> > domain with sqlplus.
> >
> > we cannot, however, cross-domain connect.
> > not even a tnsping works correctly.
> > this is the output of tnsping when pinging from a station in the first
> > domain (domain.ny):
> >
> > ---8<-----------------------------------------------------------------------------
> > [oracle_at_dbserver:~]$ tnsping orcl.domain.la
> >
> > TNS Ping Utility for Linux: Version 9.2.0.1.0 - Production on
> > 02-FEB-2003 20:53:53
> >
> > Copyright (c) 1997 Oracle Corporation. All rights reserved.
> >
> > Used parameter files:
> > /opt/oracle/product/9.2.0/network/admin/sqlnet.ora
> >
> > TNS-03505: Failed to resolve name
> > ---8<-----------------------------------------------------------------------------
> >
> >
> > a tnsping to the ip-address brings me the desired results, however:
> >
> > ---8<-----------------------------------------------------------------------------
> > [oracle_at_dbserver:~]$ tnsping 192.168.2.25
> >
> >
> > TNS Ping Utility for Linux: Version 9.2.0.1.0 - Production on
> > 02-FEB-2003 20:54:37
> >
> > Copyright (c) 1997 Oracle Corporation. All rights reserved.
> >
> > Used parameter files:
> > /opt/oracle/product/9.2.0/network/admin/sqlnet.ora
> >
> > Used HOSTNAME adapter to resolve the alias
> > Attempting to contact
> > (DESCRIPTION=(CONNECT_DATA=(SID=*)(SERVICE_NAME=192.168.2.25))(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.2.25)(PORT=1521)))
> > OK (490 msec)
> > ---8<-----------------------------------------------------------------------------
> >
> > trying to connect to our server from a workstation in the second
> > domain brings the same results.
> > i have double-checked my tnsname.ora file, which has the following
> > section defined:
> >
> > ORCL.DOMAIN.LA
> > (DESCRIPTION =
> > (ADDRESS_LIST =
> > (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.2.25)(PORT = 1521))
> > )
> > (CONNECT_DATA =
> > (SERVICE_NAME = ORCL)
> > )
> > )
> >
> >
> > i have even set NAMES.DEFAULT_DOMAIN = world in the sqlnet.ora file as
> > well.
> >
> > i must be missing something else.
> > can anyone help me?
> >
> > thanks in advance.
>
> Read the line
> used HOSTNAME adapter to resolve the alias
> carefully
> Are you using the hostname adapter? Obviously you aren't
> Now read
> names.directory_path in your sqlnet.ora.
> The order of adapters is incorrect, if you are using the tnsnames
> adapter, it should be in the first place instead of the hostname
> adapter
>
> Regards
>
> Sybrand Bakker
> Senior Oracle DBA

hi,

thanks for the reply, but the adapters are already in the correct order:
NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME) as you can see from my output, the line where 'used HOSTNAME adapter to resolve the alias' showed up, was the output where the tnsping via ip-address was successful. pinging via service.domain, is what doesn't work.

sorry for the cross-post, but i'm not really sure to which ng this message pertains. Received on Mon Feb 03 2003 - 17:54:28 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US