JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle SuperCluster M6-32 Zones With Oracle Database on Database Domains

Configuration Guide

search filter icon
search icon

Document Information

Using This Documentation

Product Notes

Related Documentation

Feedback

Access to Oracle Support

Planning to Set Up Zones on Database Domains

Important Cautions

Naming Conventions

Understanding PDomains

PDomains Overview

PDomain Guidelines

Extended Configuration PDomain Overview

Understanding Extended Configuration PDomains

Base Configuration Overview

Understanding Base Configuration PDomains

Understanding LDoms

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

Example Configuration

Memory Available for LDoms

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

Prepare to Configure Zones

Update the Base Software

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)

Example Configuration

Verify Storage Server Disk Space for Additional Zones

Locate the Necessary Files to Set Up Zones

Set Up the OEDA

Start the OEDA

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 Page

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

Creating VNETs

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)

Locate the Control Domain

Create VNETs for Zones

Delete VNETs

Running the Java OneCommand

Set Up Public Key Authentication for ZFS Storage Controllers

Set Up the Java OneCommand

Run the Java OneCommand

NTP Issue

Creating Additional Links on the IB Storage Network for Zones

Create Additional Links on the IB Storage Network for Zones

Setting Up VLAN Tagging for Zones

Set Up VLAN Tagging for Zones

Index

Locate the Necessary Files to Set Up Zones

  1. Locate the folder that contains the most recent configuration files.
    • If this is the first time after the initial installation of your system that you are creating additional zones on Database Domains with zones, locate the folder that contains the configuration files that your Oracle installer saved at the time of the initial installation of your system.

    • If you have used these instructions previously to create additional zones on Database Domains with zones, locate the folder that contains the most recent configuration files from that previous configuration.

    The configuration files are typically in a folder named ExadataConfigurations.

  2. Locate the necessary files within the folder that contains the most recent configuration files.

    The folder should contain the following files:

    • Individual configuration files for every zone that was set up on Database Domains with zones (shown as name-prefix-zone-name-zoneConfig.xml)

    • Individual configuration files for every cluster that was set up, either for zones or for Database Domains without zones (shown as customer-name-name-prefix-cluster-clucluster-number.xml)

    • A single master file that contains the configuration information for all the zones, Database Domains, and clusters that were set up on your system (shown as customer-name-name-prefix.xml)

    For example, assume you had zones and clusters created during your initial installation as described in Example Configuration, and you provided the following information during your initial installation:

    • Customer name: Acme

    • Name prefix: osc01

    Then you should see configuration files similar to the following in the configuration folder:

    • Individual configuration files for the eight zones that were set up on Database Domains with zones:

      • osc01zdbadm01-zoneConfig.xml: Configuration file for the first zone

      • osc01zdbadm02-zoneConfig.xml: Configuration file for the second zone

      • osc01zdbadm03-zoneConfig.xml: Configuration file for the third zone

      And so on for the configuration files for the remaining five zones.

    • Individual configuration files for the five clusters that were set up:

      • Acme-osc01-cluster-clu1.xml: Configuration file for the first cluster (the first cluster with zones)

      • Acme-osc01-cluster-clu2.xml: Configuration file for the second cluster (the second cluster with zones)

      • Acme-osc01-cluster-clu3.xml: Configuration file for the third cluster (the third cluster with zones)

      • Acme-osc01-cluster-clu4.xml: Configuration file for the fourth cluster (the fourth cluster with zones)

      • Acme-osc01-cluster-clu5.xml: Configuration file for the fifth cluster (the cluster for the Database Domains without zones)

    • A single master configuration file that contains all the configuration information for your system:

      • Acme-osc01.xml

    You will be using one of these configuration files when you use OEDA or Java OneCommand to set up zones on the Database Domains.