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 Number of Zones and Clusters
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
To better understand the number of cores available for zones on certain types of Database Domains, consider the example configuration as described in Example Configuration, where:
Your Oracle SuperCluster M6-32 consists of one compute server with two fully-populated DCUs.
The R1_1 PDomain configuration is set up on the compute server (see Four Fully-Populated DCUs (R1_1 PDomain Configuration) for more information).
The E4-4 LDom configuration (four LDoms) is set up on the R1_1 PDomain configuration (see E4-4 LDom Configuration for more information).
The following LDom types are assigned to each LDom in the E4-4 LDom configuration:
LDom 1: Database Domain (without zones)
LDom 2: Solaris 10 Application Domain
LDom 3: Solaris 11 Application Domain
LDom 4: Database Domain with zones, with four zones
For the purposes of this exercise, assume the following:
No zones will be set up on LDom 1 (the second Database Domain) in both PDomains.
Four zones will be set up on LDom 4 (the first Database Domain) in both PDomains.
Using the information provided in the following sections:
You can determine the following information about the two Database Domains on each PDomain:
120 total cores are available for LDom 1 (the first Database Domain).
24 total cores are available for LDom 4 (the second Database Domain).
The following sections describe how cores could be allocated in both of these Database Domains:
This Database Domain has 120 cores available to it, but this Database Domain will not contain any zones. The Database Domain is still considered the global zone in this situation, but because there are no zones in this LDom, all 120 cores are available for this Database Domain, so you could allocate all 120 cores to this Database Domain on both PDomains.
This Database Domain will contain four zones, which means that:
The Database Domain will be the global zone.
The four zones within the Database Domain will be nonglobal zones.
Because this Database Domain on each PDomain will contain four zones, and it has 24 cores available to it, it would appear at first that you could create four equal-sized zones with regards to the number of cores, where each zone would have six cores (24 / 4 = 6).
However, based on the information provided in Cores Available for Domains and Zones, a certain number of cores will be set aside for the global zone. For this specific domain, four cores will be set aside for the global zone, so you actually have 20 cores available for the four zones in this Database Domain. So, for the zones in this Database Domain, you could allocate five cores for each of the four zones to use all 20 cores available for zones in this Database Domain (20 / 4 = 5).