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
Planning the Storage Server Disk Group Layout
Understanding an Example Scenario
Determine the Available Existing Storage Capacity (Example Scenario)
Determine the Amount of Space for Each Disk Group in Each Cluster (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
An Oracle representative should have set up a cluster on the Database Domains as part of their installation and configuration process. However, when you set up zones on the Database Domains and you set up new clusters with those zones as members, if you want to create clusters that will share the storage servers, the storage servers must be repartitioned. That action erases the clusters that were set up at your initial installation.
Consider these items when planning the storage server disk group layout. For example, how many clusters are you setting up? How many storage servers are available? What level of redundancy do you want for the storage servers for these clusters?
If three storage servers are available for every cluster with zones on the Database Domains, and you are using normal redundancy, then you do not have to share storage servers across each cluster, and the storage servers do not have to be repartitioned. For high redundancy, five storage servers should be available for every cluster with zones on the Database Domains.
For example, assume you are creating one cluster with zones on the Database Domains and you are using normal redundancy, then you would not have to share storage servers because the storage rack that is part of your Oracle SuperCluster M6-32 has nine storage servers.
Likewise, assume that you have an Oracle Exadata Storage Expansion Full Rack (expansion rack) connected to your Oracle SuperCluster M6-32 (with 18 storage servers). If you are creating eight clusters with zones on the Database Domains and you are using normal redundancy, then you would have 27 storage servers altogether, which means you would have more than three storage servers for every cluster that you are creating. You would not have to share storage servers across the clusters.
If fewer than three storage servers are available for every cluster with zones on the Database Domains using normal redundancy, or fewer than five storage servers for every cluster if you are using high redundancy, then you must share storage servers across each cluster.
The following topics provide more detail on the process for planning the storage server layout, and an example scenario that describes how certain decisions are made based on an example situations and values.