Oracle Support Master Note for Configuring 10g Grid Control Components for High Availability

 

 

For most current information refer How To Configure Grid Control Components for High Availability (Doc ID 330072.1)

 

 

 

In this Document
  Purpose
  
Scope and Application
  
How To Configure Grid Control Components for High Availability
     
Background and Terminology
     
Management Agent
     
Oracle Management Service (OMS)
     
Management Repository (MR)
  
References


Applies to:

Enterprise Manager Grid Control - Version: 10.2.0.1 to 10.2.0.5 - Release: 10.2 to 10.2
Information in this document applies to any platform.

Purpose

This document provides a general reference for Grid Control administrators on configuring 10g Grid Control for High Availability (HA).

Scope and Application

All Unix platforms; not tested for Windows
This document provides a general reference for Grid Control administrators on configuring 10g Grid Control for High Availability.

How To Configure Grid Control Components for High Availability

Grid Control deployments in Fail-Over and HA configurations.

Background and Terminology



Oracle's Enterprise Manager Grid Control (EM GC) has an architecture that is engineered to be scalable and available. Maximum Availability Architecture (MAA) provides a highly available Enterprise Manager implementation by guarding against failure at each component of EM. Each Grid Control component can be configured in various ways to achieve HA. This paper describes the supported configurations of each component, and Oracles recommendation for MAA.

Generally speaking, the overall flow of HA for Grid Control is as follows:

  • Highly available services (targets) are monitored by Agents that upload to highly available and/or load balanced group of OMSs
  • Each OMS loads data received from agents into a highly available repository database
  • Each repository database instance can be configured for redundancy, failover and/or disaster recovery.

 

Management Agent

A native process responsible for monitoring your data center resources such as Database, Application servers etc, and communicating with the Oracle Management Service.

Agents are installed on each host to monitor the services associated with the host. One agent is required for each host in any configuration. 
For installing the Agent in Oracle Real Application Cluster (RAC) configurations, please refer to: " 
Note:378037.1 How To Install Oracle 10g Grid Agent On RAC ". 

For environments that utilize a virtual hostname, such as: 

  • SunCluster
  • Veritas VCS
  • IBM HACMP
  • HP MC ServiceGuard
  • etc. 

Please see: Note:406014.1 How to Configure Grid Control Agents to Monitor Virtual Hostname in HA environments

For Windows FailSafe configurations, please refer to: 
http://www.oracle.com/technology/products/oem/deployments/fs_with_gc.pdf

Oracle Management Service (OMS)


A J2EE application that processes the information collected by the agents, renders the EM Grid Control Console GUI and uses the Repository to store the data.

Active/Passive

An active-passive configuration involves two hardware nodes with a single node running an OMS instance (active) at a time. The node that primarily hosts OMS is called the active node; the node or sets of nodes that can potentially host the OMS are called the passive nodes

Active/Active (MAA) Configuration 

In an active-active configuration, two or more OMS instances are configured to serve the same application workload. These instances can reside on the same machine as the repository (described below) or on different machines. They are all active instances front-ended by a load balancer router, which can redirect requests to any of the active instances.

For information on configuring the OMS using a virtual hostname, please refer to 
Note:405642.1

For information on configuring multiple OMSs using a load balancer, please refer to the Advanced Configuration Guide Chapter 3

Management Repository (MR)


An Oracle database that stores EM data within a special schema.  All best practices normally associated with Database High Availability such as RMAN backups and Flashback Technology can be applied.  The repository can be configured using either Active/Passive or Active/Active (RAC) solutions with Data Guard (DG) for Data Recovery.

To configure the repository in a failover group using a virtual hostname, please refer to 
Note:405979.1

To configure the repository using RAC for the database repository, including DG please refer to the Advanced Configuration Guide Chapter 11

Form more information on Database high availability best practices, please refer to the Database High Availability Best Practices Guide.

DBControl/DBConsole can also support virtual hostnames starting 10.2.0.2 
Please refer to 
Note:362524.1 for details.

References

NOTE:353074.1 - How to configure Pre-Release 10.2.0.4 Grid Control 10.2 Management Servers behind a Server Load Balancer (SLB)
NOTE:362524.1 - Configure DB Control 10.2, 11g for use in Active/Passive High Availability Environments
NOTE:378037.1 - How To Install Grid Control Agents On RAC Clusters
NOTE:405642.1 - How to Configure Grid Control OMS in Active/Passive CFC Environments failover / HA
NOTE:405979.1 - How to Configure Grid Control Repository in Active/Passive HA environments
NOTE:406014.1 - How to Configure Grid Control Agents to Monitor Virtual Hostname in HA environments
NOTE:464191.1 - How to Configure Grid Control Agents in Windows HA - Failover Cluster Environments
NOTE:473412.1 - How to configure and add a new Grid Control Management Service (OMS) Release 10.2.0.4 behind a SLB
NOTE:549848.1 - How to configure and add a new Grid Control Management Service (OMS) Pre-Release 10.2.0.4 behind a SLB
NOTE:549861.1 - How to reconfigure the Server load Balancer (SLB) after the Grid Control OMS is ugraded to 10.2.0.4
NOTE:577443.1 - How to Setup and Configure Target Relocate using EMCLI
NOTE:579893.1 - How To Install Grid Control OMS on Windows in CFC Configuration
NOTE:731652.1 - How to Configure SSO with Grid Control While Using an SLB
NOTE:866732.1 - How to Configure 2 OMSs Using F5 BigIP SLB
Enterprise Manager 10G R2 MAA Best Practices at 
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_EnterpriseManagerBestPractices.pdf
Highly Available Management Agent with Oracle Fail Safe http://www.oracle.com/technology/products/oem/deployments/fs_with_gc.pdf
FailSafe Release Notes http://download.oracle.com/docs/html/B25003_01/toc.htm#BABCHGJD

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

News and Troubleshooting tips for Oracle Database and Enterprise Manager

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today