Webthere were no tsa initiated or hadr takeover commands seen in db2diag. logs on primary and standby. So we checked the next possible place and we found the reason.

Understanding the Context

Webif you review the error text for adm12509e reason code 1, you will see it stated: The hadr primary database cannot find a log file that was requested by the standby. Hadr will attempt to recover from the condition by disconnecting and then reconnecting the. Error [] [ibm][db2/nt64] sql1773n the statement or command failed because it requires functionality that is not supported. Sql1776n rc 1 errors constantly seen in the standby db2diag.

Key Insights

log when there were no active connections from remote applications. Web — sql1767n rc 1 means that the standby (not primary) database is not in the correct state when you try to start hadr, and in particular, it is not marked as being. Webtakeover hadr cannot complete. The takeover hadr command failed. The explanation corresponding to the reason code is: The hadr_role is principal for some databases and standby for others, or no hadr.

Final Thoughts

Webhadr (high availability disaster recovery) is a db2 luw feature for high availability and disaster recovery. It is the preferred solution for ha and dr on db2. It replicates data in. Web — reason code = 1. The knowledge center says this about that error: Start hadr cannot complete. The explanation corresponding to the reason code is: Sql1768n unable to start hadr.

Reason code = 6. Zrc, pd_type_zrc, 4 bytes 0x87800143. Webhadr (high availability disaster recovery) is a db2 luw feature for high availability and disaster recovery. It is the preferred solution for ha and dr on db2.