Note that there are some explanatory texts on larger screens.

plurals
  1. POtnsping ping fails, even though I can successfully connect to database
    text
    copied!<p>In trying to establish connectivity from my workstation (actually, am seeing the same behavior on both WinXP32 and Win764 workstations) to an Oracle server, the first thing I always try is a tnsping. When I do so, this is what I get: </p> <pre><code>&gt; C:\&gt;tnsping MYDBNAME &gt; &gt; TNS Ping Utility for 32-bit Windows: &gt; Version 10.2.0.1.0 - Production on &gt; 25-JAN-2 011 15:03:35 &gt; &gt; Copyright (c) 1997, 2005, Oracle. All &gt; rights reserved. &gt; &gt; Message 3511 not found; No message &gt; file for product=NETWORK, &gt; facility=TNSMessage 3512 not found; &gt; No message file for product=NETWORK, &gt; facility=TNSAttempting to contact &gt; (DESCRIPTION = (ADDRESS_LIST = &gt; (ADDRESS = (PROTOCOL = TCP) (HOST = &gt; thisismyservername.com)(PORT = 1577))) &gt; (CONNECT_DATA = (SID = MYDBNAME))) &gt; Message 3509 not found; No message &gt; file for product=NETWORK, facility=TNS </code></pre> <p>So, as you can see, it is properly detecting my tnsnames file, and picks up the correct server address and port for the specified database, but the tnsping fails with 3511 and 3509 errors. </p> <p>The strange part is, using sqlplus or Toad, from the same workstation, I <strong>can</strong> connect to that very same database successfully. </p> <p>Can anyone explain what is happening here?</p> <p>FWIW:</p> <p>The ORACLE_HOME system environment variable (and any other oracle environment variables) is <strong>not</strong> set.</p> <h2>Update</h2> <p>The ORACLE_HOME environment variable does not necessarily HAVE to be set, it seems to depend per machine somehow. My particular issue was: Oracle 10g has/had a known defect in that tnsping.exe simply didn't work. There is a patch</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload