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
Oracle Exadata Deployment Assistant Overview
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
Before You Begin
Caution - Ensure that you backup all existing databases before running the Java OneCommand. |
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 - 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. |
The configuration files for the new clusters that you created should be named customer-name-name-prefix-cluster-clucluster-number.xml. For example:
Acme-ssc01-cluster-clu3.xml
Acme-ssc01-cluster-clu4.xml
./install.sh -cf /path-to-config-file/customer-name.name-prefix.xml -l
For example:
./install.sh -cf /path-to-config-file/Acme-ssc01-cluster-clu3.xml -l
Information similar to the following is displayed:
1. Validate Configuration File 2. Setup Required Files 3. Create Users 4. Setup Cell Connectivity 5. Verify IB and Calibrate Cells 6. Create Cell Disks 7. Create Grid Disks 8. Install Cluster Software 9. Initialize Cluster Software 10. Install Database Software 11. Relink Database with RDS 12. Create ASM Diskgroups 13. Create Databases 14. Apply Security Fixes 15. Create Installation Summary 16. 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.
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 IB and calibrate cells (step 5 in the example output above)
Create cell disks (step 6 in the example output above)
Configure cell alerting (not shown in the example output above)
./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-ssc01-cluster-clu3.xml -s 1
Run all of the steps in the Java OneCommand except for the following:
Verify IB 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-ssc01-cluster-clu3.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.
Go to Creating Additional Links on the IB Storage Network for Zones.