User`s guide

Troubleshooting Oracle Net Services
Oracle Net Services 9-9
9.4.5 Configuration on the Client
Configuration of network clients involves adding or editing parameters in the client
configuration file
SQLNET.ORA
and dependent on the used naming method, the
configuration file
LDAP.ORA
or
TNSNAMES.ORA
. For more information about the
configuration parameters, refer to Oracle Database Net Services Reference.
9.4.6 Testing the Configuration on the Client
After you have verified the network connections, you can verify the connections to the
desired Oracle database systems using the
TNSPING
utility:
/CALL-PROCEDURE sid.P.ORAENV
/START-PROGRAM $ORAC1120.TNSPING
When the
enter options
prompt is displayed, enter the net service name for the
database service which you have specified in the naming service. If everything works
fine, then a message similar to the following is returned:
TNS Ping Utility for BS2000/OSD S series: Version 11.2.0.2.0 -
Production on 12-JUN-2012 12:07:40
Used parameter files: network.admin.sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = sales-server)(PORT = 3055)))
(CONNECT_DATA = (SERVICE_NAME = sales.us.acme.com)))
OK (40 msec)
For more information, refer to the Oracle Database Net Services Administrator's Guide.
9.5 Troubleshooting Oracle Net Services
The following is a list of error messages and steps to fix the errors:
1. Listener could not be started.
LSNRCTL
returns the following error message:
LSNRCTL> start
Starting /BS2/$ORAC1120.tnslsnr: please wait...
TNS-12547: TNS:lost contact
TNS-12560: TNS:protocol adapter error
TNS-00517: Lost contact
BS2000 Error: 145: Connection timed out
LSNRCTL>
Ensure that the subsystem
POSIX
is up and running.
Ensure that the
BCAM
Leight Weight Resolver
LWRESD
is properly configured
and running.
2. Listener could not open the log file.
Check if the listener log file, for example,
NETWORK.LOG.LISTENER.LOG
, is
accessible and readable.
Verify the listener log file using the BS2000 SDF command
REPAIR-DISK-FILES
.
If you are not able to repair the listener log file, then delete the file.
3. A client reports ORA-12545