when I do a failover, hacmp always starts db2 but recently it fails to start db2..noticed the issue is db2nodes.cfg is not modified by hacmp and is still showing primary node..manually changed the node name to secondary after which db2 started immediately..unable to figure out why hacmp is not doing it automatically as it should.. I have checked permissions, all configuration I can think of and even compared to working ones but could not find any diff...any help on the issue is greatly appreciated.
As I understand, modification of db2nodes.cfg file is the responsiblity of the DB2 start script. So, if that is not happening then something is wrong in the DB script and not an issue with HACMP configuration itself?
In simple, HACMP is not directly responsible for modifying this file with the correct nodename..right? instead it should be the DB2 start script(which is initiated by HACMP) that should be doing it?