SQL*Net Troubleshooting
Even in the best planned network, problems can and do occur. There are few things more frustrating than to have what appear to be a properly configured client and server that refuse to connect. Even in the simplest network, there could be several potential causes of this failure, including:
A problem with a SQL*Net configuration parameter
A non-functioning network protocol
A failure in a logical network component, like a router
A failure in the physical network, like a broken wire or unplugged connection
The key to diagnosing network connectivity problems is to logically analyze the problem and confirm the proper operation of each component. You must determine if the failure is due to a problem in:
The Oracle software
The network protocol layers
The physical network
In diagnosing the problem, you may be able to take advantage of tools and techniques provided by the host operating system as well as by Oracle.
One easy way to determine whether SQL*Net is properly installed, configured, and running on a particular server is to perform a loopback test on the server host. This technique uses SQL*Net to connect to the database, even though it is local on that machine. To perform a loopback test using SQL*Plus:
Verify that the database is up and running by connecting locally using SQL*Plus. For example, issue the command line:
sqlplus scott/tiger
to establish a connection to the database.
Connect to the database using a SQL*Net loopback connection by specifying a SQL*Net connect ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access