If you have set up DB2 10.1 Active / Passive or HADR with TSA, the db2haicu command sets up the cluster manager DBM CFG to TSA and there is no way you can unset that by using db2 update dbm cfg command as it can only be done by the application and that is in our case is the db2haicu command.
Why do you need to do this?
Sometime it may be necessary to break the connection for the testing, maintenance, upgrade purposes etc. When you break the connetion, TSA and DB2 are not tied together anymore and you can always enable that connection later on.
Assuming that you already have db2 enabled with TSA and this can be DB2 Active / Passive, HADR with TSA and DB2 pureScale.
$ db2 get dbm cfg | grep –i cluster
If the above output shows that the Cluster Manager is set to TSA, it means that TSA is sitting in front of DB2 to regulate it.
Type $ db2haicu –disable to disable DB2’s integration with TSA.
Hit Enter to confirm that you want to disable TSA for DB2 and again check $ db2 get dbm cfg | grep –i cluster and this time it should show as blank. With this, DB2 is separated from TSA but this does not mean that TSA resources have been disabled. You can do the testing on TSA and DB2 and when it is time to establish the connection, again run command db2haicu and confirm to use TSA as the cluster manager.