| Skip Navigation Links | |
| Exit Print View | |
|
Oracle SuperCluster M6-32 Zones With Oracle Database on Database Domains Configuration Guide |
| 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 Four DCUs in One Compute Server (R1 Extended Configuration PDomains)
Four Fully-Populated DCUs (R1_1 PDomain Configuration)
Two Fully-Populated DCUs and Two Half-Populated DCUs (R1_2 PDomain Configuration)
Four Half-Populated DCUs (R1_3 PDomain Configuration)
Understanding Four DCUs Across Two Compute Servers (R2 Extended Configuration PDomains)
Four Fully-Populated DCUs (R2_1 PDomain Configuration)
Two Fully-Populated DCUs and Two Half-Populated DCUs (R2_2 PDomain Configuration)
Four Half-Populated DCUs (R2_3 PDomain Configuration)
Understanding Base Configuration PDomains
Understanding Four DCUs on One Compute Server (R3 Base Configuration PDomains)
Four Fully-Populated DCUs (R3_1 PDomain Configuration)
Two Fully-Populated DCUs and Two Half-Populated DCUs (R3_2 PDomain Configuration)
Four Half-Populated DCUs (R3_3 PDomain Configuration)
Understanding Four DCUs Across Two Compute Servers (R4 Base Configuration PDomains)
Four Fully-Populated DCUs (R4_1 PDomain Configuration)
Two Fully-Populated DCUs and Two Half-Populated DCUs (R4_2 PDomain Configuration)
Four Half-Populated DCUs (R4_3 PDomain Configuration)
Two Fully-Populated DCUs and Two Half-Populated DCUs (R4_4 PDomain Configuration)
Understanding Two DCUs on One Compute Server (R5 Base Configuration PDomains)
Two Fully-Populated DCUs (R5_1 PDomain Configuration)
Understanding Two DCUs Across Two Compute Servers (R6 Base Configuration PDomains)
Two Fully-Populated DCUs (R6_1 PDomain Configuration)
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
Each PDomain has its own set of fans and I/O boards, and operates as an independent server that has full hardware isolation from other PDomains in the chassis. A hardware or software failure on one PDomain does not affect the other PDomains in the chassis. There are two redundant SPs (SP0 and SP1) in the chassis. One of the SPs functions as the Active-SP and actively manages the chassis, while the other acts as the Standby-SP that assumes the Active-SP role in the event of a failure. You can use the Oracle ILOM software that is preinstalled on each SP to remotely monitor and control PDomains.
There are two types of PDomains:
|
Each server can contain either two or four PDomains, in the following configurations:
All PDomains in a single server, with the two or four PDomains all contained within the single server.
PDomains split across two servers, with one of these situations:
Two PDomains are split across the two servers (one PDomain on each server)
Four PDomains are split across the two servers (two PDomains on each server)
|