!! Grid Infrastructure Management Repository (GIMR) !!
Every Oracle Standalone Cluster and Oracle Domain Services Cluster contains a Grid Infrastructure Management Repository (GIMR), or the Management Database (MGMTDB).
The Grid Infrastructure Management Repository (GIMR) is a multitenant database with a pluggable database (PDB) for the GIMR of each cluster. The GIMR stores the following information about the cluster:
Real time performance data the Cluster Health Monitor collects
Fault, diagnosis, and metric data the Cluster Health Advisor collects
Cluster-wide events about all resources that Oracle Clusterware collects
CPU architecture data for Quality of Service Management (QoS)
Metadata required for Rapid Home Provisioning
The Oracle Standalone Cluster locally hosts the GIMR on an Oracle ASM disk group; this GIMR is a multitenant database with a single pluggable database (PDB).
The global GIMR runs in an Oracle Domain Services Cluster. Oracle Domain Services Cluster locally hosts the GIMR in a separate Oracle ASM disk group. Client clusters, such as Oracle Member Cluster for Database, use the remote GIMR located on the Domain Services Cluster. For two-node or four-node clusters, hosting the GIMR for a cluster on a remote cluster reduces the overhead of running an extra infrastructure repository on a cluster. The GIMR for an Oracle Domain Services Cluster is a multitenant database with one PDB, and additional PDB for each member cluster that is added.
When you configure an Oracle Domain Services Cluster, the installer prompts to configure a separate Oracle ASM disk group for the GIMR, with the default name as MGMT.
About Oracle Standalone Clusters
An Oracle Standalone Cluster hosts all Oracle Grid Infrastructure services and Oracle ASM locally and requires direct access to shared storage.
Oracle Standalone Clusters contain two types of nodes arranged in a hub and spoke architecture: Hub Nodes and Leaf Nodes. The number of Hub Nodes in an Oracle Standalone Cluster can be as many as 64. The number of Leaf Nodes can be many more. Hub Nodes and Leaf Nodes can host different types of applications. Oracle Standalone Cluster Hub Nodes are tightly connected, and have direct access to shared storage. Leaf Nodes do not require direct access to shared storage. Hub Nodes can run in an Oracle Standalone Cluster configuration without having any Leaf Nodes as cluster member nodes, but Leaf Nodes must be members of a cluster with a pool of Hub Nodes. Shared storage is locally mounted on each of the Hub Nodes, with an Oracle ASM instance available to all Hub Nodes.
Oracle Standalone Clusters host Grid Infrastructure Management Repository (GIMR) locally. The GIMR is a multitenant database, which stores information about the cluster. This information includes the real time performance data the Cluster Health Monitor collects, and includes metadata required for Rapid Home Provisioning.
When you deploy an Oracle Standalone Cluster, you can also choose to configure it as an Oracle Extended cluster. An Oracle Extended Cluster consists of nodes that are located in multiple locations or sites.
About Oracle Cluster Domain and Oracle Domain Services Cluster
An Oracle Cluster Domain is a choice of deployment architecture for new clusters, introduced in Oracle Clusterware 12c Release 2.
Oracle Cluster Domain enables you to standardize, centralize, and optimize your Oracle Real Application Clusters (Oracle RAC) deployment for the private database cloud. Multiple cluster configurations are grouped under an Oracle Cluster Domain for management purposes and make use of shared services available within that Oracle Cluster Domain. The cluster configurations within that Oracle Cluster Domain include Oracle Domain Services Cluster and Oracle Member Clusters.
The Oracle Domain Services Cluster provides centralized services to other clusters within the Oracle Cluster Domain. These services include:
A centralized Grid Infrastructure Management Repository (housing the MGMTDB for each of the clusters within the Oracle Cluster Domain)
Trace File Analyzer (TFA) services, for targeted diagnostic data collection for Oracle Clusterware and Oracle Database
Consolidated Oracle ASM storage management service, including the use of Oracle ACFS.
An optional Rapid Home Provisioning (RHP) Service to install clusters, and provision, patch, and upgrade Oracle Grid Infrastructure and Oracle Database homes. When you configure the Oracle Domain Services Cluster, you can also choose to configure the Rapid Home Provisioning Server.
An Oracle Domain Services Cluster provides these centralized services to Oracle Member Clusters. Oracle Member Clusters use these services for centralized management and to reduce their local resource usage.
About Oracle Member Clusters
Oracle Member Clusters use centralized services from the Oracle Domain Services Cluster and can host databases or applications. Oracle Member Clusters can be of two types - Oracle Member Clusters for Oracle Databases or Oracle Member Clusters for applications.
Oracle Member Clusters do not need direct connectivity to shared disks. Using the shared Oracle ASM service, they can leverage network connectivity to the IO Service or the ACFS Remote Service to access a centrally managed pool of storage. To use shared Oracle ASM services from the Oracle Domain Services Cluster, the member cluster needs connectivity to the Oracle ASM networks of the Oracle Domain Services Cluster.
Oracle Member Clusters cannot provide services to other clusters. For example, you cannot configure and use a member cluster as a GNS server or Rapid Home Provisioning Server.
*. Oracle Member Cluster for Oracle Databases
An Oracle Member Cluster for Oracle Databases supports Oracle Real Application Clusters (Oracle RAC) or Oracle RAC One Node database instances. This cluster registers with the management repository service and uses the centralized TFA service. It can use additional services as needed. An Oracle Member Cluster for Oracle Databases can be configured with local Oracle ASM storage management or make use of the consolidated Oracle ASM storage management service offered by the Oracle Domain Services Cluster.
An Oracle Member Cluster for Oracle Database always uses remote Grid Infrastructure Management Repository (GIMR) from its Oracle Domain Services Cluster. For two-node or four-node clusters, hosting the GIMR on a remote cluster reduces the overhead of running an extra infrastructure repository on a cluster.
*. Oracle Member Cluster for Applications
Oracle Member Cluster for Applications hosts applications other than Oracle Database, as part of an Oracle Cluster Domain. The Oracle Member Cluster requires connectivity to Oracle Cluster Domain Services for centralized management and resource efficiency. The Oracle Member Cluster uses remote Oracle ASM storage, with any required shared storage provided through the Oracle ACFS Remote service. This cluster configuration enables high availability of any software application.
Unlike other cluster configurations that require public and private network interconnects, the Oracle Member Cluster for Application can be configured to use a single public network interface.
Parent topic: Configuring Storage for Oracle Automatic Storage Management
Every Oracle Standalone Cluster and Oracle Domain Services Cluster contains a Grid Infrastructure Management Repository (GIMR), or the Management Database (MGMTDB).
The Grid Infrastructure Management Repository (GIMR) is a multitenant database with a pluggable database (PDB) for the GIMR of each cluster. The GIMR stores the following information about the cluster:
Real time performance data the Cluster Health Monitor collects
Fault, diagnosis, and metric data the Cluster Health Advisor collects
Cluster-wide events about all resources that Oracle Clusterware collects
CPU architecture data for Quality of Service Management (QoS)
Metadata required for Rapid Home Provisioning
The Oracle Standalone Cluster locally hosts the GIMR on an Oracle ASM disk group; this GIMR is a multitenant database with a single pluggable database (PDB).
The global GIMR runs in an Oracle Domain Services Cluster. Oracle Domain Services Cluster locally hosts the GIMR in a separate Oracle ASM disk group. Client clusters, such as Oracle Member Cluster for Database, use the remote GIMR located on the Domain Services Cluster. For two-node or four-node clusters, hosting the GIMR for a cluster on a remote cluster reduces the overhead of running an extra infrastructure repository on a cluster. The GIMR for an Oracle Domain Services Cluster is a multitenant database with one PDB, and additional PDB for each member cluster that is added.
When you configure an Oracle Domain Services Cluster, the installer prompts to configure a separate Oracle ASM disk group for the GIMR, with the default name as MGMT.
About Oracle Standalone Clusters
An Oracle Standalone Cluster hosts all Oracle Grid Infrastructure services and Oracle ASM locally and requires direct access to shared storage.
Oracle Standalone Clusters contain two types of nodes arranged in a hub and spoke architecture: Hub Nodes and Leaf Nodes. The number of Hub Nodes in an Oracle Standalone Cluster can be as many as 64. The number of Leaf Nodes can be many more. Hub Nodes and Leaf Nodes can host different types of applications. Oracle Standalone Cluster Hub Nodes are tightly connected, and have direct access to shared storage. Leaf Nodes do not require direct access to shared storage. Hub Nodes can run in an Oracle Standalone Cluster configuration without having any Leaf Nodes as cluster member nodes, but Leaf Nodes must be members of a cluster with a pool of Hub Nodes. Shared storage is locally mounted on each of the Hub Nodes, with an Oracle ASM instance available to all Hub Nodes.
Oracle Standalone Clusters host Grid Infrastructure Management Repository (GIMR) locally. The GIMR is a multitenant database, which stores information about the cluster. This information includes the real time performance data the Cluster Health Monitor collects, and includes metadata required for Rapid Home Provisioning.
When you deploy an Oracle Standalone Cluster, you can also choose to configure it as an Oracle Extended cluster. An Oracle Extended Cluster consists of nodes that are located in multiple locations or sites.
About Oracle Cluster Domain and Oracle Domain Services Cluster
An Oracle Cluster Domain is a choice of deployment architecture for new clusters, introduced in Oracle Clusterware 12c Release 2.
Oracle Cluster Domain enables you to standardize, centralize, and optimize your Oracle Real Application Clusters (Oracle RAC) deployment for the private database cloud. Multiple cluster configurations are grouped under an Oracle Cluster Domain for management purposes and make use of shared services available within that Oracle Cluster Domain. The cluster configurations within that Oracle Cluster Domain include Oracle Domain Services Cluster and Oracle Member Clusters.
The Oracle Domain Services Cluster provides centralized services to other clusters within the Oracle Cluster Domain. These services include:
A centralized Grid Infrastructure Management Repository (housing the MGMTDB for each of the clusters within the Oracle Cluster Domain)
Trace File Analyzer (TFA) services, for targeted diagnostic data collection for Oracle Clusterware and Oracle Database
Consolidated Oracle ASM storage management service, including the use of Oracle ACFS.
An optional Rapid Home Provisioning (RHP) Service to install clusters, and provision, patch, and upgrade Oracle Grid Infrastructure and Oracle Database homes. When you configure the Oracle Domain Services Cluster, you can also choose to configure the Rapid Home Provisioning Server.
An Oracle Domain Services Cluster provides these centralized services to Oracle Member Clusters. Oracle Member Clusters use these services for centralized management and to reduce their local resource usage.
About Oracle Member Clusters
Oracle Member Clusters use centralized services from the Oracle Domain Services Cluster and can host databases or applications. Oracle Member Clusters can be of two types - Oracle Member Clusters for Oracle Databases or Oracle Member Clusters for applications.
Oracle Member Clusters do not need direct connectivity to shared disks. Using the shared Oracle ASM service, they can leverage network connectivity to the IO Service or the ACFS Remote Service to access a centrally managed pool of storage. To use shared Oracle ASM services from the Oracle Domain Services Cluster, the member cluster needs connectivity to the Oracle ASM networks of the Oracle Domain Services Cluster.
Oracle Member Clusters cannot provide services to other clusters. For example, you cannot configure and use a member cluster as a GNS server or Rapid Home Provisioning Server.
*. Oracle Member Cluster for Oracle Databases
An Oracle Member Cluster for Oracle Databases supports Oracle Real Application Clusters (Oracle RAC) or Oracle RAC One Node database instances. This cluster registers with the management repository service and uses the centralized TFA service. It can use additional services as needed. An Oracle Member Cluster for Oracle Databases can be configured with local Oracle ASM storage management or make use of the consolidated Oracle ASM storage management service offered by the Oracle Domain Services Cluster.
An Oracle Member Cluster for Oracle Database always uses remote Grid Infrastructure Management Repository (GIMR) from its Oracle Domain Services Cluster. For two-node or four-node clusters, hosting the GIMR on a remote cluster reduces the overhead of running an extra infrastructure repository on a cluster.
*. Oracle Member Cluster for Applications
Oracle Member Cluster for Applications hosts applications other than Oracle Database, as part of an Oracle Cluster Domain. The Oracle Member Cluster requires connectivity to Oracle Cluster Domain Services for centralized management and resource efficiency. The Oracle Member Cluster uses remote Oracle ASM storage, with any required shared storage provided through the Oracle ACFS Remote service. This cluster configuration enables high availability of any software application.
Unlike other cluster configurations that require public and private network interconnects, the Oracle Member Cluster for Application can be configured to use a single public network interface.
Parent topic: Configuring Storage for Oracle Automatic Storage Management
