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 Storage Server Disk Group Layout
Planning the Exadata Storage Server Disk Group Layout
Understanding an Example Scenario
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
Following are a list of guidelines regarding zones and clusters on the Database Domains:
When you first install the operating system instances on a domain, that domain is automatically designated as the global zone. Any domains or zones that you create from that point forward are nonglobal zones.
Global zones and nonglobal zones cannot run RAC clusterware in the same domain. When a Database Domain is created and an operating system is installed on the Database Domain, that domain is considered a global zone. The following scenarios describe what is and is not acceptable in that situation:
If you have two Database Domains (global zones) and those Database Domains are members of a cluster, you cannot create zones on those Database Domains and have those zones as members of their own clusters. Because those zones would be considered non-global zones, you cannot have those non-global zones running RAC clusterware within Database Domains that are also running RAC clusterware.
If you have two Database Domains (global zones) but those Database Domains are not members of a cluster, then you can create zones on those Database Domains and have those zones as members of their own clusters.
You can create clusters with zones of different sizes. However, each zone that is a member of a cluster should be the same size with regards to the number of cores being used by each zone in the cluster. For example, if you are creating a two-node cluster and the first zone in that cluster uses four cores, the other zone in that cluster should also use four cores.
You can cluster zones together across multiple Database Domains that are of different sizes. For example, you can create a four-node cluster, where there is one zone on each Database Domain on the four SPARC T4-4 servers, and those zones are clustered together, even if two of the Database Domains take up 25% of the servers and the other two Database Domains take up 50% of the servers. The private interface connections (the IB connections) are limited to the lower number from the smaller domain, based on the IB HCAs available to the zone.
When creating zones on a Database Domain, if the last zone that you are creating on that domain uses the last remaining core available in that domain, then that zone will be configured with no CPU resource controls. For example, if you are creating zones on a server with four total domains, so that you could have a maximum of six single-core zones on each domain, the sixth and final zone in the domain would be configured with no CPU resource controls. This zone would share the core and vCPUs with the global zone in this case.
To minimize remote memory accesses, you should allocate physical memory to each of the zones in multiples of 16 GB to align with the size of the memory banks on the server.
While it is possible to create a cluster where all the zones are in the same Database Domain or are on the same SPARC 4-4 server, that configuration is not recommended because it is not a highly-available configuration. It is advisable to create clusters where the zones are on separate Database Domains, and the cluster spans across several SPARC T4-4 servers, so that there is not a single point of failure.