16.2 Diagnosing Oracle Net Services
Any underlying fault, noticeable or not, is reported by Oracle Net Services with an error number or message. The error number and message provide useful information for diagnosing the problem, but may not always identify the actual problem.
This section helps you determine the parts of Oracle Net Services that function properly. You can also determine one of the following categories to which the fault belongs:
- Oracle software
- Operating system layer
- Other network layers
Testing the various network layers progressively should, in most cases, uncover any problem.
Starting with Oracle Database 21c, a connection identifier is available for each network connection. The connection identifier uniquely identifies a connection in trace and logs of different network elements and helps in correlating diagnostic data from these elements.
When a SQL*Net connection has multiple hops, such as from a client to Oracle Connection Manager (CMAN) and then to a server, correlating diagnostic information from the existing logs and traces becomes difficult. However, with the availability of a connection identifier, you can correlate diagnostics, track network data traffic, and resolve connectivity errors.
The connection identifier consists of two components, namely,
CONNECTION_ID and CONNECTION_ID_PREFIX. The
CONNECTION_ID parameter contains a unique value, which is
generated when the connection originates at the client. The
CONNECTION_ID_PREFIX is an application specific prefix parameter
that is added to the connection identifier.