During addition of the network interface to the HA network, the
db2haicu tool might return error:
Adding network interface card 'eth0' on cluster node 'node02' to
the network 'db2_public_network_0' ...
Object creation failed because that object already exists.
In addition to error reported via db2haicu tool, during problem
occurrence you might also notice entry in the db2diag.log:
2015-01-07-08.30.05.026253-300 E164795E564 LEVEL:
Error
PID : 21417 TID : 140008616036096 PROC :
db2haicu
INSTANCE: db2inst1 NODE : 000
HOSTNAME: node01
FUNCTION: DB2 UDB, high avail services, sqlhaUIAddNICToNetwork,
probe:10
RETCODE : ECF=0x90000551=-1879046831=ECF_SQLHA_OBJECT_EXISTS
Cluster object already exists
MESSAGE : Failed to update the network equivalency.
DATA #1 : String, 20 bytes
db2_public_network_0
DATA #2 : String, 4 bytes
eth0
DATA #3 : String, 6 bytes
node01
DATA #4 : Boolean, 1 bytes
true
Above error is returned in scenario when db2haicu is executed in
maintenance mode to perform network setup. The error is returned
during addition of the second network interface to the network,
due to fact that db2haicu creates relationships to the newly
created db2_public_network_0 network equivalency when the first
network interface is added, and then it tries to create the same
relationships after adding another node to the existing network
equivalency.
Further more, even though the error is returned, the network
interface is correctly added. You can verify in the lssam output
afterwards:
Online IBM.Equivalency:db2_public_network_0
|- Online IBM.NetworkInterface:eth0:node01
'- Online IBM.NetworkInterface:eth0:node02 |
