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
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
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
The Oracle Exadata Deployment Assistant is normally used when the system is initially installed and configured, and its purpose is to gather networking information for the Database Domains and for the physical components in the SPARC SuperCluster T4-4, such as the SPARC T4-4 servers, Exadata Storage Servers, switches and PDUs. However, in this section, you will be using the Oracle Exadata Deployment Assistant to gather networking information for the clusters and single-instance database zones that you want to set up.
Because you will be using the Oracle Exadata Deployment Assistant to gather networking information for clusters and single-instance database zones, rather than for physical components as the tool was originally intended for, it's useful to keep these things in mind as you perform the procedures in this section:
The Database Machine Prefix would normally refer to the name of the SPARC SuperCluster T4-4 as a whole, and would be used as a prefix for the hostnames for the components inside the SPARC SuperCluster T4-4. However, for the procedures in this section, the Database Machine Prefix refers to the name for the cluster that you will be setting up, and will be used as a prefix for the zones that are a part of that cluster.
The Oracle Database Deployment Assistant would normally assign hostnames to the compute nodes (the SPARC T4-4 servers) in several areas, such as the Administration Network. However, in some areas in this section, information that is being entered for compute nodes will actually apply to the zones that are part of this particular cluster, not to the compute nodes themselves. The instructions in this section will point out when information that needs to be entered for compute nodes actually applies to zones rather than compute nodes.
In other areas in this process, information that is being entered for a compute node actually does apply to the compute node and not to a zone in the cluster, such as the ILOM host name and IP address for the compute node. The instructions in this section will point out when information that needs to be entered for compute nodes actually does apply for the compute nodes, and not for zones in this cluster.
When the Oracle Database Deployment Assistant is first run on your SPARC SuperCluster T4-4 during the initial installation and configuration, part of the process would include assigning host names and IP addresses to the switches and PDUs. Because you are using this same tool in this situation to gather networking information to be used for the clusters and single-instance database zones, certain screens will have networking information for the switches and PDUs that will be based on the information you are entering for this particular cluster, and would therefore be different from the information that was originally entered for those components when your system was first set up. The networking information for the switches and PDUs are not cluster-dependant, so you will be asked to manually change the networking information for those components back to their original values several times in these procedures.