My Oracle Support Banner

SQLCL Tnsping Command Always Reports A Time Of "-2ms" (Doc ID 2313678.1)

Last updated on FEBRUARY 05, 2022

Applies to:

Oracle SQL Developer - Version 4.2.0 and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Environment
---------------------
java version "1.8.0_121
Oracle SQLDeveloper Command-Line (SQLcl) version: 4.2.0.17.073.1038
Windows 10 64-bit

Problem
--------------
SQLcl tnsping command always reports a time of "-2ms". This occurs regardless of whether or not the supplied tns alias is valid, with no error message being reported in either case.

Works in SQLCL 4.2.0.16.260.1205 as expected.



Steps to reproduce the issue
---------------------------------
SQL> show version
Oracle SQLDeveloper Command-Line (SQLcl) version: 4.2.0.17.073.1038


Available TNS Entries
---------------------
mydb

SQL> tnsping mydb
 ping:-2ms

SQL> tnsping bogus
 ping:-2ms

SQL> connect <user>@mydb
Password? (**********?) ***********
Connected.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.