1

<Insert Picture Here>

One Command InstallHow to Install the Grid in ~30 minutes

Philip NewlanConsulting Member Technical Staff RAC Pack

Vitor Pacheco MoreiraManager DB ServicesAmadeus

3

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

4

Agenda

• The Goal

• Install Methods & Challenges

• Rapid install tools

• Customer Perspective

• Benefits

5

The GoalSilent, repeatable install

• Install– Validate : Hardware, Configure: Operating System– Oracle Grid Infrastructure– Oracle Real Application Clusters

• Grid Infrastructure – Clusterware – ASM and Diskgroup(s)– Patching: Patchset, Bundle Patch, One Off – SCAN/VIP listeners

• RAC Home– Patching: Patchset, Bundle Patch, One Off

• Database(s)

6

Installation Methods

• Oracle Universal Installer (OUI, runInstaller)– GUI based– Silent with response file– Allows for software only (no configuration)

• Cloning (clone.pl)– Uses OUI in silent mode under the covers

• OEM Provisioning Pack

7

The Challenges

• Ensuring all nodes meet minimum requirements– OS packages, kernel parameters, etc.– Users, groups, devices, directories, etc.

• Requirement to run some commands as root OS user

• Silent Install– Separate Configuration from Build

8

OneCommand

• What is it ?– A solution to the automated – silent install request

• Where can I use it ?– Linux– porting to other Unix platforms• Solaris• AIX• HP-UX

9

OneCommandDemonstration - Start

10

Sweet spot

• What is the target market for OneCommand– Customers that need to ‘repeat build’ RAC Clusters– Have a cookie cutter approach to deployment– Build more than 1 cluster

• If all you need to build….– … is 1 cluster

• Then maybe OneCommand is not for you

11

One Command

• Two major phases when building the cluster database

ConfigureConfigure

BuildBuildonecommand.params

12

One CommandConfiguration Phase

• Key to correctly building a cluster using OneCommand

• Create a file with name/value pairs that describes the cluster

• The key to repeatable builds

13

One CommandConfiguration File

#######################

# CLUSTER DETAILS

#######################

CLUSTER_PREFIX=strrac

#######################

# NODE DETAILS

#######################

# An associated array of node names, node ip's etc.

NODE_NAMES=(strrac15 strrac16 )

NODE_IPS=(144.25.246.92 144.25.246.93)

VIP_NAMES=(strrac15-vip strrac16-vip)

VIP_IPS=(144.25.246.115 144.25.246.116)

PRIV_NAMES=(strrac15-priv strrac16-priv)

PRIV_IPS=(10.10.10.15 10.10.10.16)

DNS_SERVERS=(130.35.249.41)

NTP_SERVERS=(152.68.120.1 139.185.249.114 10.204.32.1)

.

.

#######################

# CLUSTER DETAILS

#######################

CLUSTER_PREFIX=strrac

#######################

# NODE DETAILS

#######################

# An associated array of node names, node ip's etc.

NODE_NAMES=(strrac15 strrac16 )

NODE_IPS=(144.25.246.92 144.25.246.93)

VIP_NAMES=(strrac15-vip strrac16-vip)

VIP_IPS=(144.25.246.115 144.25.246.116)

PRIV_NAMES=(strrac15-priv strrac16-priv)

PRIV_IPS=(10.10.10.15 10.10.10.16)

DNS_SERVERS=(130.35.249.41)

NTP_SERVERS=(152.68.120.1 139.185.249.114 10.204.32.1)

.

.View demo

14

One CommandBuild Phase

• Use OneCommand to read the configuration File

• Steps 0 – 13– 0 is Validate Environment– .– .– 13 is DbcaDB – Build the RAC Database

# ./OneComand.sh -i –r 0-13# ./OneComand.sh -i –r 0-13

15

One CommandBuild Phase – Individual Steps

