Re: Can't TNSPing XE database

From: Shakespeare <whatsin_at_xs4all.nl>
Date: Wed, 13 Aug 2008 13:46:32 +0200
Message-ID: <48a2c998$0$190$e4fe514c@news.xs4all.nl>

"Knickerless Parsons" <knickerlessparsons_at_googlemail.com> schreef in bericht news:bf042442-1f01-46a9-a756-788ff5001847_at_59g2000hsb.googlegroups.com...
> Thanks for the reply, it was much appreciated, here's an update:
>
> I have set the ORACLE_HOME environment variable in my computer
> advanced properties, doing this using the SET command only did it for
> the command prompt session I was running at the time and I don't know
> how to do the eqivalent of the unix EXPORT command in DOS type OS's.
>
> So now the important environment variables are:
> =======================================================================================
> Path=C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\app
> \D7998\product\11.1.0\client;C:\app\D7998\product\11.1.0\client\bin;C:
> \Windows\system32;C:\Windows;C:\Windows\System32\Wbem;c:\Program Files
> \Microsoft SQL Server\90\Tools\binn\;C:\Windows
> \System32\WindowsPowerShell\v1.0\
>
> ORACLE_HOME=C:\oraclexe\app\oracle\product\10.2.0\server
>
> TNS_ADMIN is no longer set.
> =======================================================================================
> My assumption is that windows isn't case sensitive!!
>
> so now starting a command prompt in C:\oraclexe\app\oracle\product
> \10.2.0\server\BIN I try tnsping again
>
> =======================================================================================
> C:\oraclexe\app\oracle\product\10.2.0\server\BIN>tnsping xe
>
> TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production
> on 13-AUG-2008 11:39:13
>
> Copyright (c) 1997, 2005, Oracle. All rights reserved.
>
> Used parameter files:
> C:\oraclexe\app\oracle\product\10.2.0\server\network\admin\sqlnet.ora
>
> TNS-03505: Failed to resolve name
> =======================================================================================
> also tried xe.world with the same result!
>
> Looking at the listener, it appears to be started already, issuing
> lsnrctl start gives:
>
> TNS-01106: Listener using listener name LISTENER has already been
> started
>
> During all of this, the database is still accessible via SQL Plus on
> the same machine. I might try to access it from another machine on the
> network, if that fails then it's probably something network related.
> I'll keep you all posted.
>
> Any more ideas??

  1. Windows is not case sensitive, that's correct
  2. Env. variables are valid within the session you run (dos-box), unless you set the way you did. Win has no 'export' functionality.

What I do see is that your TNSNAMES is not used (or at least, the entry is not found there). If it was, tnsping would say so: "Used TNSNAMES adapter to resolve the alias" This might help: copy the entry for XE in your tnsnames, and make it xe.world = (etc.....). Just leave the old one in place.

It's probably your default domain in sqlnet.ora that is causing the error. By using TNSPING XE, tnsping starts looking for xe.world, which isn't there. TNSPING xe.world won't help either, for it still is not there. You could also remove the default_domain from sqlnet.ora, but I would opt to add xe.world to TNSNAMES

Shakespeare Received on Wed Aug 13 2008 - 06:46:32 CDT

Original text of this message