Support Policy for RHEL High Availability Clusters - Management of IBM Db2 for Linux, Unix, and Windows in a Cluster

Updated -

Contents

Overview

Applicable Environments

  • Red Hat Enterprise Linux (RHEL) with the High Availability Add-On

Useful References and Guides

Introduction

This guide offers Red Hat's policies and requirements around managing IBM Db2 for Linux, Unix, and Windows - IBM Db2 LUW - also formerly referred to as IBM Db2 UDB - with a RHEL High Availability cluster. Users of RHEL High Availability clusters should adhere to these policies in order to be eligible for support from Red Hat with the appropriate product support subscriptions.

Policies

Scope of Red Hat support with IBM Db2 resources managed by a cluster: Refer to Red Hat's policy on Management of applications that Red Hat does not ship for further details on Red Hat's scope of support applicable to Db2 software deployments in a RHEL High Availability cluster.

The focus of Red Hat's assistance may be limited to functionality of the High Availability software and the db2 agent. In some cases IBM's input may be necessary to diagnose the nature of a problem - even if the problem originates in the resource-agent Red Hat ships. Solutions to problems with RHEL High Availability + Db2 deployments may be dependent upon some input or deliverable from IBM in cases where the issue can not be solved adequately through RHEL High Availability without IBM's assistance.


ocf:heartbeat:db2 pacemaker resource-agent compatibility with IBM Db2: Red Hat does not define specific product version compatibility for this agent in relation to Db2. In other words: the agent was developed to use generally accepted commands and practices to manage the availability of Db2 databases, and those practices are not known to be version-specific or incompatible with any IBM Db2 LUW release. However, it is possible that some version of the software may be or may become incompatible with this agent's practices, and therefore Red Hat recommends testing any new deployment with this agent thoroughly to ensure desired functionality.

If any defect or undesired behavior is observed, please contact Red Hat Support for assistance in diagnosing and addressing the concern.

If Red Hat becomes aware of any incompatibility or caveat in relation to the usage of this agent with IBM Db2, this article will be updated to reflect that condition.

Comments