Configuration of SQLNET Protocol

Configuration of SQLNET Protocol

SQLNET is a built-in protocol in oracle. It is available in client machines and database server machines. This network protocol contains three files.

1. listener.ora
2. tnsnames.ora
3. sqlnet.ora

Listener.ora:

Listener.ora must be configured at server side. This file can be created by using NETCA tool. This file must contain database SID name. Once the listener service is started, then user request can be accessed by database server.

How to start listener service:

$ lsnrctl start LISTENER

Tnsnames.ora:

This file must be configured or created at client machine. Every client machine require a tnsnames.ora file.

“TNS” means = transparent net service

This file also can be created by NETCA tool means NETWORK CONFIGURATION ASSISTANT

Configuration of listener.ora at server side: (200.200.0.2)

$ xhost + (this command disables access control list and allow users to access NETCA tool)

$ su – oracle

$cd $ORACLE_HOME/network/admin

$ pwd

$ ls

$ rm *

$ ls

$ netca

$ lsnrctl status = to check the status of listener

$ lsnrctl stop = to stop the listener

$ lsnrctl start = to start the listener

$ lsnrctl reload = refresh the listener

$ vi listener.ora

$:wq

$ lsnrctl stop

$ lsnrctl start

$ lsnrctl status

Configuration of tnsnames.ora at client side: (200.200.0.1)

$ ping 200.200.0.2

$ xhost +

$ su – oracle

$ cd $ORACLE_HOME/network/admin/

$netca

 $ ls

$ vi tnsnames.ora

How to test the physical connectivity between the oracle client and database machine:

$tnsping hcp

$sqlplus system/********@hcp

Sql>select * from tab;

Note: If listener service is down at server side then client cannot able to access server.