This seems to vary considerably, depending upon the specific syntax. For
example, both of the tests below resolve to the same host/port/service.
SQL> tnsping finvdev
ping:-1ms
SQL> tnsping vadc-devdb01-zcdcdevdb01:1521/finvdev.cdc.nicusa.com
ping:350ms
Interestingly, it looks like the sqlcli version step beyond the classic
tnsping utility, in that it actually checks that the service is recognized.
SQL> tnsping vadc-devdb01-zcdcdevdb01:1521/bogus
ORA-12514, TNS:listener does not currently know of service requested in
connect descriptor
100% agreed that the "-1ms" response isn't terribly useful.
On Tue, Oct 27, 2015 at 9:01 AM, Mladen Gogala <gogala.mladen@xxxxxxxxx>
wrote:
On 10/27/2015 09:01 AM, Jeff Smith wrote:
Saying tnsping ‘doesnt work’ – not sure what you mean. What happens when
you try it?
It comes back with "-1ms", which is highly misleading:
mgogala@umajor:~$ sql /nolog
SQLcl: Release 4.2.0.15.296.0549 RC on Tue Oct 27 09:57:29 2015
Copyright (c) 1982, 2015, Oracle. All rights reserved.
SQL> tnsping local
ping:-1ms
SQL>
The server is turned off. The same result is returned when the database is
up and running.
--
Mladen Gogala
Oracle DBAhttp://mgogala.freehostia.com
