Operating System - HP-UX
1833824 Members
2528 Online
110063 Solutions
New Discussion

Communication Problems between Database Servers

 
SOLVED
Go to solution
Victor BERRIDGE
Honored Contributor

Re: Communication Problems between Database Servers

So...
I believe the ROUTE_GATEWAY[0]="200.200.120.254"
is maybe not quite good so check that

it should be the same on both servers since you are on the same lan
If lan1 is the config you want then copy the whole block:
ROUTE_DESTINATION[0]=default
ROUTE_MASK[0]=""
ROUTE_GATEWAY[0]=""
ROUTE_COUNT[0]=""
ROUTE_ARGS[0]=""

Just after the lan1 configuration and replace [0] by[1] and give the good route

Then you should be OK

Good luck
Victor
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

What you said about that missing part in my netconf, is that for the file I just sent you or the originial (test) netconf file?

attached are both in a zip...netconf_production is production 200.200.120.3 and netconf_test is test 200.200.120.8

going to lunch..awaiting much needed help...thanks a lot all!

Re: Communication Problems between Database Servers

don't forget to net stop - start after the modifications!
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

Victor,

I want to be very clear. On production I have to replace

ROUTE_DESTINATION[0]="default"
ROUTE_MASK[0]=""
ROUTE_GATEWAY[0]="200.200.120.254"
ROUTE_COUNT[0]="1"
ROUTE_ARGS[0]=""


with

what?

I'm not understanding...I'm like SO NEW at this UNIX stuff, furthermore the networking stuff....please help.
Victor BERRIDGE
Honored Contributor

Re: Communication Problems between Database Servers

The [0] by [1]
And the route by ?
Since it was not configured on inland3 I believe it took the default:
200.200.120.1


Im looking at your 2 netconf files...

All the best
Victor
Victor BERRIDGE
Honored Contributor

Re: Communication Problems between Database Servers

I just looked and think you can copy the above mentionned block with the correction and the end of both files and that should do it, but dont forget in the test netconf to remove or comment out:
INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=200.200.120.8
SUBNET_MASK[0]=255.255.255.0
BROADCAST_ADDRESS[0]=200.200.120.255
INTERFACE_STATE[0]=down
DHCP_ENABLE[0]=0
I would comment out:
#INTERFACE_NAME[0]=lan0
#IP_ADDRESS[0]=200.200.120.8
#SUBNET_MASK[0]=255.255.255.0
#BROADCAST_ADDRESS[0]=200.200.120.255
#INTERFACE_STATE[0]=down
#DHCP_ENABLE[0]=0

And in the prod netconf
ROUTE_GATEWAY[0]="200.200.120.254" to:
ROUTE_GATEWAY[0]=""

All the best
Victor

Re: Communication Problems between Database Servers

attached, the file i would use!
Victor BERRIDGE
Honored Contributor

Re: Communication Problems between Database Servers

This is what you would add to both at the end:

ROUTE_DESTINATION[1]="default"
ROUTE_MASK[1]=""
ROUTE_GATEWAY[1]="200.200.120.1"
ROUTE_COUNT[1]="1"
ROUTE_ARGS[1]=""

But check with your network guys what is the default gateway on you 200.200.120 network as the value I give is only what I think...


All the best
Victor
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

default gateway is 200.200.120.254
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

Did netstop and netstart and still not working (pinging etc. to see INLAND3 200.200.120.8) I'm shutting down Oracle as we speak now and getting ready to do a reboot to see if that helps...
Victor BERRIDGE
Honored Contributor

Re: Communication Problems between Database Servers

Back from lunch?

Well for sure not having the same default gateway on both sides didnt help, so since the production was correct (gateway) maybe by rebooting inland3 (test) now you did the coreections could help us see more clear and hopefully solve this issue, what do you think?
Check again you dont have strange char or dos2ux your files if so before.
What have you chosen - Keep lan1 up both sides?


Victor
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

Victor,

Ok rebooted test (200.200.120.8) and I can now ping 200.200.120.8 from itself and I can also ping 200.200.120.3 (production) from test. I CANNOT however ping hostname INLAND3 (test) from itself...

