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

Example Configuration

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:

For the purposes of this exercise, assume the following:

Using the information provided in the following sections:

You can determine the following information about the two Database Domains on each PDomain:

The following sections describe how cores could be allocated in both of these Database Domains:

LDom 1 (First Database Domain)

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.

LDom 4 (Second Database Domain)

This Database Domain will contain four zones, which means that:

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).