db2haicu TSAMP Advanced Topics: Objects Created

You may also like...

6 Responses

  1. Luiz da Silva says:

    Hi Ember,

    I faced before a situation where not all databases were not failed over together. Do you follow any best practice/rule of thumb in your environments? Maybe a next post topic to explore? 🙂


    • Ember Crooks says:

      Databases are not failed over together by default. You would have to create a relationship to make that happen. I don’t have the syntax for how to make that happen, but it would be a TSAMP command and not a db2 command.

  2. Steven Raspudic says:

    Ember, the granularity of failover is at the *database level*. i.e. db2haicu is hooked into the runtime for HADR failover (TAKEOVER, TAKEOVER BY FORCE, etc.), and these HADR state change commands are at the granulaity of the *database*. Hence, anything that ties together multiple databases is problematic (i.e. a shared VIP). The granularity of HADR TAKEOVER is then multiple databases. Anyhow, there’s no real reason to use VIPs anymore (it isn’t the 1980’s anymore), just use ACR. Cheers,

    • Ember Crooks says:

      I have found a number of applications don’t play nice with ACR and have to be manually configured to be aware of the standby, including those like WebSphere Commerce that use JDBC type 4 drivers. A virtual IP is much easier for many of my clients than ACR.

  1. August 18, 2015

    […] db2haicu TSAMP Advanced Topics: Objects Created […]

  2. January 26, 2016

    […] db2haicu TSAMP Advanced Topics: Objects Created […]

Leave a Reply

Your email address will not be published. Required fields are marked *