IBM DB2 v9.7 HADR TSA failure on the standby server I have an environment here where I have 2 servers running DB2.
One is the primary and the other one is standby. They replicate with HADR and failover is made automatically by TSA.

What's the default behaviour when the standby host fails ? Because for now failover is perfect when the primary peer fails. And then I can reintegrate the old primary peer as standby.
But when the standby peer fails, here is my problem, I have to start HADR manually on this peer. Is it normal ?
Ember Crooks works with HADR and TSA a LOT on DB2. (She uses it for WebSphere Commerce, but you can apply the generalities from her posts.)

Here are two posts(#1 and #2) regarding HADR that feature a similar issue to what you are facing. Based off of what she has documented, what you are seeing appears to be normal behavior (or at least expected behavior, even if it isn't desirable).

Check out Ember's blog (the first link in my post). I subscribe to it as I've learned a lot of key things about DB2 operations-especially related to HADR and TSA-from her.