Monday , September 25 2017
Home / Oracle DBA / NETWORKING WITH ORACLE

NETWORKING WITH ORACLE

NETWORKING WITH ORACLE

  1. We need to have oracle client software installed on client machine in order to connect to server
  2. The following files are required to establish a successful connection to the server
    1. Client – TNSNAMES.ORA and SQLNET.ORA
    2. Server – LISTENER.ORA, TNSNAMES.ORA and SQLNET.ORA
  3. TNSNAMES.ORA file contains the description of the database to which connection should establish
  4. SQLNET.ORA will define the type of connection between client and server
  5. Apart from using tnsnames.ora we can also use EZCONNECT, LDAP, bequeath protocol etc to establish connection to server
  6. These files will reside $ORACLE_HOME/network/admin
  7. LISTENER service will run based on LISTENER.ORA file and we can manage listener using below commands
    1. $ lsnrctl start / stop / status / reload
  8. We can have host string different from service name i.e instance name or SID and even it can be different from database name. This is to provide security for the database
  9. Tnsping is the command to check the connectivity to the database from client machine
  10. Do create seperate listeners for multiple databases
  11. If the connections are very high, create multiple listeners for the same database
  12. Any network related problem should be resolved in the following steps
    1. Check whether listener is up and running or not on server side
    2. Check the output is ok for tnsping command
    3. If still problem exist, check firewall on both client and server. If not known take the help of network admin
  13. We can know the free port information from netstat command
  14. We need to set password for listener so as to provide security
  15. TNSNAMES.ORA and SQLNET.ORA files can also be seen on server side because server will act as client when connecting to another server
  16. If listener is down, existing users will not have any impact. Only new users cannot be able to connect to instance
  17. From 10g, SYSDBA connection to database will use bequeath protocol as it doesn’t require any protocol like TCP/IP
Note: article about LISTENER security can be found @ http://pavandba.files.wordpress.com/2009/11/integrigy_oracle_listener_tns_security.pdf
Read More:
USER MANAGEMENT
ORACLE MANAGED FILES (OMF)
CREATING THE ORACLE WALLET

Comments

comments

Check Also

How to switch on primary database to physical standby database

After configuration data guard then data is switching  into primary database  to standby database : …

Leave a Reply

Your email address will not be published. Required fields are marked *