![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
change the hostname value in db2nodes.cfg of instance to service IP alias ( say srv1 ) which is nothing but another resolvable hostname |
#3
| |||
| |||
|
|
change the hostname value in db2nodes.cfg of instance to service IP alias ( say srv1 ) which is nothing but another resolvable hostname I think you mean the virtual IP address which is failing over when one node goes down, right? service ip addresses are usually used to connect directly to one of the nodes. You need to make sure that the reverse lookup points to the correct IP. Please add the virtual IP to your hosts file. Furthermore you have to change your .rhosts file to include the new hostname/ip. Here are the correct steps: install DB2 on both machines, with their physical machine names and service ip addresses. add virtual hostname / ip address to your resource group or use a new resource group (depending on your env) change the entries in db2nodes.cfg to the virtual hostname add virtual hostname / ip address to /etc/hosts add the virtual addresses to your .rhosts file that should do it. -- Helmut K. C. Tessarek DB2 Performance and Development /* * *Thou shalt not follow the NULL pointer for chaos and madness * *await thee at its end. */ |
#4
| |||
| |||
|
|
A better approach than using .rhosts is to build a ssh environment;-) http://www.ibm.com/developerworks/db...nie/index.html |
#5
| |||
| |||
|
|
Hi Joachim, A better approach than using .rhosts is to build a ssh environment;-) http://www.ibm.com/developerworks/db...le/dm-0506finn... You are right, I usually use that approach too, but db2admin did not mention anything about ssh, so I assumed that ssh was not installed. For some reason there are still AIX admins out there who do not install an ssh server on their boxes. -- Helmut K. C. Tessarek DB2 Performance and Development /* * *Thou shalt not follow the NULL pointer for chaos and madness * *await thee at its end. */ |
#6
| |||
| |||
|
|
I have added following entries in files like ~db2inst/.rhosts , ~db2inst1/sqllib/db2nodes.cfg , and /etc/hosts . consider node1 and node2 as nodes $ cat ./sqllib/db2nodes.cfg 0 srv1 0 $ cat .rhosts node1 db2inst1 node2 db2inst1 srv1 db2inst1 $ cat /etc/hosts -------------------lines ommited---------------------------------------- IPaddress srv1 |
#7
| |||
| |||
|
|
Hi, You still seem to have problems with the reverse lookup. What is the output of: # host srv1 srv1.domain.com has address a.b.c.d # host a.b.c.d is the output srv1? You can also try to change your /etcv/hosts file to include the following: ip_of_node1 * *node1 * *node1.domain.com * *srv1 Please also check out the following redbook:http://www.redbooks.ibm.com/redbooks/pdfs/sg247363.pdf There are so many ways to configure DB2 in an HACMP environment and your description is not very detailed. What filesystems are in the resource group? Which filesystems are moved to the other node in case of a failover? What is your virtual IP / hostname? Do you move the instance directory aswell or just the database directory? Are you using rsh or ssh? Do you want to use ssh or are you ok with just rsh? What is the output of 'db2set -all' and 'db2level'? Without a sufficient description of the environment, everything is just abest guess. On 22.6.2010 11:37, db2admin wrote: I have added following entries in files like ~db2inst/.rhosts , ~db2inst1/sqllib/db2nodes.cfg , and /etc/hosts . consider node1 and node2 as nodes $ cat ./sqllib/db2nodes.cfg 0 srv1 0 $ cat .rhosts node1 db2inst1 node2 db2inst1 srv1 db2inst1 $ cat /etc/hosts -------------------lines ommited---------------------------------------- IPaddress * *srv1 -- Helmut K. C. Tessarek DB2 Performance and Development /* * *Thou shalt not follow the NULL pointer for chaos and madness * *await thee at its end. */ |
#8
| |||
| |||
|
|
Then re-run verification and synchronization with the instance home directory mounted on one of the participating nodes of the instance resource group. |
|
ERROR: The DB2 instance owner home directory: /db2inst1/tp_instance for instance: tp_instance, and user: tp_instance is incorrectly set to path: on node: node1 Please change the instance owners home directory on node: csudwhp1 to match the instance owner home directory. |
#9
| |||
| |||
|
|
I think the following paragraphs already explain what you have to do. Then re-run verification and synchronization with the instance home directory mounted on one of the participating nodes of the instance resource group. Your instance home directory does not seem to be mounted. ERROR: The DB2 instance owner home directory: /db2inst1/tp_instance for instance: tp_instance, and user: tp_instance is incorrectly set to path: on node: node1 Please change the instance owners home directory on node: csudwhp1 to match the instance owner home directory. The path value seems to be empty and should be set to the instance owner home directory. -- Helmut K. C. Tessarek DB2 Performance and Development /* * *Thou shalt not follow the NULL pointer for chaos and madness * *await thee at its end. */ |
#10
| |||
| |||
|
|
are you referring to PATH variable? i added db2 instance home directory to the path but error did not go away. |
![]() |
| Thread Tools | |
| Display Modes | |
| |