Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle SuperCluster M6-32 Zones With Oracle Database on Database Domains Configuration Guide |
Planning to Set Up Zones on Database Domains
Extended Configuration PDomain Overview
Understanding Extended Configuration PDomains
Understanding Base Configuration PDomains
Understanding LDom Configurations for Extended Configuration PDomains
Understanding LDom Configurations for Base Configuration PDomains
Determining the Cores Available for LDoms and Zones
Cores Available for Domains and Zones
Zones and Cluster Planning for Database Domains
Guidelines for Planning the Storage Server Disk Group Layout
Planning the Storage Server Disk Group Layout
Understanding an Example Scenario
Recording Your Existing and Planned Configuration Information
Recording Your Zone Configuration Information
Recording Your Cluster Configuration Information
Recording Your Storage Server Disk Group Layout
Preparing to Configure Zones on Database Domains
Determine the Repository Location
Install or Update Packages From the Remote Repository
Install or Update Files From the Local Repository
Verify Configuration Tool Installation
Creating Configuration Files (OEDA)
Verify Storage Server Disk Space for Additional Zones
Locate the Necessary Files to Set Up Zones
Import the Most Recent OEDA Configuration File
Review Existing Configuration Information
Review the Information in the Identify Compute Node Operating System Page
Review the Information in the Management and Private Networks Page
Complete the Define Clusters Page
Set Zone Default Configurations
Complete the Cluster Review and Edit SCAN, Client, VIP, and Optional Backup Networks Page
Verify Remaining Configuration Information
Generate the Configuration Files
Creating the Template Zone on Each Database Domain
Create a Template Zone on a Database Domain
Delete a Template Zone From a Database Domain
Determining if Additional VNETs Are Needed for a Database Domain
Determine if Additional VNETs Are Needed (Using Specific LDom Information)
Determine if Additional VNETs Are Needed (Using Software Commands)
Set Up Public Key Authentication for ZFS Storage Controllers
Creating Additional Links on the IB Storage Network for Zones
Create Additional Links on the IB Storage Network for Zones
Following are a list of guidelines regarding zones and clusters on the Database Domains:
When you first install the operating system instances on a domain, that domain is automatically designated as the global zone. Any zones that you create from that point forward on that domain are nonglobal zones.
Global zones and nonglobal zones cannot run RAC clusterware in the same domain. When a Database Domain is created and an operating system is installed on the Database Domain, that domain is considered a global zone. The following scenarios describe what is and is not acceptable in that situation:
If you have two Database Domains (global zones) and those Database Domains are members of a cluster, you cannot create zones on those Database Domains and have those zones as members of their own clusters. Because those zones would be considered nonglobal zones, you cannot have those nonglobal zones running RAC clusterware within Database Domains that are also running RAC clusterware.
If you have two Database Domains (global zones) but those Database Domains are not members of a cluster, then you can create zones on those Database Domains and have those zones as members of their own clusters.
You can create clusters with zones that are of different sizes. However, each zone that is a member of a cluster should be the same size with regards to the number of cores being used by each zone in the cluster. For example, if you are creating a two-node cluster and the first zone in that cluster uses four cores, the other zone in that cluster should also use four cores.
You can cluster zones together across multiple Database Domains that are of different sizes. For example, you can create a two-node cluster, where there is one zone each on two Database Domains, and those zones are clustered together, even if one of the Database Domains is a different size from the other Database Domain. The private interface connections (the IB connections) are limited to the lower number from the smaller LDom, based on the IB HCAs available to the zone.
When creating zones on a Database Domain, if the last zone that you are creating on that LDom uses the last remaining core available in that LDom, then that zone is configured with no CPU resource controls. For example, assume you are creating zones on the first LDom in an E4-4 LDom configuration, so four cores would be set aside for the global zone based on the information provided in Determining the Cores Available for LDoms and Zones. You could therefore have a maximum of 116 single-core zones on this LDom. In this case, the 116th and final zone in the domain is configured with no CPU resource controls. This zone shares the core and VCPUs with the global zone in this case.
To minimize remote memory accesses, allocate physical memory to each of the zones in multiples of 16 GB or 32 GB, depending on the DIMM size you have in your system, to align with the size of the memory banks on the server.
While it is possible to create a cluster with the zones in the same Database Domain or on the same PDomain, that configuration is not a highly-available configuration. Instead, create clusters where the zones are on separate Database Domains, and the cluster spans across multiple PDomains, so that there is not a single point of failure.