The Trace Route Utility ( TRCROUTE), in Linux and UNIX environments, enables administrators to discover the path or route a connection is taking from a client to a server. Using the TRCROUTE Utility to Test Connectivity from the Client TNS Ping Utility for Linux: Version 11.1.0.0.2 on 1 14:48:28Įxample 15-2 is an example of TNSPING attempting to check using an invalid net service name. This command produces the following message: To determine whether the listener for the sales database is available, and to specify that TNSPING try to connect eight times and then give up, use the following syntax: TCP)(HOST = sales-server)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = Used TNSNAMES adapter to resolve the aliasĪttempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = Use SQL*Plus to attempt a connection to the database.Įxample 15-1 Checking a Listener with TNSPING It does not actually determine whether the database is running. If the net service name specified is a database name, then TNSPING attempts to contact the corresponding listener. Net_service_name must exist in tnsnames.ora file or the name service in use, such as NIS.Ĭount determines how many times the program attempts to reach the server. In the preceding command, the following arguments are used:
Use the following command to test connectivity: This enables you to see the network error that is occurring without the overhead of a database connection. If it fails, then it displays a message describing the error that occurred. If you can connect successfully from a client to a server (or a server to another server) using the TNSPING utility, then it displays an estimate of the round trip time (in milliseconds) it takes to reach the Oracle Net service. The TNSPING utility determines whether the listener for a service on an Oracle Net network can be reached successfully. Using the TNSPING Utility to Test Connectivity from the Client To test several different clients in your network, initiate a connection to a database server from each of them using the following command: You will be prompted for the password.Ĭlick Close to close the Connect Test dialog box. To change the user name, click Change Login. Or the server may not be ready for a connection.Ĭhange the user name to an account known to be unlocked.
There may be an error in the fields entered, Initializing first test to use userid: scott, password: tigerĪttempting to connect using userid: scott For example, if the error message is the following: If the test was not successful, then use the error message to determine further action. If the test was successful, then proceed to Step 5. A successful test results in the following message: If they are not, then see "Starting Oracle Net Listener and the Oracle Database Server" to start components.ĭuring testing, a Connection Test dialog box appears, providing status and test results. Testing assumes the listener and database are running. Select the net service name or database service.Ĭhoose Command, and then select Test Net Service. In the navigator, expand Directory or Local, and then select Service Naming. See Also: "Using Oracle Net Manager to Configure Oracle Net Services"
LAN SPEED TEST CONNECTION TO LST SERVER FAILED HOW TO
The following procedure describes how to perform a loopback test using Oracle Net Manager: Performing a successful loopback verifies that Oracle Net is functioning on the database server. Test the server with a loopback test or Oracle Net Manager.Ī loopback test uses Oracle Net to go from the database server back to itself, bypassing the Interprocess Communication (IPC). To test Oracle Connection Manager, initiate a connection from a client to any active database that has been registered with Oracle Connection Manager. To start Oracle Connection Manager, use the procedure described in "Starting Oracle Connection Manager". Start and test each Oracle Connection Manager, if included in your network. To test a listener, initiate a connection from a client to any active database controlled by that listener. To start the listener, use the procedure described in "Starting Oracle Net Listener and the Oracle Database Server". The following is the recommended sequence for testing the network:
0 kommentar(er)
