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

Run the Java OneCommand

Before You Begin


Caution

Caution - Ensure that you backup all existing databases before running the Java OneCommand.



Caution

Caution - You must use the latest version of OEDA and the Java OneCommand patch (patch 19766190 or later). Refer to the Oracle Exadata Deployment Assistant (OEDA) section in MOS Note 888828.1 for details.



Caution

Caution - Any version of Java OneCommand prior to patch 19766190 can destroy the storage cell disks and griddisk if an undo option is performed on certain steps (Create Cell disk, for example). This can cause complete destruction of all the griddisks on the storage cells. In addition, re-running the griddisk creation step or mistakenly specifying a non-unique diskgroup in OEDA will result in the destruction of existing griddisks. Be aware that older versions of Java OneCommand also destroy cell disks and griddisks with the Create Cell Disks step.


  1. Locate the configuration file that was generated at the end of the OEDA process when you added zones to the Database Domains.

    The configuration file should be named customer-name.name-prefix.xml, such as Acme.osc01.xml.

  2. Display the list of functions to be performed by the Java OneCommand.
    ./install.sh -cf customer-name.name-prefix.xml -l

    For example:

    ./install.sh -cf Acme.osc01.xml -l

    Information similar to the following is displayed:

    1. Validate Configuration File
    2. Create Virtual Machine
    3. Setup Required Files
    4. Create Users
    5. Setup Cell Connectivity
    6. Verify Infiniband and Calibrate Cells
    7. Create Cell Disks
    8. Create Grid Disks
    9. Install Cluster Software
    10. Initialize Cluster Software
    11. Install Database Software
    12. Relink Database with RDS
    13. Create ASM Diskgroups
    14. Create Databases
    15. Apply Security Fixes
    16. Create Installation Summary
    17. Resecure Machine

    The output that you see and the number assigned to each step in the output varies depending on the configuration choices you made in OEDA.

  3. Note the specific steps that you will not run in Java OneCommand.

    In the next step, you will run the appropriate steps in Java OneCommand. Do not run any of the following steps in Java OneCommand in the next step:

    • Verify InfiniBand and calibrate cells (step 6 in the example output above)

    • Create cell disks (step 7 in the example output above)

    • Configure cell alerting (not shown in the example output above)

  4. Run the appopriate steps in the Java OneCommand, using the configuration file that was generated at the end of the OEDA process as input.
    ./install.sh -cf customer-name.name-prefix.xml -s step-number

    where step-number is the number of each step that you are running, in order. For example:

    ./install.sh -cf Acme.osc01.xml -s 1

    Run all of the steps in the Java OneCommand except for the following:

    • Verify InfiniBand and calibrate cells

    • Create cell disks

    • Configure cell alerting

    You can also run a series of steps by using the -r option. For example, if you wanted to run steps 1 through 5, enter the following:

    ./install.sh -cf Acme.osc01.xml -r 1-5

    You can destroy a zone from a Database Domain using the instructions in Delete a Template Zone From a Database Domain if necessary (for example, if Java OneCommand fails at step 2 for some reason). However, use caution when destroying zones from a Database Domain.

  5. Create additional links on the IB storage network for the zones that you set up on the Database Domains.

    Go to Creating Additional Links on the IB Storage Network for Zones.