JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle SuperCluster M6-32 Zones With Oracle Database on Database Domains

Configuration Guide

search filter icon
search icon

Document Information

Using This Documentation

Product Notes

Related Documentation

Feedback

Access to Oracle Support

Planning to Set Up Zones on Database Domains

Important Cautions

Naming Conventions

Understanding PDomains

PDomains Overview

PDomain Guidelines

Extended Configuration PDomain Overview

Understanding Extended Configuration PDomains

Base Configuration Overview

Understanding Base Configuration PDomains

Understanding LDoms

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

Example Configuration

Memory Available for LDoms

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

Prepare to Configure Zones

Update the Base Software

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)

Example Configuration

Verify Storage Server Disk Space for Additional Zones

Locate the Necessary Files to Set Up Zones

Set Up the OEDA

Start the OEDA

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 Page

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

Creating VNETs

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)

Locate the Control Domain

Create VNETs for Zones

Delete VNETs

Running the Java OneCommand

Set Up Public Key Authentication for ZFS Storage Controllers

Set Up the Java OneCommand

Run the Java OneCommand

NTP Issue

Creating Additional Links on the IB Storage Network for Zones

Create Additional Links on the IB Storage Network for Zones

Setting Up VLAN Tagging for Zones

Set Up VLAN Tagging for Zones

Index

Cores Available for Domains and Zones

The number of cores available for LDoms, and for zones within those LDoms, varies depending on the following factors:

Each CMU contains two CMPs, and each CMP contains one twelve-core SPARC M6 processor. The number of CMUs and CMPs that are associated with a specific domain varies, depending on the type of configuration PDomain that you have on each compute server and the type of LDom configuration that you have on the PDomain.

When you first install the operating system instances on an LDom, that LDom is automatically designated as the global zone. When creating zones on Database Domains, the Database Domain is designated as the global zone. The zones created on that Database Domain are designated as nonglobal zones.

A certain number of cores are always set aside for the global zone, and the remaining cores in the Database Domain are available for the nonglobal zones (the zones in the Database Domain). The number of cores that are set aside for the global zone varies, depending on the factors mentioned previously.

The following tables provide information on the number of cores that are available for specific LDoms and zones that are created within those LDoms. See Understanding LDoms for more information on the different types of PDomain and LDom configurations.

Table 33 Cores Available for Extended Configuration PDomains (Fully-Populated DCU Configurations)

LDom Configuration
Total Number of Cores Available for LDoms in This Configuration
Number of Cores Set Aside for Global Zone
Number of Cores Available for Nonglobal Zones
E4-1
LDom 1: 192
LDom 1: 4
LDom 1: 188
E4-2
  • LDom 1: 144
  • LDom 2: 48

  • LDom 1: 4
  • LDom 2: 4

  • LDom 1: 140
  • LDom 2: 44

E4-3
  • LDom 1: 144
  • LDom 2: 24

  • LDom 3: 24

  • LDom 1: 4
  • LDom 2: 4

  • LDom 3: 4

  • LDom 1: 140
  • LDom 2: 20

  • LDom 3: 20

E4-4
  • LDom 1: 120
  • LDom 2: 24

  • LDom 3: 24

  • LDom 4: 24

  • LDom 1: 4
  • LDom 2: 4

  • LDom 3: 4

  • LDom 4: 4

  • LDom 1: 116
  • LDom 2: 20

  • LDom 3: 20

  • LDom 4: 20

Table 34 Cores Available for Extended Configuration PDomains (Half-Populated DCU Configurations)

LDom Configuration
Total Number of Cores Available for Domains in This Configuration
Number of Cores Set Aside for Global Zone
Number of Cores Available for Nonglobal Zones
E2-1
LDom 1: 96
LDom 1: 4
LDom 1: 92
E2-2
  • LDom 1: 72
  • LDom 2: 24

  • LDom 1: 4
  • LDom 2: 4

  • LDom 1: 68
  • LDom 2: 20

E2-3
  • LDom 1: 72
  • LDom 2: 12

  • LDom 3: 12

  • LDom 1: 4
  • LDom 2: 2

  • LDom 3: 2

  • LDom 1: 68
  • LDom 2: 10

  • LDom 3: 10

E2-4
  • LDom 1: 60
  • LDom 2: 12

  • LDom 3: 12

  • LDom 4: 12

  • LDom 1: 4
  • LDom 2: 2

  • LDom 3: 2

  • LDom 4: 2

  • LDom 1: 56
  • LDom 2: 10

  • LDom 3: 10

  • LDom 4: 10

Table 35 Cores Available for Base Configuration PDomains (Fully-Populated DCU Configurations)

LDom Configuration
Total Number of Cores Available for Domains in This Configuration
Number of Cores Set Aside for Global Zone
Number of Cores Available for Nonglobal Zones
B4-1
LDom 1: 96
LDom 1: 4
LDom 1: 92
B4-2
  • LDom 1: 48
  • LDom 2: 48

  • LDom 1: 4
  • LDom 2: 4

  • LDom 1: 44
  • LDom 2: 44

B4-3
  • LDom 1: 48
  • LDom 2: 24

  • LDom 3: 24

  • LDom 1: 4
  • LDom 2: 4

  • LDom 3: 4

  • LDom 1: 44
  • LDom 2: 20

  • LDom 3: 20

B4-4
  • LDom 1: 24
  • LDom 2: 24

  • LDom 3: 24

  • LDom 4: 24

  • LDom 1: 4
  • LDom 2: 4

  • LDom 3: 4

  • LDom 4: 4

  • LDom 1: 20
  • LDom 2: 20

  • LDom 3: 20

  • LDom 4: 20

Table 36 Cores Available for Base Configuration PDomains (Half-Populated DCU Configurations)

LDom Configuration
Total Number of Cores Available for Domains in This Configuration
Number of Cores Set Aside for Global Zone
Number of Cores Available for Nonglobal Zones
B2-1
LDom 1: 48
LDom 1: 4
LDom 1: 44
B2-2
  • LDom 1: 24
  • LDom 2: 24

  • LDom 1: 4
  • LDom 2: 4

  • LDom 1: 20
  • LDom 2: 20

B2-3
  • LDom 1: 24
  • LDom 2: 12

  • LDom 3: 12

  • LDom 1: 4
  • LDom 2: 2

  • LDom 3: 2

  • LDom 1: 20
  • LDom 2: 10

  • LDom 3: 10

B2-4
  • LDom 1: 12
  • LDom 2: 12

  • LDom 3: 12

  • LDom 4: 12

  • LDom 1: 2
  • LDom 2: 2

  • LDom 3: 2

  • LDom 4: 2

  • LDom 1: 10
  • LDom 2: 10

  • LDom 3: 10

  • LDom 4: 10

When using the information in the tables, keep in mind that the number of cores that are set aside for the global zone applies only when you are creating nonglobal zones on that Database Domain. In that case, a certain number of cores are reserved for the Database Domain (the global zone) and the remaining cores are available for the zones on that Database Domain (the nonglobal zones). If you have a Database Domain with no zones, then all the cores are available for that Database Domain.

For each zone that you create, use a minimum of one core per zone. However, depending on the workload that you expect on a zone, a larger number of cores per zone might be preferable, thereby reducing the total number of zones in that domain. Carefully consider the expected workload on each zone that you create, so that you allot the appropriate number of cores to those zones.