Especially with TSA and db2haicu, sometimes you see an error, and you have a bag of tricks that you try, even though you don’t understand exactly why they work. In this case, I had a brand-spanking-new server, with DB2 installed the very same day, and no matter what I did, db2haicu would fail on creating the domain with this error message in the diag.log:
Line # : 9386---2632-044 The domain cannot be created due to the following errors that were detected while harvesting information from the target nodes: dbserver1.adomain.com: 2632-075 This node has a duplicate IP address (xxx.xxx.xxx.xxx) with node dbserver2.adomain.com. The duplicate address will not be used. Correct the network configuration on one of the nodes or use -c option to perform the operation.
On looking at an ifconfig, we saw, in part:
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.yyy Mask:255.255.255.0
inet6 addr: aaaa::aaa:aa:aaaa:a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:7239 (7.0 KiB)
So the Client’s DBA and I tried everything I could possibly think of before going back to the network/server team. The last thing on my list to try was uninstalling/re-installing the TSA software, as I described in this post: Using TSA/db2haicu to Automate Failover Part 3: Testing, Ways Setup can go Wrong and What to do (section “Other Failures”, #3)
And that worked. Again, don’t know why since we had just installed the server the same day, but in case someone sees a similar issue, I thought I’d put the solution out there.
