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

Determine the Available Existing Storage Capacity (Example Scenario)

Determine the Number of Clusters in the System and Maximum Amount of Space Available to Each Cluster (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

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

Planning the Storage Server Disk Group Layout

In general, follow this process to determine how to lay out your zones and clusters across the storage servers, where each decision point at the top of the process affects decisions made lower in the decision tree.

  1. Determine the amount of existing usable disk space. How many storage servers are available for the clusters that you are creating? How much total usable disk space is available for those clusters?

    For more information, see Determine the Available Existing Storage Capacity.

  2. Determine the number of clusters that you want for the zones that you are creating on the Database Domains. This, in conjunction with the total amount of existing usable disk space, is used to determine the maximum amount of space that will be available for each cluster.

    For more information, see Determine the Number of Clusters in the System and Maximum Amount of Space Available to Each Cluster.

  3. Determine the amount of space to assign to each of the three disk groups in each cluster.

    • DATA

    • RECO

    • DBFS


    Note - There is an option to designate the DBFS disk group set as UNUSED, if necessary.


    Also determine the names to use for the disk groups for each cluster. For example, if you are creating disk groups for two clusters (osc01r1 and osc01r2), then you might use these names for the three disk groups for each cluster:

    • First cluster (osc01r1):

      - DATA_osc01r1

      - RECO_osc01r1

      - DBFS_osc01r1

    • Second cluster (osc01r2):

      - DATA_osc01r2

      - RECO_osc01r2

      - DBFS_osc01r2

Record your storage server disk group layout in the worksheet in Recording Your Storage Server Disk Group Layout.

For more information, see Determine the Amount of Space for Each Disk Group in Each Cluster.

Determine the Available Existing Storage Capacity

You must first determine how much existing storage capacity is available before deciding how to carve that storage up for the disk groups for each cluster that you create.

Every storage server contains 12 drives, with the following capacities:

In addition, the total number of storage servers varies, depending on the type of Exadata Storage Expansion Rack that you have:

Finally, the total capacity that you have available depends on the level of redundancy that you want to set for the ASM disk groups (normal redundancy or high redundancy).

The following tables provide capacity information for the Oracle SuperCluster M6-32 storage rack and the expansion rack.

Table 37 Storage Server Storage Capacity in the Oracle SuperCluster M6-32 Storage Rack

Capacity Type
4 TB High-Capacity Disks
1.2 TB High-Performance Disks
Raw disk capacity
432 TB
129 TB
Usable mirrored capacity (ASM normal redundancy)
192 TB
58 TB
Usable triple mirrored capacity (ASM high redundancy)
129 TB
39 TB
Raw flash capacity
28.8 TB
28.8 TB

Table 38 Storage Server Storage Capacity in the Expansion Rack

Capacity Type
4 TB High-Capacity Disks
1.2 TB High-Performance Disks
Raw disk capacity
  • Quarter Rack: 192 TB
  • Half Rack: 432 TB

  • Full Rack: 864 TB

  • Quarter Rack: 57 TB
  • Half Rack: 129 TB

  • Full Rack: 258 TB

Usable mirrored capacity (ASM normal redundancy)
  • Quarter Rack: 85.3 TB
  • Half Rack: 192 TB

  • Full Rack: 384 TB

  • Quarter Rack: 26 TB
  • Half Rack: 58 TB

  • Full Rack: 116 TB

Usable triple mirrored capacity (ASM high redundancy)
  • Quarter Rack: 57.3 TB
  • Half Rack: 129 TB

  • Full Rack: 258 TB

  • Quarter Rack: 16 TB
  • Half Rack: 39 TB

  • Full Rack: 78 TB

Raw flash capacity
  • Quarter Rack: 12.8 TB
  • Half Rack: 28.8 TB

  • Full Rack: 57.6 TB

  • Quarter Rack: 12.8 TB
  • Half Rack: 28.8 TB

  • Full Rack: 57.6 TB

Determine the Number of Clusters in the System and Maximum Amount of Space Available to Each Cluster

The number of clusters in your system varies, depending on several factors, such as:

See Zones and Cluster Planning for Database Domains for more information on how to decide on the total number of zones and clusters in your system.

Once you determine the number of clusters in your system, you can now determine the maximum amount of space that you can assign to each cluster based on the total amount of usable storage that is available. The total amount of space that you assign to all the clusters in the system cannot exceed the total amount of storage that is available.

For example, assume you have a total amount of 48 TB available as usable storage, and you want to create four clusters total in your system, where each cluster has the same overall size. Then the maximum amount of usable space for each cluster would be 12 TB apiece.

Determine the Amount of Space for Each Disk Group in Each Cluster

Once you have decided on the total amount of disk space to use for each cluster, you must break that total disk space for each cluster down into disk space that is used for the three disk groups within each cluster:

The DBFS disk group is normally assigned a substantially smaller amount of total disk space than the other two disk groups. You can also designate the DBFS disk group as UNUSED, if necessary.

For example, if 12 TB of space is available for each cluster, you must carve that 12 TB of space up so that the combined disk space used by all three disk groups is 12 TB or less.