It has been quite a while since I posted, going forward you will see this blob becoming much more active.
I am now in a new role in the Tech Sales organization for IBM Analytics, supporting all North American sales teams. I continue to focus primarily on DB2, in all of its new forms - on-prem, in the cloud, or in an appliance form factor.
I will now use this blog to document solutions to issues I encounter while deploying systems at customer sites or deploying in the cloud.
The first such entry involves enabling automation of HADR Takeovers, yes I still focus on resiliency.
While setting up a system for one of my clients I came across an interesting limitation that appears to be poorly documented.
If you are setting up TSA to automate HADR takeovers on an environment that is using dual NICs, one for public access and one for private HADR log transmission, you can not use a HOSTNAME for the private network. You must use the actually IP address, which should not be an issue as your apps will never use this IP address to connect to the DB.
If you are having challenges setting up HADR automation please let me know, I am working on an updated DB2HAICU white paper. We also have an excellent HADR PoT that focuses on TSA automation that can be provided at your site.