On production I can ping 200.200.120.3 from itself and also I can ping inland8 hostname. I cannot however ping INLAND3 hostname from production. I can only ping the ip (200.200.120.8)

However when I do a uname -a on TEST (200.200.120.8) it says INLAND3 etc...
How come INLAND3 is not being recongnized on the network as hostname, can only see "IP address"??

please help...
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

Could it be a problem with our DNS name server? It's Windows 2000 Professional Server.
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

root:INLAND3>nslookup 200.200.120.8
*** Warning - the local domain is not
*** Either hostname should be a domain
*** the domain should be specified in
*** or the shell variable LOCALDOMAIN

Name Server: inland7.irdbb.com
Address: 200.200.120.7

Trying DNS
Name: inland8
Address: 200.200.120.8

root:INLAND3>
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

I also did this from Windows prompt:

ping -a 200.200.120.8

it reached the address but was showing as Inland3 and not INLAND3

Do I need to make this change in UNIX and then reboot again, if so where? Which file(s)? Only hosts?
Victor BERRIDGE
Honored Contributor

Re: Communication Problems between Database Servers

Well
From any server do nslookup INLAND3 then nslookup 200.200.120.3
Do they match?

What do you have in your /etc/hosts, beacuse if I remember right in nsswitch.conf you have files first

While you look at them I will try to think a bit...
Victor BERRIDGE
Honored Contributor

Re: Communication Problems between Database Servers

Is it important for you the hostname being INLAND3 rather than inland3 like inland8?
what does netstat -rn show now on inland3?
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

Attached is the output from netstat -rn on INLAND3 (200.200.120.8)

Yes the output from the nslookup command match. I ran it on inland8 (200.200.120.3)

It does not matter that the hostname is INLAND3 as opposed to Inland3, just that I don't want to have to change it anywhere else now...
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

From the nslookup on INLAND3, notice the part

Trying DNS
Name: inland8
Address: 200.200.120.8

That is wrong, because inland8 is 200.200.120.3


Where can I change this?
Victor BERRIDGE
Honored Contributor

Re: Communication Problems between Database Servers

Sorry Adrian,
Its support/dispatch week for me ( you remember the phone?...) and its not easy to not get mixed up...

I had to leave my desk a moment...



The DNS is difficult to correct unless you are responsible of it...
So tell them to correct
What you can do is check that on both systems you have in nsswitch.conf:
hosts: files [NOTFOUND=CONTINUE] dns
dont add more for now so save the files you have: cp -p nsswitch.conf nsswitch.conf.last

meaning you will use /etc/hosts FIRST
AND in /etc/hosts put:
Hey didnt I ask you for you hosts file?...

For inland3:
127.0.0.1 localhost loopback
200.200.120.8 INLAND3 inland3 inland3.
for inland8:
127.0.0.1 localhost loopback
200.200.120.3 INLAND8 inland8 inland8.


Adrian I just realized werent the names given in relation with the IP?
ilnalnd3 should be 200.200.120.3 and inland8 200.200.120.8?






Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

no hostnames are usually given in relation to IP but for production IP is always 200.200.120.3 but machine is inland8. So it is a bit confusing in this case :)

so production is hostname inland8 but ip is 200.200.120.3

test is hostname INLAND3 but ip is 200.200.120.8

i made change in hosts file. I cannot ping HOSTNAME only ip though...
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

think problem is that local domain is not set on INLAND3, how do I set that. It is supposed to be IRDBB.COM

Victor BERRIDGE
Honored Contributor

Re: Communication Problems between Database Servers

You know what I think?
I would try to reinitialize the box name and IP
TO do this, use set_parms (do a man of set_parms before so you know what you will be asked)
Then reboot
And see if this changes anything

Give a try?
Adrian Sobers2
Super Advisor

Re: Communication Problems between Database Servers

did the set_parms yesterday and rebooted. Did nothing
Victor BERRIDGE
Honored Contributor

Re: Communication Problems between Database Servers

You should have the domain name in /etc/resolv.conf e.g:
domain .etatge.ch
nameserver

nameserver