| 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 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
The following configuration is used as an example throughout this exercise:
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
Five cluster instances are set up on the R1_1 PDomain configuration:
One cluster instance for the two Database Domains (without zones)
One cluster instance for each zone on the Database Domain with zones (four cluster instances total for the zones)
The storage rack has storage servers with 1.2 TB high performance disks
For each cluster, the example configuration assumes that you have zones within the Database Domain with zones, or Database Domains (without zones), that reside on different PDomains. So for the zones on Database Domains with zones, these zones are members of the first cluster:
First zone in the Database Domain with zones in the first PDomain (DCU 0 and DCU 1)
First zone in the Database Domain with zones in the second PDomain (DCU 2 and DCU 3)
Throughout these procedures, it is assumed that this configuration was created during your initial installation, and that you are adding zones to the existing Database Domains with zones.
|