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

Delete VNETs

Follow these procedures if you need to delete any VNETs that you added using the addvnet-wrapper.sh script, and you created VNETs accidentally that are not needed.


Note - Do not delete VNETs that are used by zones. Doing so results in a failed zone.


  1. Locate the rmvnet.sh script.

    See Preparing to Configure Zones on Database Domains for the location of the rmvnet.sh script.

  2. Identify the VNETs that you want to remove.
    ldm ls -l -p DB-domain | grep '^VNET'

    where DB-domain is the name of the Database Domain that you added the VNETs to.

    For example, if the name of the Database Domain that you added the VNETs to is osc01dbadmin02-01, you would type the following:

    ldm ls -l -p osc01dbadmin02-01 | grep '^VNET'
    VNET|name=mgnet0|dev=network@0|service=mng-primary-net1@primary|mac-addr=00:14:4f:fa:f8:e8|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=0
    VNET|name=mgnet1|dev=network@1|service=mng-primary-net00@primary|mac-addr=00:14:4f:fb:a0:cd|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=1
    VNET|name=z0mgnet0|dev=network@2|service=mng-primary-net1@primary|mac-addr=00:14:4f:fb:da:06|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=2
    VNET|name=z0mgnet1|dev=network@3|service=mng-primary-net1@primary|mac-addr=00:14:4f:f8:a8:06|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=3
    VNET|name=z1mgnet0|dev=network@4|service=mng-primary-net1@primary|mac-addr=00:14:4f:fb:83:cc|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=4
    VNET|name=z1mgnet1|dev=network@5|service=mng-primary-net1@primary|mac-addr=00:14:4f:fb:26:ab|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=5
  3. Remove the VNETs.
    • If you want to remove specific VNETs, type.
      rmvnet.sh -n vnet-name DB-domain

      where:

      • vnet-name is the name of the VNET that you want to remove. If you want to remove more than one VNET, type the name of each VNET that you want to remove, separated by commas.

      • DB-domain is the name of the Database Domain from which you are removing the VNETs.

      For example, assume you have the following setup:

      • The names of the VNETs that you want to remove are z1mgnet0 and z1mgnet1.

      • The name of the Database Domain that you are removing the VNETs from is osc01dbadmin02-01.

      Then you would type the following:

      rmvnet.sh -n z1mgnet0,z1mgnet1 osc01dbadmin02-01
    • If you want to remove several VNETs that have common characteristics, type.
      rmvnet.sh -p 'beginning-term+' DB-domain

      where:

      • beginning-term is the term at the beginning of the VNET names for the VNETs that you want to remove (for example, all VNETs with names that begin with z1).

      • domain-name is the name of the Database Domain from which you are removing the VNETs.

      For example, assume you have the following setup:

      • You want to remove all VNETs with names that begin with z1 (in the output from Step 2, that would be z1mgnet0 and z1mgnet1).

      • The name of the Database Domain that you are removing the VNETs from is osc01dbadmin02-01.

      Then you would type the following:

      rmvnet.sh -p 'z1+' osc01dbadmin02-01
  4. Verify that the VNETs have been removed.
    ldm ls -l -p DB-domain | grep '^VNET'

    where DB-domain is the name of the Database Domain that you removed the VNETs from.

    For example, if the name of the Database Domain that you removed the VNETs from is osc01dbadmin02-01, type the following:

    ldm ls -l -p osc01dbadmin02-01 | grep ‘^VNET'
    VNET|name=mgnet0|dev=network@0|service=mng-primary-net1@primary|mac-addr=00:14:4f:fa:f8:e8|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=0
    VNET|name=mgnet1|dev=network@1|service=mng-primary-net00@primary|mac-addr=00:14:4f:fb:a0:cd|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=1
    VNET|name=z0mgnet0|dev=network@2|service=mng-primary-net1@primary|mac-addr=00:14:4f:fb:da:06|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=2
    VNET|name=z0mgnet1|dev=network@3|service=mng-primary-net1@primary|mac-addr=00:14:4f:f8:a8:06|mode=|pvid=1|vid=|mtu=1500|linkprop=|id=3

    The VNETs that you removed should not appear in the list.