• ValidateEnv – Validate configuration file• UnzipFiles - Unzip Oracle software• WriteNodelists - Create list of nodes• UpdateEtcHosts - Update /etc/hosts for node connectivity• SetupNTP - Configure NTP correctly• CreateUsers - Create required users• SetupStorage - Setup udev, and permissions for storage• SetupSSHusers - Setup ssh for required users• GridSwInstall - Install Grid Infrastructure on all nodes• GridRootScripts - Run root scripts for Grid Infrastructure• DbSwInstall - Install database software on all homes and

nodes• CreateASMDiskgroups - Create ASM instance• CreateListener - Create ASM Listener• DbcaDB - Create all databases based on best practices

16

One CommandBuild Phase Methodology

• Uses standard Oracle tools– OUI, CVU, OPatch

• Becomes root for administrative tasks:– Create users– Update /etc/hosts– Setup udev– Configure ntpd.conf– Run root.sh for install and configuration

17

One Command

• Build Phase

BuildBuildonecommand.params

grid_infrastructure.zip

rdbms_software_1.zip

rdbms_software_2.zip

18

OneCommandTracking Installation status

• Log file for every step is written– including comprehensive timing

• Each command is logged to a separate file– Allows detailed examination of the install process

View demo

19

Real-world ExamplesWhere do we use One Command ?

• General case RAC– Uses silent Install

• Install and Configuration of Database Machine– Automatically install/configures RAC on DB Machine– Uses silent install

• Oracle RAC in Oracle VM templates– Automatically deploys Grid Infrastructure and Oracle RAC

within VM templates– Uses cloning technology

20

Database Machine – The BasicsOne Command – Used to build every Database Machine

• 8 Compute Nodes• 14 Storage Nodes [Cells]• One or more – Clusters– Databases– Diskgroups

• End to End Provisioning for the complete Database Machine

21

Database MachineConfiguration Phase

• OS/Hardware Setup – First Boot– IP addresses, dns,ntp,/etc/hosts,users,ssh– Validation

• Storage Setup– Cell disks– Grid disks

• Oracle Software Setup– Grid Infrastructure– Database(s)

22

Step 1 CreateWorkDir -took 0 minutes 0 seconds

Step 2 setupSSHroot -took 2.20 minutes 132 seconds

Step 3 etchostupd -took 3.51 minutes 211 seconds

Step 4 CreateCellipnitora -took .15 minutes 9 seconds

Step 5 OraSetup -took .30 minutes 18 seconds

Step 6 SetupSSHora -took 1.06 minutes 64 seconds

Step 7 ValidateCell -took .33 minutes 20 seconds

Step 8 CreateGridDisks -took 3.80 minutes 228 seconds

Step 9 GridSwInstall -took 9.10 minutes 546 seconds

Step 10 GiRootScripts -took 11.43 minutes 686 seconds

Step 11 112DBSwInstall -took 7.30 minutes 438 seconds

Step 12 RunAsmCa -took 1.86 minutes 112 seconds

Step 13 112CreateListener -took .40 minutes 24 seconds

Step 14 DoUnlock -took 1.36 minutes 82 seconds

Step 15 RelinkRDS -took .61 minutes 37 seconds

Step 16 ApplyASMPatches -took .46 minutes 28 seconds

Step 17 ApplyRDBMSPatches -took 0 minutes 0 seconds

Step 18 LockUpGI -took 2.55 minutes 153 seconds

Step 19 DbcaDB -took 29.80 minutes 1788 seconds

4576 seconds, 76.26 minutes in total and sum minutes is 76.22 minutes...:)

Database MachineSample build log overview

23

One Command – The Tool

• Results– Repeatable– Consistent– Complete– Updateable– Uniform– Less errors– Documented– Less human keystrokes

24

Helpful ToolsUse alongside One Command

• Check RAC Technology Matrix on OTN: linux, Unix, Windows and inside My Oracle Support

• Cluster Verification Utility

• Cluster Health Monitor

• Use oracle-validated rpm to set/install kernel rpms/parameters (Note: 728346.1)

