Support Policies for RHEL High Availability Clusters - Management of Oracle ASM Services in a Cluster

Contents

• Overview
  • Applicable Environments
  • Useful References and Guides
  • Introduction
• Policies

Overview

Applicable Environments

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

Useful References and Guides

• Support Policies for RHEL High Availability Clusters

Introduction

This guide offers Red Hat's policies and requirements around managing Oracle ASM services 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 Oracle ASM services 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 Oracle software deployments in a RHEL High Availability cluster.

• Support policies: General policies for cluster managed resources and applications

The focus of Red Hat's assistance may be limited to functionality of the High Availability software and the oraasm agent(s). In some cases Oracle'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 + Oracle ASM deployments may be dependent upon some input or deliverable from Oracle in cases where the issue can not be solved adequately through RHEL High Availability without Oracle's assistance.

ocf:heartbeat:oraasm pacemaker resource-agent compatibility with Oracle releases: Red Hat does not define specific product version compatibility for this agent in relation to ASM. In other words: the agent was developed to use generally accepted commands and practices to manage the availability of Oracle's ASM services, and those practices are not known to be version-specific or incompatible with any currently supported Oracle product 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 Oracle software, this article will be updated to reflect that condition.

There are known limitations for the oraasm resource that is outlined in the following solution: Can multiple oraasm resources be managed on a pacemaker cluster?