We have db2 10.5.0.5 on Centos 6.7 and use tsamp 3.2 to achieve high availability. We follow the steps required to implement high availability using tsamp, after sometimes when we check the CLUSTER_MGR parameter of the database manager it was null in the primary database, but in the lssam output every thing was correct, at this time we have a takeover and the database resource group remains in Pending offline for some minutes and then changes to Stuck online. We haven't find the reason of this event, can any one help us?