An Unfortunate Series of TSAMP Events

You may also like...

6 Responses

  1. Éric Castro says:

    Hi Ember, great post and history.

    I did not know its not possible to set CLUSTER_MGR anymore except by db2haicu.

    I think what you could have done to completely erase TSA configuration its to list and remove the domain using root. Like this:

    [root@server1 ~]# lsrpdomain
    Name OpState RSCTActiveVersion MixedVersions TSPort GSPort
    dpa_domain Pending online No 12347 12348
    [root@server1 ~]#

    [root@server1 ~]# rmrpdomain -f dpa_domain

    I’ve done this a few time when I couldn’t use db2haicu to delete TSA configuration. But the instance parameter CLUSTER_MGR is still there.

    I don’t know if its an IBM best practice but it worked.

    • Ember Crooks says:

      I believe my SA did just that for me.

      • Kishore says:

        Hello Ember,

        Great Post. Intially i tried your solution

        When i had same issue again, i carefully removed all the resource associated with database and was able to manage to bring instance up.


  2. KR says:


    Nice article, great blog.

    Not sure if this was an option at your DB2 level (or would have helped even if it was) but I had a similar issue and the following allowed me to start DB2 again:

    db2haicu -disable

    I notice after running this, CLUSTER_MGR gets unset.

  1. June 24, 2014

    […] An Unfortunate Series of TSAMP Events […]

Leave a Reply

Your email address will not be published. Required fields are marked *