Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Showing results for 
Search instead for 
Did you mean: 

oracle name server

Rpger Tavener
Occasional Advisor

oracle name server

We are experiencing slow performance when we start the Oracle Name server on our primary server. It takes as long as 15-20 minutes to start. Also, registering new databases usually just times out. All other network components seem to be working ok. No other performance issues have been reported. Any insight on this?

When the only tool you own is a hammer, every problem looks like a nail!
harry d brown jr
Honored Contributor

Re: oracle name server


Are you using DNS? What are the contents of /etc/resolv.conf and /etc/nsswitch.conf?

live free or die
Live Free or Die
Bill Hassell
Honored Contributor

Re: oracle name server

Very common problem with the DNS server. To prove this, place the important IP addresses and hostnames in /etc/hosts and rename the resolv.conf file to something like resolv.conf.old. Now try your should respond normally.

What is happening is that all socket requests (telnet, rlogin, SQLnet, etc) are asking the DNS server for IP and hostname information and when it refuses to respond or is overloaded, your local server will be appear to be almost crippled as each network task will take 20 seconds or so to timeout.

A problem DNS server will do bad things to an entire network so for reliability, create nsswitch.conf, and use files then dns, and put the important addresses in /etc/hosts.

Bill Hassell, sysadmin
Jeff Schussele
Honored Contributor

Re: oracle name server

I agree with Bill except for relying on /etc/hosts.
Becomes an admin headache in large environments.
You should hound the DNS dudes to have no fewer than 2 servers - 3 is even better, PROPERLY config & monitor/maintain them. Then set the search order to go thru all of them before hitting the hosts file.
/etc/hosts should be the resolver of absolutely LAST resort.
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!