db2pd -db <dbname> -hadr will give you the status

If you are doing a HADR failover test and both nodes are up you can do a gracefu
l takeover:
d2bw takeover hadr on db <dbname> <-- Note this is run on the failover node, it
will communicate back to the primary. I have not used this on a superasynch stan
dby db, so I am not 100% there are not any differences in takeover procedures.
One thing to keep in mind is you are running superasynch, which by its nature do
es allow for the possibility of some data loss. What I do on my HADR systems is
in a failover situation we automatically try to do a graceful takeover, if that
fails manual intervention is required. This is a bit slower but avoids issues li
ke Split Brain Scenario, Data Loss etc. These issues are rare, but in the event
of a Split Brain Scenario fixing the issue could take a very long tme.
Thanks for the replies.
I wanted to know what parameters in the output obtained from db2pd -hadr needs t
o be checked for getting to know that the standby is missing updates.
For the scenario where primary has crashed suddenly, and takeover is done by for
ce on standby, old primary will not know that the standby is now the new primary
.
If you takeovered the database by force the only way to understand if you have l
ost transactions or not is to try to reintegrate these databases.
You should run on the old primary the following:
Code:
db2 start hadr on db mydb as standby