It's OS utility:
On NT, tracert server_name
On Unix, traceroute server_name

Hi,

I don't agree with binxiong.
The utilities binxiong shows are OS utilities, but oralce has a client utility called TRCROUTE.

This utility is not supported in windows platform, so if you're trying to look for it you won't find it.
In this case use tnsping instead and test network level with the OS trace commands.

If you did install on Unix platform, and still you can't find it under $ORACLE_HOME/bin, then send the exact oracle version and unix version you're using.

Here is an extract from oracle's documentation about this utility:

8.3.5 Using TRCROUTE
The Trace Route Utility (TRCROUTE) enables administrators to discover what path or route a connection is taking from a client to a server. If TRCROUTE encounters a problem, it returns an error stack to the client instead of a single error. These additional error messages make troubleshooting easier.

TRCROUTE is different from TNSPING in that it travels as a special type of connect packet, and is routed as such. As it travels toward its destination, the TRCROUTE connect packet collects the TNS addresses of every node it travels through. If an error occurs, TRCROUTE collects error information that shows where the error occurred. The Trace Route Utility displays the information collected on the client screen. You can redirect the TRCROUTE output to a file, and print it if you wish.

8.3.5.1 Requirements
Trace Route works only over Net8 and SQL*Net version 2.3 and later. Every node along the route from client to server must use SQL*Net version 2.3 or later. If a pre-2.3 node is on the path, the following error is displayed:

TNS-03603:  Encountered a node with pre-2.3 version of SQL*Net


TRCROUTE shows what node along the path is responsible for any errors.

8.3.5.2 Effect on Performance
The Trace Route Utility uses minimal resources. It gathers information in the connect data of a special connect packet; standard connect packets are not affected.

The server is not affected by TRCROUTE. The listener receives and processes the TRCROUTE connect packet. It returns the information to the client by putting it into a refuse packet. The server does not need to start up any new processes or deal with dummy connections.

8.3.5.3 Starting the Trace Route Utility
To invoke TRCROUTE, type the following from the command line:

trcroute service_name


If you have configured your network to use listener load balancing, there may be more than one listener on different nodes for a database. If so, the Trace Route Utility might use any of the listeners, just as a regular connection request might. The output it returns shows you what listener node it used.

8.3.5.4 Examples of Trace Route Output
The following are two examples of trace route output:

a successful Trace Route packet that traveled from a client to a listener
an unsuccessful Trace Route packet that could not reach the listener because the listener was not up.
Example 8-1 Successful Trace Route
%trcroute tcp_direct
Trace Route Utility for Solaris:
Copyright (c) Oracle Corporation 1997.  All rights reserved.

Route of TRCROUTE:------------------
Node: Client            Time and address of entry into node:
-------------------------------------------------------------
01-DEC-96 13:26:36 ADDRESS= PROTOCOL=TCP  Host=shining-sun  Port=1581
Node: Server            Time and address of entry into node:
-------------------------------------------------------------
01-DEC-96 13:27:20 ADDRESS= PROTOCOL=TCP  Host=setting-sun  Port=1521



Example 8-2 Trace Route with Error
% trcroute tcp_direct

Trace Route Utility for SVR4:
Copyright (c) Oracle Corporation 1996.  All rights reserved.

Route of TRCROUTE:------------------
Node: Client            Time and address of entry into node:
-------------------------------------------------------------
01-DEC-96 11:12:34 ADDRESS= PROTOCOL=TCP  Host=shining-sun  Port=1581
TNS-12224: TNS:no listener
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-03601: Failed in route information collection

I search TRCROUTE for testing the listener of an Oracle Database on NT,i have a good network connection with the server ,but the problem is about database connection.

The need of TRCROUTE is to resolve this problem :
The problem is that i usually recieve the error :
 TNS-12535 TNS:operation timed out;
and if i change the port id (in the tnsnames.ora) whith
the port id of dispatcher service (shows when we do :
 lsnrctl>services ) the connection work good.But this is not a slution because id port change  everytime we restart the instance .

Please update and finalize this old, open question. Please:

1) Award points ... if you need Moderator assistance to split points, comment here with details please or advise us in Community Support with a zero point question and this question link.
2) Ask us to delete it if it has no value to you or others
3) Ask for a refund so that we can move it to our PAQ at zero points if it did not help you but may help others.

EXPERT INPUT WITH CLOSING RECOMMENDATIONS IS APPRECIATED IF ASKER DOES NOT RESPOND.

Thanks to all,
Moondancer - EE Moderator

P.S.  Click your Member Profile, choose View Question History to go through all your open and locked questions to update them.

points to sbenyo

Comment from expert accepted as answer.

Computer101
E-E Moderator