| Skip Navigation Links | |
| Exit Print View | |
|
SPARC SuperCluster T4-4 Zones With Oracle Database on Database Domains Configuration Guide |
| Skip Navigation Links | |
| Exit Print View | |
|
|
SPARC SuperCluster T4-4 Zones With Oracle Database on Database Domains Configuration Guide |
Planning to Set Up Zones on Database Domains
Understanding Domain Configurations
Determining the Cores Available for Domains 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 Exadata Storage Server Disk Group Layout
Determine the Available Existing Storage Capacity
Determine the Number of Clusters in the System and Maximum Amount of Space Available to Each Cluster
Determine the Amount of Space for Each Disk Group in Each Cluster
Understanding an Example Scenario
Determine the Available Existing Storage Capacity
Determine the Number of Clusters in the System and Maximum Amount of Space Available to Each Cluster
Determine the Amount of Space for Each Disk Group in Each Cluster
Recording Your Existing and Planned Configuration Information
Recording Your Existing Configuration
Recording Your Zone Configuration Information
Recording Your Cluster Configuration Information
Recording Your Exadata Storage Server Disk Group Layout
Understanding Network Considerations
Understanding the Networking Setup Before Zone Creation
Host Management Network Before Zone Creation
Client Access Network Before Zone Creation
InfiniBand Network Before Zone Creation
Understanding the Networking Setup After Zone Creation
Host Management Network After Zone Creation
Client Access Network After Zone Creation
InfiniBand Network After Zone Creation
Understanding the Network Setup for Clusters
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 Using OEDA
Verify Exadata Storage Server Disk Space for Additional Zones
Creating Configuration Files Using OEDA: Manual Procedures
Oracle Exadata Deployment Assistant Overview
Complete the Customer Details Page
Complete the Hardware Selection Page
Complete the Define Customer Networks Page
Complete the Administration Network Page
Complete the Client Ethernet Network Page
Complete the Identify Compute Node OS and Enable Capacity-on-Demand Configuration 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 Configuration Files Using OEDA: Automated Procedures
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 (CPU-to-Database Domain Mapping)
Determine if Additional VNETs Are Needed (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 Database Domain clusters 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 Exadata Storage Servers, the Exadata Storage Servers will have to be repartitioned. That action erases the clusters that were set up at your initial installation.
Consider these items when planning the Exadata Storage Server disk group layout. For example, how many clusters are you setting up? How many Exadata Storage Servers are available? What level of redundancy do you want for the Exadata Storage Servers for these clusters?
If you have three Exadata Storage Servers available for every cluster with zones on the Database Domains, and you are using normal redundancy, then you do not have to share Exadata Storage Servers across each cluster, and you do not have to manually partition the Exadata Storage Servers. For high redundancy, you should have five Exadata Storage Servers available for every cluster with zones on the Database Domains.
For example, if you have a SPARC SuperCluster T4-4 Half Rack, which has three Exadata Storage Servers, and you are creating one cluster with zones on the Database Domains and you are using normal redundancy, then you would not have to share Exadata Storage Servers.
Likewise, if you have a SPARC SuperCluster T4-4 Full Rack (with six Exadata Storage Servers) and an Oracle Exadata Storage Expansion Full Rack connected to your SPARC SuperCluster T4-4 (with 18 Exadata Storage Servers), and you are creating eight clusters with zones on the Database Domains and you are using normal redundancy, then you would have three Exadata Storage Servers for every cluster that you are creating, and you would not have to share Exadata Storage Servers across the clusters.
If fewer than three Exadata Storage Servers are available for every cluster with zones on the Database Domains using normal redundancy, or fewer than five Exadata Storage Servers for every cluster if you are using high redundancy, then you must share Exadata Storage Servers across each cluster.
The following topics provide more detail on the process for planning the Exadata Storage Server layout, and an example scenario that describes how certain decisions are made based on an example situations and values.
|