3 Replies Latest reply: Feb 28, 2013 1:45 AM by 934249 RSS

    database reacting very slowly when enable dns

    934249
      Hi frennds,

      Now i have installed RHEL 5.5 on my server. And installed Oracle Database 11g Enterprise Edition Release 11.2.0.1.0.

      My problem is when we set DNS values in network settings for getting connected with internet, application taken too long time to retrieve values from database. If we remove values from DNS and made the server disconnected from internet, then no issue. But we need internet connection in our server.

      Previously i have installed RHEL 5.3 and Oracle 10g.. at that time i didn't faced this type of problem.

      Please help me to overcome this problem

      Thanks in advance
        • 1. Re: database reacting very slowly when enable dns
          sb92075
          931246 wrote:
          Hi frennds,

          Now i have installed RHEL 5.5 on my server. And installed Oracle Database 11g Enterprise Edition Release 11.2.0.1.0.

          My problem is when we set DNS values in network settings for getting connected with internet, application taken too long time to retrieve values from database. If we remove values from DNS and made the server disconnected from internet, then no issue. But we need internet connection in our server.

          Previously i have installed RHEL 5.3 and Oracle 10g.. at that time i didn't faced this type of problem.

          Please help me to overcome this problem

          Thanks in advance
          how can we reproduce what you report?


          How do I ask a question on the forums?
          SQL and PL/SQL FAQ
          • 2. Re: database reacting very slowly when enable dns
            alvaromiranda
            Hello,

            What other application you have on the database server?

            Looks like is giving time out trying to resolve the reverse of each connection.

            That is when example IP 192.168.1.2 connects, for logs it want to write name-of-the-machine

            What about using a proxy to reach internet? the Proxy will handle the name resolution.

            Paste here what you have on the /etc/resolv.conf and /etc/nsswitch.conf for hosts: configuration.


            If this is the case, you can identify what's not being resolved and put in the dns or the /etc/hosts with:

            $ netstat -ap | grep '[0-9]\.[0-9]'
            tcp 0 0 server:ssh 192.168.1.2:57513 ESTABLISHED 23517/sshd

            the -ap will give you all the connections and the port information, not converting to ip, and the grep '[0-9]\.[0-9]' will cut those number dot number lines like the IP

            If you want to see only the connection to your listener, $ netstat -ap | grep '[0-9]\.[0-9]' | grep ':1521'

            At one company, we found the server was handling thousands of connections, coming from 4 app servers.. none of those in the dns.. we did include the app ip in the hosts file, and was a huge improvement.

            good luck

            Alvaro.
            • 3. Re: database reacting very slowly when enable dns
              934249
              Thank u for reply friend.

              In network proxy, I have chosen "Direct internet connection". And in "Advanced configuration" tab, ip addresses in Ignore Host List are "localhost" and 127.0.0.0/8.

              content in my "resove.conf" file
              ------------------------------------------
              ; generated by /sbin/dhclient-script
              nameserver 202.160.161.3
              nameserver 202.138.96.2
              nameserver 202.138.100.103

              content in my "nsswitch.conf" file
              ---------------------------------------------
              #
              # /etc/nsswitch.conf
              #
              # An example Name Service Switch config file. This file should be
              # sorted with the most-used services at the beginning.
              #
              # The entry '[NOTFOUND=return]' means that the search for an
              # entry should stop if the search in the previous entry turned
              # up nothing. Note that if the search failed due to some other reason
              # (like no NIS server responding) then the search continues with the
              # next entry.
              #
              # Legal entries are:
              #
              #     nisplus or nis+          Use NIS+ (NIS version 3)
              #     nis or yp          Use NIS (NIS version 2), also called YP
              #     dns               Use DNS (Domain Name Service)
              #     files               Use the local files
              #     db               Use the local database (.db) files
              #     compat               Use NIS on compat mode
              #     hesiod               Use Hesiod for user lookups
              #     [NOTFOUND=return]     Stop searching if not found so far
              #

              # To use db, put the "db" in front of "files" for entries you want to be
              # looked up first in the databases
              #
              # Example:
              #passwd: db files nisplus nis
              #shadow: db files nisplus nis
              #group: db files nisplus nis

              passwd: files
              shadow: files
              group: files

              #hosts: db files nisplus nis dns
              hosts: files dns

              # Example - obey only what nisplus tells us...
              #services: nisplus [NOTFOUND=return] files
              #networks: nisplus [NOTFOUND=return] files
              #protocols: nisplus [NOTFOUND=return] files
              #rpc: nisplus [NOTFOUND=return] files
              #ethers: nisplus [NOTFOUND=return] files
              #netmasks: nisplus [NOTFOUND=return] files

              bootparams: nisplus [NOTFOUND=return] files

              ethers: files
              netmasks: files
              networks: files
              protocols: files
              rpc: files
              services: files

              netgroup: nisplus

              publickey: nisplus

              automount: files nisplus
              aliases: files nisplus

              Result by $netstat -ap | grep '[0-9]\.[0-9]'
              -----------------------------------------------------

              [oracle@myserver ~]$ netstat -ap | grep '[0-9]\.[0-9]'
              (Not all processes could be identified, non-owned process info
              will not be shown, you would have to be root to see it all.)
              tcp 0 0 192.168.0.197:61266 maa03s16-in-f0.1e100.:https ESTABLISHED -
              tcp 0 0 192.168.0.197:16566 par03s12-in-f15.1e100:https TIME_WAIT -
              tcp 0 0 192.168.0.197:27660 bom03s02-in-f21.1e100:https ESTABLISHED -
              tcp 0 0 ::ffff:192.168.0.197:16355 ::ffff:192.168.0:ricardo-lm ESTABLISHED -
              tcp 0 0 ::ffff:192.168.0.197:39622 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39621 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39618 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39619 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39616 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39598 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39597 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39595 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39614 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39613 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39611 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39608 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39609 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39606 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39605 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39603 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39600 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.168.0.197:39601 ::ffff:192.168.0.1:ncube-lm TIME_WAIT -
              tcp 0 0 ::ffff:192.1:personal-agent ::ffff:192.168.0.212:44151 ESTABLISHED -
              tcp 0 0 ::ffff:192.1:personal-agent ::ffff:192.168.0.212:44152 ESTABLISHED -
              unix 2 [ ACC ] STREAM LISTENING 866187 9776/tnslsnr /var/tmp/.oracle/s#9776.1
              unix 2 [ ACC ] STREAM LISTENING 866192 9776/tnslsnr /var/tmp/.oracle/s#9776.2
              unix 2 [ ACC ] STREAM LISTENING 12186 - /tmp/scim-bridge-0.3.0.socket-0@localhost:0.0
              unix 3 [ ] STREAM CONNECTED 997577 - /tmp/scim-bridge-0.3.0.socket-0@localhost:0.0
              unix 3 [ ] STREAM CONNECTED 867200 - /tmp/scim-bridge-0.3.0.socket-0@localhost:0.0
              unix 3 [ ] STREAM CONNECTED 328869 - /tmp/scim-bridge-0.3.0.socket-0@localhost:0.0
              unix 3 [ ] STREAM CONNECTED 166231 - /tmp/scim-bridge-0.3.0.socket-0@localhost:0.0
              unix 3 [ ] STREAM CONNECTED 12192 - /tmp/scim-bridge-0.3.0.socket-0@localhost:0.0

              while i was trying "$netstat -ap | grep '[0-9]\.[0-9]' | grep ':1521'" , following information was displayed

              (Not all processes could be identified, non-owned process info
              will not be shown, you would have to be root to see it all.)

              And i had logged in as root and try for netstat -ap | grep '[0-9]\.[0-9]' | grep ':1521... No one result came.

              I have installed Apache tomcat and oracle database in same server. Then In my case should i include anything in hosts file?

              Edited by: 931246 on Feb 27, 2013 11:45 PM