25

Installation Methods

• Oracle Universal Installer (OUI, runInstaller)– GUI based– Silent with response file– Allows for software only (no configuration)

• Cloning (clone.pl)– Uses OUI in silent mode under the covers

• OEM Provisioning Pack

26

11.2 Install ImprovementsAutomatic SSH configuration

27

11.2 Install ImprovementsOUI Integrated with CVU

28

11.2 Install ImprovementsCVU Fixups

29

11.2 Install ImprovementsSave Response File

• Also auto saved to Oracle Home/inventory/response

• For 11gR1 use the –record flag with runInstaller

Vitor Pacheco Moreira, Manager DB Services

September 2010

Amadeus

An essential industry provider for distribution in 2009

95%of world’s schedulednetwork airline seats

103,000+Travel agency locations

503 millionBookings processed

40Low Cost Carriers

Over 260Airline websites

85,000+Hotel properties

21%Online booking

145Hosted airlines

150 millionLines of written Program code

Operations excellence

The worlds no 1 processor of travel transactions

High Security Facility

Computer center concept ensuring uninterrupted service

Uninterrupted power supply

No single Point of Failure

Multiple power and network connections

Vision Statement

More than 30 DB Clusters in Production About 15 Clusters in Test On average we deploy a new cluster per month in Production On average we perform a cluster change per week

What we want to achieve: Deployment best practices

Favoring availability and reliability Identify appropriate times for deployment

Consistent deployment in all platforms Automation and minimization of manual processes Documentation and automated feed to the CMDB

Deployment inventory Reference to configurations

OneCommand - First impressions Positives

Configure first and then deploy is very appealing Good fit to the Operational Processes Favors revision and reuse

Silent installer enables automation and time adaptation I.e., configure during working hours, deploy outside of

peak hours

Platform independent Same process in HP-UX and Linux

Flexible, adaptable

OneCommand - First impressionsExisting constraints

Limited adaptation to customer standards Demands manual changes

Constrained to the first deployment phase Other aspects of the deployment are not covered by the tool Different tools needed for patching, reconfigurations,

extensions of the clusters, etc

Missing a central repository of configurations/deployments Comparison between different deployments Reutilization and cloning of deployments Reverse engineering

What we would like to have

Repository of deployments/configurations Extensions to other areas of deployment

Adding new nodes to a Cluster Changing a cluster configuration

Process to transform a configuration in an online manner Based on a previous deployment Fallback included

Alternative to UI deployment processes Ex.: Patch Management provided by OEM

Rehearse/deploy process Rehearse in a Test environment Deploy in Production

OneCommand in three bullet points

Light weight

Configure and deploy

Addresses only one part of the deployment

39

One Command – Going forward…

• Cloned software images – posssibly – Allows updates to Grid, ASM and RAC

• Latest patches and bundle patches• Recommended parameters• Bake in the latest and greatest patchset

• Add / Delete Node– Attend Next Session in this room

• Install and Configuration become a non-event…

40

OneCommandDemonstration - Status

41

One CommandFeature Summary

• Automate and control your RAC Install

• Repeatable, Error Free install

• Bake in Best Practices

• Do it RIGHT every time

42

AQ&Q U E S T I O N SQ U E S T I O N S

A N S W E R SA N S W E R S

43

Next Session here at OOW 2010

S317077 - Oracle RAC on Oracle VM: Best Practices

Running today’s non-critical business applications in virtualized environments has proven to be efficient and cost-saving. However, highly available applications are typically incompatible with commonly used software virtualization solutions. With the combination of Oracle VM and Oracle Real Application Clusters (Oracle RAC), Oracle now offers a highly available, grid-ready virtualization solution for the datacenter. This session reviews configuration best practices and deployment examples of Oracle RAC in Oracle VM environments. It introduces templates that automatically create a cluster with all recommended patches and best practices. The session will interest architects, DBAs, and system administrators.

44

45© 2009 Oracle Corporation