RACGuides_Rac11gR1OnWindows

Table of ContentsRac11gR1OnWindows........................................................................................................................................1

1. *Introduction.......................................................................................................................................1 1.1. *What you need to know....................................................................................................1

1.1.1. Software required for install...............................................................................1 1.1.2. Processor Model.................................................................................................2

1.2. *Installation steps..........................................................................................................................................2 1.3. *Schematic....................................................................................................................................................2

1.3.1. Hardware/software configuration BEFORE Oracle software install............................................2 1.3.2. Hardware/software configuration AFTER Oracle software install..............................................3

1.4. *Installation Method.....................................................................................................................................4 2. Prepare the cluster nodes for Oracle RAC.......................................................................................................4

2.1. User Accounts..................................................................................................................................4 2.2. Installing Using Windows Remote Desktop Client.........................................................................6 2.3. Environment Variables....................................................................................................................6 2.4. Networking......................................................................................................................................7

2.4.1. Network Ping Tests..........................................................................................................8 2.4.2. Network Adapter configuration.......................................................................................8 2.4.3. Network Adapter naming and binding order...................................................................8 2.4.4. Net Use Test...................................................................................................................11 2.4.5. Disable DHCP Media Sense..........................................................................................11

2.5. Remote Registry Connect...........................................................................................................................13 2.6. Stopping Services........................................................................................................................................17 2.7. Time Sync...................................................................................................................................................18 2.8. Stage the Oracle Software...........................................................................................................................18 2.9. CVU stage check.........................................................................................................................................19 3. Prepare the shared storage for Oracle RAC...................................................................................................20

3.1. Shared Disk Layout........................................................................................................................20 3.2. Enable Automount.........................................................................................................................21 3.3. Clean the Shared Disks - Optional Step.........................................................................................22 3.4. Create Logical partitions inside Extended partitions.....................................................................23

3.4.1. View Created partitions.................................................................................................25 3.5. List Drive Letters........................................................................................................................................25

3.5.1. Remove Drive Letters.................................................................................................................26 3.5.2. List volumes on Second node.....................................................................................................27

3.6. View Disks using diskmgmt.msc................................................................................................................28 4. Oracle Clusterware Installation and Configuration.......................................................................................28

4.1. CVU Pre Oracle Clusterware install check....................................................................................29 4.2. Oracle Clusterware Install..............................................................................................................30

4.2.1. Oracle Clusterware has been installed...........................................................................59 5. Oracle Clusterware patching..........................................................................................................................59

5.1. Apply the latest major patchset......................................................................................................60 5.1.1. Install the patch software...............................................................................................60 5.1.2. Stop the Clusterware software on the first node............................................................66 5.1.3. Stop any other Clusterware processes...........................................................................67 5.1.4. run the patch111.bat file................................................................................................69

i

Rac11gR1OnWindows

1. *Introduction

1.1. *What you need to know

For those of you starting a RAC install for the first time. All this will be new. For those of you with 10g RACon Windows experience there are just a few changes.

Disk requirements for Oracle Clusterware devicesThe storage requirement for the OCR & vote devices used by Oracle Clusterware has been increasedto 256 MB.

Better support for IP addressIP addresses from what is sometimes known as the non-routable address ranges. The previous releasehad some restrictions that could be easily worked around. These restrictions have been removed in the11g version and the workarounds are no longer required.

1.1.1. Software required for install

Microsoft Windows 2003

Microsoft Windows 2003 – Service Pack 2 is strongly recommended, do not run with SP1• Base Oracle 11gR1 DVD• The latest Oracle Patchset (currently 11.1.0.7 available as patch 6890831 for x64)• The latest mini patch (currently PATCH 34 available as patch 9393550 for x64) - These patches arecumulative - The latest mini patch will have all previous mini patch components with it. Use MetalinkNote:373040.1 : 'How To Identify and Locate the Latest Windows MiniPatch For Your PatchsetVersion'.

•

The latest Oracle Cluster verify Utility (CVU) from here :http://www.oracle.com/technology/products/database/clustering/cvu/cvu_download_homepage.html

•


For Microsoft Windows 2008 – Service Pack 2 is strongly recommended, do not run with SP1• Oracle Database 11g Release 1 (11.1.0.7.0) for Microsoft Windows Server 2008 x64• The latest mini patch (currently PATCH 24 available as patch 9384497 for x64) - These patches arecumulative - The latest mini patch will have all previous mini patch components with it. Use MetalinkNote:373040.1 : 'How To Identify and Locate the Latest Windows MiniPatch For Your PatchsetVersion'.

•

The latest Oracle Cluster verify Utility (CVU) from here :http://www.oracle.com/technology/products/database/clustering/cvu/cvu_download_homepage.html

•

Do not mix Microsoft Operating Systems between nodes in a cluster. e.g Windows 2003 X64 on one node andWindows Xp X64 on another

Rac11gR1OnWindows 1

http://www.oracle.com/technology/products/database/clustering/cvu/cvu_download_homepage.html

http://www.oracle.com/technology/products/database/clustering/cvu/cvu_download_homepage.html

1.1.2. Processor Model

This paper covers both 32bit and 64bit install. Please note that The OS Version of Oracle you install mustmatch the OS Chip Version.


Windows 2003 32bit - you must install the 32bit versions of the Oracle software.• Windows 2003 64bit X64 - you must install the 64bit X64 versions of the Oracle software.• Windows 2003 64bit Itanium IA64 - you must install the 64bit Itanium IA64 versions of the Oraclesoftware.

•


Windows 2008 32bit - you must install the 32bit versions of the Oracle software.• Windows 2008 64bit X64 - you must install the 64bit X64 versions of the Oracle software.•

1.2. *Installation steps

To summarise the install steps are:

Preparation

Pre-reqs. to make sure the cluster is setup OK.♦ Stage all the software on one node, typically Node1♦

•

Establish Oracle Clusterware

Install the Oracle Clusterware (using the push mechanism to install on the other nodes in thecluster)

♦

Patch the Clusterware to the latest patchset♦

•

Establish ASM

Install an Oracle Software Home for ASM♦ Patch the ASM Home to the latest patchset♦ Create the Listeners♦ Create the ASM Instances and initial Disk Group♦

•

Establish RAC Database

Install an Oracle Software Home for RAC Database♦ Patch the RAC Database Home to the latest patchset♦ Create the RAC Database Instances♦

•

1.3. *Schematic

The following is a schematic of the software & hardware layout of a 2node RAC cluster. As explained in thisdocument the actual number of LUN’s required will vary depending on your mirroring requirements.

1.3.1. Hardware/software configuration BEFORE Oracle software install

1.1.2. Processor Model 2

1.3.2. Hardware/software configuration AFTER Oracle software install

Notice that there are a number of LUNs present to both machines from the shared storage.

5 of 270MB LUNs

2 are used for the OCR devices♦ 3 are used for the vote devices♦

•

9 of 1GB LUNs

6 are used for the +DATA ASM diskgroup♦ 3 are used for the +FLASH diskgroup.♦

•

Also notice there is a dedicated switch on the cluster interconnect.

1.3.1. Hardware/software configuration BEFORE Oracle software install 3

1.4. *Installation Method

This document details one method of installing a 2-node Oracle 11gR1 RAC cluster on Windows:

NTFS_RAW_ASM: The Oracle Cluster, ASM & Oracle Database Homes are established on thelocal disk of each of the RAC nodes. The files required by Oracle Clusterware are on RAW partitions.The database data-files are on ASM. The local Homes for Oracle Clusterware, ASM and RAC take upa total of 6.5GB on each nodes local disk filesystem.

•

It should be noted that there are 2 other popular installation configurations. This document does not coverthese methods:

NTFS_RAW_RAW: The Oracle Cluster, ASM & Oracle Database Homes are established on thelocal disk of each of the RAC nodes. The files required by Oracle Clusterware are on RAW partitions.The database data-files are also on RAW.

•

NTFS_OCFS_OCFS: The Oracle Cluster, ASM & Oracle Database Homes are established on thelocal disk of each of the RAC nodes. The files required by Oracle Clusterware are on OCFS. Thedatabase data-files are also on OCFS.

•

There are other possible combinations although Oracle recommends one of the above methods.

Oracle Database 11g introduces the possibility of using directnfs for the database files

You cannot place the Clusterware devices on directnfs. Directnfs is not covered here•

2. Prepare the cluster nodes for Oracle RAC

This page includes hidden sections, use the and image for each section to show/hide the section

or you can 'Show' or 'Hide' all by selecting here : Show all Hide all

This installation routine presumes that you have a 2-node Windows cluster. There are a number of items thatrequire checking before the install commences. Getting this bit right will enhance your install experience.

User Accounts1. Installing using Remote desktop client.2. Environment Variables3. Networking4. Remote Registry Connect5. Stopping Services that might impact the installation process6. Time sync7. Stage the Oracle Software8. Run CVU9.

It is essential that these items are checked and are configured correctly before the install commences.

2.1. User Accounts

Run the installation as the local Administrator account. The local admin username and password must be thesame on both nodes. If you must use a domain account, then you must ensure that the domain user isexplicitly declared as a member of the local Administrators (not granted membership to this group throughanother group) on each node in the cluster.

1.4. *Installation Method 4

Not using an administrator account that is explicitly declared by username in the Local administrators groupwill cause the install to fail later on

Show the User Account setup information Hide the User Account setup information

For Microsoft Windows 2008, you will need to change the elevation prompt behavior for administrators to"Elevate without prompting" to allow for user equivalence to function properly:

Open a command prompt and type â–�secpol.mscâ–� to launch the Security Policy Consolemanagement utility.

1.

From the Local Security Settings console tree, click Local Policies, and then Security Options2. Scroll down to and double-click User Account Control: Behavior of the elevation prompt foradministrators.

3.

From the drop-down menu, select: Elevate without prompting (tasks requesting elevation willautomatically run as elevated without prompting the administrator)

4.

Click OK to confirm the changes.5. Repeat steps 1-5 on ALL cluster nodes.6.

You also must ensure that the Administrators group is listed under â–�Manage auditing and security logâ–�:

Open a command prompt and type â–�secpol.mscâ–� to launch the Security Policy Consolemanagement utility.

1.

Click on â–�Local Policiesâ–�2. Click on â–�User Rights Assignmentâ–�3. Locate and double click the â–�Manage auditing and security logâ–� in the listing of User RightsAssignments.

4.

If the Administrators group is NOT listed in the â–�Local Security Settingsâ–� tab, add the group now.5. Click OK to save the changes (if changes were made).6. Repeat steps 1-6 on ALL cluster nodes.7.

2.1. User Accounts 5

2.2. Installing Using Windows Remote Desktop Client

For Microsoft Windows 2003, if you must use the MS Terminal Services Client it is essential that you invokethe mstsc.exe application with the /console parameter which connects to the console session of the specifiedWindows Server. From the Start-> run menu you must type mstsc /v:nodename /console For moreinformation go here :http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ts_cmd_mstsc.mspx?mfr=true

For Microsoft Windows 2008, the /admin parameter should be used instead of the /console parameter withMS Terminal Services Client. From the Start-> run menu you must type mstsc /v:nodename /adminFor more information go here: http://support.microsoft.com/kb/947723

2.3. Environment Variables

Make sure that both the TEMP and TMP environment variables for both the install user and the LocalSystemaccount are set to point at sensible directories. e.g.

TEMP=C:\WINDOWS\TEMP• TMP=C:\WINDOWS\TEMP•

and that the directory actually exists. You should check these values are the same on all nodes in the cluster.

The installer assumes that the local user and system user TMP & TEMP environment variables are the same.It copies temporary binaries to remote nodes at that path. If they are not the same on all nodes the install willfail.

Show the Enviroment Variable setup information Hide the Enviroment Variable setup information

2.2. Installing Using Windows Remote Desktop Client 6

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ts_cmd_mstsc.mspx?mfr=true

http://support.microsoft.com/kb/947723

2.4. Networking

You will need a minimum of 2 network adapters per machine, 1 adapter is the public interface. The otheradapter, the private interface, is used for Oracle RAC node membership and inter-instance traffic. The privateinterface adapters should be connected to each other via a network switch which is used exclusively for theinterconnect traffic. In 2 node environments do not be tempted to use a 'Crossover Cable'. Best practice is touse more than 2 adapters, Before installation of the Oracle software you take 2 of the adapters on the privateinterface and team them together to create what looks like a single, highly available adapter for theinterconnect traffic. You can then take the remaining 3rd adapter and use it for the public interface; somecustomers even team their public adapters as well. In that case you would need to start with 4 adapters, 2public & 2 private. Ensure you team the adapters before starting installation. Most customers useactive/passive teaming rather than active/active. It is recommended that all failure scenarios be testedwhichever teaming method is chosen. Please be aware that even with 2-node cluster you must use a dedicatednetwork switch on the interconnect, Crossover cables are not supported. Other settings recommended for theNICS are :

Flow Control : Auto• Speed & Duplex : do not leave this as Auto - instead fix it to full, at the maximum speed the card /switch will allow (typically 1Gbit)

•

You will need a total of 3 IP addresses per node:

The public IP address, which should be recorded in hosts file on each node and, if available, DNS.This IP Address should be bound to the public adapter before starting the install. It should be a static,not DHCP, address

•

The private IP address, which should be from a different subnet than the public IP address. Thisaddress does not require registering in DNS but you should place an entry in the hosts file on eachnode. This IP Address should be bound to the private adapter before starting the install. It should be astatic, not DHCP, address

•

A VIP address, which should be from the same subnet as the public IP address and should berecorded in DNS and the hosts file on each node. This IP Address should NOT be bound to the publicadapter before starting the install. Oracle Clusterware is responsible for binding this address. It shouldbe a static, not DHCP, address

•

If you do not have a DNS server then make sure both the public and the VIP addresses are entered into all therelevant hosts files that are normally found in the %SystemRoot%\system32\drivers\etc\hostsfile.

Show Networking setup information Hide Networking setup informationYou should use ipconfig on each node to confirm the correct IP addresses are bound to the correct adapters

C:\Documents and Settings\Administrator>ipconfigWindows IP Configuration

Ethernet adapter PublicLAN: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 10.10.10.11 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . :

Ethernet adapter PrivateLAN: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.10.11 Subnet Mask . . . . . . . . . . . : 255.255.255.0

2.4. Networking 7

Default Gateway . . . . . . . . . :A sample hosts file

127.0.0.1 localhost10.10.10.11 winnode1 # Also in DNS if available10.10.10.21 winnode2 # Also in DNS if available

10.10.10.51 winnode1-vip # Also in DNS if available10.10.10.61 winnode2-vip # Also in DNS if available

192.168.10.11 winnode1-priv192.168.10.21 winnode2-priv

It is important to confirm that networking is configured correctly before commencing install.

2.4.1. Network Ping Tests

There are a series of 'ping' tests that should be completed, and then the network adapter binding order shouldbe checked. You should ensure that the public IP addresses resolve correctly and that the private addresses areof the form 'nodename-priv' and resolve on both nodes via the hosts file.

Public Ping test•

Pinging Node1 from Node1 should return Node1's public IP address Pinging Node2 from Node1 should returnNode2's public IP address Pinging Node1 from Node2 should return Node1's public IP address Pinging Node2from Node2 should return Node2's public IP address

Private Ping test•

Pinging Node1 private from Node1 should return Node1's private IP address Pinging Node2 private fromNode1 should return Node2's private IP address Pinging Node1 private from Node2 should return Node1'sprivate IP address Pinging Node2 private from Node2 should return Node2's private IP address

VIP Ping test•

Pinging the VIP address at this point should fail. VIPs will be activated at the end of the Oracle Clusterwareinstall.

If any of the above tests fail you should fix name/address resolution by updating the DNS or local hosts fileson each node before continuing with the installation.

2.4.2. Network Adapter configuration

If your network adapters allow configuration you should make sure that they are configured for Full Duplexand at the 'fastest' speed consistent among nodes. They should not be left to 'auto-negotiate'.

2.4.3. Network Adapter naming and binding order

You must check the network adapter binding order. The public adapter must be listed first. Windows willnormally name the adapters "Local Area Connection" and "Local Area Connection 2". Take the opportunity torename the adapters on each node at this point. It is important the names used for each class of adapter beconsistent across all nodes.

For Microsoft Windows 2003: In the Control Panel double click on the Network (or Network & Dialup)Connections icon.For Microsoft Windows 2008: From the Start-> run menu you must type ncpa.cpl, and then click OK

2.4.1. Network Ping Tests 8

As an example, rename the public adapter to PublicLAN and the private adapter to PrivateLAN. It isimportant that you use the same names on all nodes. If there are other adapters take the opportunity to renamethem as well taking care to avoid overly long adapter names and use of any special characters (spaces,periods, dashes etc) in the adapter names.

2.4.3. Network Adapter naming and binding order 9

You must confirm the network adapter binding order on all the nodes in the cluster. Select the menu item'Advanced->Advanced settings...'

2.4.3. Network Adapter naming and binding order 10

On the Adapters and Bindings TAB you must ensure that the public adapter is listed first and the privateadapter is listed second. If they are not in this order: select the public adapter and use the up arrow button tothe right of the Connections list box to move the public adapter to the top of the list. It is very important toconfirm this on all nodes in the cluster

2.4.4. Net Use Test

Software gets distributed between the nodes via copying to the remote nodes from the local node. You shouldensure that this procedure will be successful by testing the net use commandOn node1 issue the following command:

C:\>net use \\winnode2\c$The command completed successfully.This should return successOn node2 issue the following command:C:\>net use \\winnode1\c$The command completed successfully.This should return success

2.4.5. Disable DHCP Media Sense

You should disable media sense. Media Sense allows Windows to uncouple an IP address from a card whenthe link to the local switch is lost. You should disable this activity using the registry editor regedit.

2.4.4. Net Use Test 11

Navigate to the Key HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters andright click to create a new key of type DWORD.

2.4.5. Disable DHCP Media Sense 12

make sure that the Key is called DisableDHCPMediaSense, is of type DWORD and has a value of 1.

2.5. Remote Registry Connect

There can sometimes be an issue during the install when Oracle attempts to update the registry on a remotenode. You should check that this is possible. Whilst the registry editor is still open select the File->ConnectNetwork Registry... menu item

Show Remote Registry information Hide Remote Registry information

2.5. Remote Registry Connect 13

In the 'Enter the object name...' edit box enter the name of the other node in the cluster (e.g. winnode2) andclick OK


Wait for the node to appear in the registry tree. If this works then remote registry connect is working and youcan continue.


If this fails then you probably have a policy set to disallow this. You need to change this policy.When done you can right click on the node in the regedit tree and select disconnect.


2.6. Stopping Services

There can be issues with some of the services, which may already be running on the cluster nodes. Typically aMicrosoft Service: Distributed Transaction Coordinator (MSDTC) can interact with Oracle software duringinstall. It is recommended that this service is stopped and set to ‘manual’ start using services.msc on bothnodes.

Show Services information Hide Services information

Select the Action->Properties Menu item.

2.6. Stopping Services 17

Stop the service and set the Startup type to Manual, repeat on all nodes in the cluster. If, after completing theinstall, the MS DTC service is required it can be restarted and set to auto start.

2.7. Time Sync

There is a general requirement for Oracle RAC that the time on all the nodes be the same. Typically this canbe achieved using Network Time Server protocol. At the very least you should ensure that the system clockson all nodes are as close as possible.

2.8. Stage the Oracle Software

It is recommended that you stage the required software onto a local drive on Node 1 of your cluster.Important. Ensure that you use only 32 bit versions of the Oracle Software on a 32bit OS and 64 bit versionsof the Oracle Software on a 64bit OSA suggested stage for Microsoft Windows 2003 is as follows

Oracle 11g Release 1 EE (11.1.0.6) (1 DVD ) - C:\stage\11gR1• Oracle Patch 1 (11.1.0.7) (from My Oracle Support) - C:\stage\11.1.0.7• The latest mini patch : currently patch 24 (available on My Oracle Support as patch 9384497) -C:\stage\patch24

•

A suggested stage for Microsoft Windows 2008 is as follows

Oracle Database 11g Release 1 (11.1.0.7.0) for Microsoft Windows Server 2008 x64 - C:\stage\11gR1• The latest mini patch : currently patch 24 (available on My Oracle Support as patch 9384497) -C:\stage\patch24

•

2.7. Time Sync 18

The 11gR1 now integrates the Oracle Clusterware, Database and Client install into one DVD with onesetup.exe program.

If you download the software from OTN you will not get the integrated installer. You will have separatedownloads for :

Oracle Clusterware and• ASM/Database•

2.9. CVU stage check

Now you can run the CVU to check the state of the cluster prior to the install of the Oracle Software.Remember to check if there is a newer version of CVU available on otn compared to the one that ships on theinstallation media

Show CVU output Hide CVU outputZ:\Disk1>runcluvfy stage -post hwos -n winnode1,winnode2 -verbose 1 file(s) copied.C:\WINDOWS\temp\cvtmphome\oui\lib\win32\msvcp71.dllC:\WINDOWS\temp\cvtmphome\oui\lib\win32\msvcr71.dll 2 file(s) copied.

Performing post-checks for hardware and operating system setupChecking node reachability...

Check: Node reachability from node "winnode1" Destination Node Reachable? ------------------------------------ ------------------------ winnode1 yes winnode2 yesResult: Node reachability check passed from node "winnode1".

Checking user equivalence...

Check: User equivalence for user "Administrator" Node Name Comment ------------------------------------ ------------------------ winnode2 passed winnode1 passedResult: User equivalence check passed for user "Administrator".

Checking node connectivity...

Interface information for node "winnode2" Interface Name IP Address Subnet Subnet Gateway Default Gateway Hardware Address ---------------- ------------ ------------ ------------ ------------ ------------ PublicLAN 10.10.10.21 10.10.10.0 10.10.10.21 192.168.1.254 00:0C:29:E3:82:6C PrivateLAN 192.168.10.21 192.168.10.0 192.168.10.21 192.168.1.254 00:0C:29:E3:82:76


Check: Node connectivity of subnet "10.10.10.0" Source Destination Connected?

------------------------------ ------------------------------ ---------------- winnode2:PublicLAN winnode1:PublicLAN yes

Result: Node connectivity check passed for subnet "10.10.10.0" with node(s) winnode2,winnode1.

Check: Node connectivity of subnet "192.168.10.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- winnode2:PrivateLAN winnode1:PrivateLAN yes

Result: Node connectivity check passed for subnet "192.168.10.0" with node(s) winnode2,winnode1.

2.8. Stage the Oracle Software 19

WARNING:Could not find a suitable set of interfaces for VIPs.WARNING:Could not find a suitable set of interfaces for the private interconnect.

Result: Node connectivity check passed.

Checking shared storage accessibility...

Shared storage check failed on nodes "winnode2,winnode1".

Post-check for hardware and operating system setup was unsuccessful on all the nodes.

Notice the Shared Storage check failed: This is because this test cluster is using iSCSI and CVU cannot checkthe ‘shared-ness’ of iSCSI disks. Also it could not automatically determine the distinct public and privatenetwork adapters.

Show all Hide all

3. Prepare the shared storage for Oracle RAC

This section describes how to prepare the shared storage for Oracle RAC

Shared Disk Layout1. Enable Automounting of disks on Windows2. Clean the Shared Disks - Optional Step3. Create Logical partitions inside Extended partitions4. Drive Letters5. View Disks6.

3.1. Shared Disk Layout

It is assumed that the two nodes have local disk primarily for the operating system and the local OracleHomes. Labelled C: The Oracle Clusterware software also resides on the local disks on each node. The 2nodes must also share some central disks. This disk must not have cache enabled at the node level. i.e. if theHBA drivers support caching of reads/writes it should be disabled. If the SAN supports caching that is visibleto all nodes then this can be enabled.

At least 2 empty partitions are required for the Oracle Clusterware install using external mirroring/redundancy

One for the Oracle Cluster Registry (OCR).• One for the vote device•

If the disk system used to provide the shared physical disk does not provide some form of RAID protectionthen Oracle recommends that you use the built in mirroring/redundancy capabilities provided by OracleClusterware for the required Clusterware RAW partitions

Two for the Oracle Cluster Registry (OCR).• Three for the vote devices•

All these partitions should be a minimum of 256MB each. Because of space used by extended and logicalpartitions it is recommended that these LUNs be a minimum of 270MB. If you choose to use Oracle mirroringyou should ensure that the partitions created for the mirrors are on separate physical devices.

2.9. CVU stage check 20

The first disk (Disk 0) is the local C: drive used for the software install. The Storage Administrator hasprovisioned 14 LUNs from the shared disk array (Disk1 – Disk14)

Disk1 – Disk5 are used for Oracle Clusterware• Disk6 – Disk11 are used by ASM for the +DATA diskgroup• Disk12– Disk14 are used by ASM for the +FLASH diskgroup•

In this document we will use the diskpart command line tool to manage these LUNs. You must create logicaldrives inside of extended partitions for the disks to be used by Oracle Clusterware and Oracle ASM. Theremust be no drive letters assigned to any of the Disks1 – Disk14 on any node. For MIcrosoft Windows 2003 itis possible to use diskmgmt.msc instead of diskpart (as used in the following sections) to create thesepartitions. For Microsoft Windows 2008, diskmgmt.msc cannot be used instead of diskpart to create thesepartitions.

3.2. Enable Automount

You must enable automounting of disks for them to be visible to Oracle Clusterware. On each node log in assomeone with Administrator privileges then Click START->RUN and type diskpart

C:\>diskpart

Microsoft DiskPart version 5.2.3790.3959Copyright (C) 1999-2001 Microsoft Corporation.On computer: WINNODE1

DISKPART>AUTOMOUNT ENABLERepeat the above command on all nodes in the cluster

3.1. Shared Disk Layout 21

3.3. Clean the Shared Disks - Optional Step

You may want to clean your shared disks before starting the install. Cleaning will remove data from anyprevious failed install. But see a later Appendix for coping with failed installs. On Node1 from within diskpartyou should clean each of the disks. WARNING this will destroy all of the data on the disk. Do not selectthe disk containing the operating system or you will have to reinstall the OSCleaning the disk ‘scrubs’ every block on the disk. This may take some time to complete.

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt -------- ---------- ------- ------- --- --- Disk 0 Online 8189 MB 8033 KB Disk 1 Online 298 MB 298 MB Disk 2 Online 298 MB 298 MB Disk 3 Online 298 MB 298 MB Disk 4 Online 298 MB 298 MB Disk 5 Online 298 MB 298 MB Disk 6 Online 1279 MB 1279 MB Disk 7 Online 1279 MB 1279 MB Disk 8 Online 1279 MB 1279 MB Disk 9 Online 1279 MB 1279 MB Disk 10 Online 1279 MB 1279 MB Disk 11 Online 1279 MB 1279 MB Disk 12 Online 1279 MB 1279 MB Disk 13 Online 1279 MB 1279 MB Disk 14 Online 1279 MB 1279 MBNow you should clean disks 1 – 14 (Not disk0 as this the local C: drive)DISKPART>select disk 1Disk 1 is now the selected disk.DISKPART> clean all

DISKPART> select disk 2Disk 2 is now the selected disk.DISKPART> clean all





DISKPART> select disk 7Disk 7 is now the selected disk.

3.3. Clean the Shared Disks - Optional Step 22

DISKPART> clean all








3.4. Create Logical partitions inside Extended partitions

Assuming the disks you are going to use are completely empty you must create an extended partition and theninside that partition a logical partition. In the following example, for Oracle Clusterware, I have dedicatedLUNS for each device. This is not strictly necessary, you can combine an OCR & vote device onto onephysical LUN, creating 2 partitions inside the extended partition although it would be foolish for example toplace the OCR and OCRMIRROR devices on the same LUN.

DISKPART> select disk 1Disk 1 is now the selected disk.DISKPART> create part extDiskPart succeeded in creating the specified partition.DISKPART> create part logDiskPart succeeded in creating the specified partition.


DISKPART> select disk 3Disk 3 is now the selected disk.

3.4. Create Logical partitions inside Extended partitions 23

DISKPART> create part extDiskPart succeeded in creating the specified partition.DISKPART> create part logDiskPart succeeded in creating the specified partition..








DISKPART> select disk 11

3.4. Create Logical partitions inside Extended partitions 24

Disk 11 is now the selected disk.DISKPART> create part extDiskPart succeeded in creating the specified partition.DISKPART> create part logDiskPart succeeded in creating the specified partition.



DISKPART> select disk 14Disk 14 is now the selected disk.DISKPART> create part extDiskPart succeeded in creating the specified partition.DISKPART> create part logDiskPart succeeded in creating the specified partition.3.4.1. View Created partitions

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt -------- ---------- ------- ------- --- --- Disk 0 Online 8189 MB 8033 KB Disk 1 Online 290 MB 0 B Disk 2 Online 290 MB 0 B Disk 3 Online 290 MB 0 B Disk 4 Online 290 MB 0 B Disk 5 Online 290 MB 0 B Disk 6 Online 1271 MB 0 B Disk 7 Online 1271 MB 0 B Disk 8 Online 1271 MB 0 B Disk 9 Online 1271 MB 0 B Disk 10 Online 1271 MB 0 B Disk 11 Online 1271 MB 0 B Disk 12 Online 1271 MB 0 B Disk 13 Online 1271 MB 0 B* Disk 14 Online 1271 MB 0 B3.5. List Drive Letters

Diskpart should not add drive letters to the partitions on the local node. The partitions on the other node mayhave drive letters assigned. You must remove them. On earlier versions of Windows 2003 a reboot of the‘other’ node will be required for the new partitions to become visible. Windows 2003 SP2 and Windows 2008do not suffer from this issue.

3.4.1. View Created partitions 25

Using diskpart on Node2

DISKPART> list volume Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 H RAW Partition 290 MB Healthy Volume 1 J RAW Partition 1271 MB Healthy Volume 2 O RAW Partition 1271 MB Healthy Volume 3 M RAW Partition 1271 MB Healthy Volume 4 D DVD-ROM 0 B Healthy Volume 5 L RAW Partition 1271 MB Healthy Volume 6 K RAW Partition 1271 MB Healthy Volume 7 C NTFS Partition 8182 MB Healthy System Volume 8 E RAW Partition 290 MB Healthy Volume 9 N RAW Partition 1271 MB Healthy Volume 10 G RAW Partition 290 MB Healthy Volume 11 F RAW Partition 290 MB Healthy Volume 12 I RAW Partition 290 MB Healthy Volume 13 P RAW Partition 1271 MB Healthy Volume 14 Q RAW Partition 1271 MB Healthy Volume 15 R RAW Partition 1271 MB HealthyNotice that the volumes are listed in a completely different order compared to the disk list.

3.5.1. Remove Drive Letters

You need to remove the drive letters H J O M L K E N G F I P Q R These relate to volumes 0 1 2 3 5 6 8 9 1011 12 13 14 15 Do NOT remove drive letters C & D which, in this case, are local disks (and CD-ROMdrive) These relate to volumes 7 & 4 (In this example)

DISKPART> select volume 0Volume 0 is the selected volume.DISKPART> removDiskPart successfully removed the drive letter or mount point.






3.5. List Drive Letters 26








DISKPART> select volume 15Volume 15 is the selected volume.DISKPART> removDiskPart successfully removed the drive letter or mount point.3.5.2. List volumes on Second node

You should check that none of the RAW partitions have drive letters assigned

DISKPART> list vol Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 RAW Partition 290 MB Healthy Volume 1 RAW Partition 1271 MB Healthy Volume 2 RAW Partition 1271 MB Healthy Volume 3 RAW Partition 1271 MB Healthy Volume 4 D DVD-ROM 0 B Healthy Volume 5 RAW Partition 1271 MB Healthy Volume 6 RAW Partition 1271 MB Healthy Volume 7 C NTFS Partition 8182 MB Healthy System Volume 8 RAW Partition 290 MB Healthy Volume 9 RAW Partition 1271 MB Healthy

3.5.1. Remove Drive Letters 27

Volume 10 RAW Partition 290 MB Healthy Volume 11 RAW Partition 290 MB Healthy Volume 12 RAW Partition 290 MB Healthy Volume 13 RAW Partition 1271 MB Healthy Volume 14 RAW Partition 1271 MB Healthy* Volume 15 RAW Partition 1271 MB HealthyYou can now exit diskpart on all nodes

3.6. View Disks using diskmgmt.msc

The disks should look like the above on all nodes in the cluster.

4. Oracle Clusterware Installation and Configuration

This page includes hidden sections, use the and image for each section to show/hide the section

or you can 'Show' or 'Hide' all by selecting here : Show all Hide all

Next we will install the Oracle Clusterware layer. Oracle Clusterware is an essential component of the OracleRAC database infrastructure. Oracle Clusterware does not require any other clustering software. There is noneed to install Microsoft Cluster Services (MSCS) software.

To install you will need the following information

The local drive that will host the Oracle Clusterware software• The shared devices that will be used by Oracle Clusterware• The public node names and IP addresses for the nodes to be used by the cluster• The private node names and IP addresses for the nodes to be used by the cluster• The Virtual Public IP names and IP addresses for the nodes to be used by the cluster•

3.5.2. List volumes on Second node 28

4.1. CVU Pre Oracle Clusterware install check

Before starting the Oracle Clusterware install it is prudent to complete a CVU check for this stage.

Z:\Disk1>runcluvfy.bat stage -pre crsinst -n winnode1,winnode2 -r 11gR1 -verbose

Show CVU output Hide CVU output 1 file(s) copied.C:\WINDOWS\temp\cvtmphome\oui\lib\win32\msvcp71.dllC:\WINDOWS\temp\cvtmphome\oui\lib\win32\msvcr71.dll 2 file(s) copied.

Performing pre-checks for cluster services setup

Checking node reachability...




Checking administrative privileges...

Administrative privileges check passed.




Check: Node connectivity of subnet "10.10.10.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- winnode2:PublicLAN winnode2:PublicLAN yes winnode2:PublicLAN winnode1:PublicLAN yes winnode2:PublicLAN winnode1:PublicLAN yes winnode2:PublicLAN winnode1:PublicLAN yes winnode2:PublicLAN winnode1:PublicLAN yes winnode1:PublicLAN winnode1:PublicLAN yesResult: Node connectivity check passed for subnet "10.10.10.0" with node(s) winnode2,winnode1.

Check: Node connectivity of subnet "192.168.10.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- winnode2:PrivateLAN winnode1:PrivateLAN yesResult: Node connectivity check passed for subnet "192.168.10.0" with node(s) winnode2,winnode1.

WARNING:Could not find a suitable set of interfaces for VIPs.

WARNING:

4.1. CVU Pre Oracle Clusterware install check 29

Could not find a suitable set of interfaces for the private interconnect.


Checking system requirements for 'crs'...

Check: Operating system version Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- winnode2 Windows Server 2003 Windows Server 2003 passed winnode1 Windows Server 2003 Windows Server 2003 passedResult: Operating system version check passed.

Check: Total memory Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- winnode2 1.63GB (1707464KB) 512MB (524288KB) passed winnode1 1.63GB (1707464KB) 512MB (524288KB) passedResult: Total memory check passed.

Check: Swap space Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- winnode2 2.99GB (3131544KB) 1GB (1048576KB) passed winnode1 2.99GB (3131544KB) 1GB (1048576KB) passedResult: Swap space check passed.

Check: System architecture Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- winnode2 32-bit 32-bit passed winnode1 32-bit 32-bit passedResult: System architecture check passed.

Check: Free disk space in "C:\WINDOWS\TEMP" dir Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- winnode2 4.91GB (5150352KB) 400MB (409600KB) passed winnode1 4.7GB (4924284KB) 400MB (409600KB) passedResult: Free disk space check passed.

System requirement passed for 'crs'

Pre-check for cluster services setup was successful.

4.2. Oracle Clusterware Install

Start the installer by running setup.exe from the staged installation media.

4.2. Oracle Clusterware Install 30

Notes

Notice that the Oracle 11gR1 Installer now combines the Oracle Database, Client andClusterware components

♦

•

Action

Select the Oracle Clusterware radio button♦ Click Next♦

•


Notes

The OUI will name the Oracle Clusterware Home'!OraCrs11g_home'. If you change this youshould make sure that the name you use is unique

♦

By default the Oracle installer will select the Local drive with the most free space and willuse the path :\product\11.1.0\crs. If you change the drive you should make sure that there isenough free space on the selected drive on all the nodes for the home (which is currentlysome 600MB). As clusterware runs it will also create various log files inside the ClusterwareHome.

♦

•

Actions

If the defaults are not acceptable modify them.♦ Click Next♦

•


Notes

The installer will validate the state of the cluster before continuing. If there are issues youshould rectify them before continuing

♦

•

Actions

Click Next♦

•


Notes

Each Cluster requires a name, this should be unique within your organization, The default is asubstring of the node name followed by _cluster

♦

This is where you specify details of all the nodes in the cluster. The installer will defaultnames for the node it is running on. You must add other nodes manually.

♦

Oracle defaults the names to 'nodename', 'nodename-priv', 'nodename-vip'♦

•

Actions

Confirm the Cluster Name selected is acceptable♦ Confirm the Details for the current node are OK. The defaults are:

Public Node Name : must resolve via hosts and or DNS to the public IP address andmust be live

◊

Private Node Name : must resolve via hosts to the interconnect IP address and mustbe live

◊

Virtual Host Name : must resolve via hosts and or DNS to a new IP address and mustnot be live

◊

If these are not correct select the node entry and click Edit... to modify OR◊

♦

Click Add... to add more nodes to the cluster♦

•


Notes

Here you specify the details of the node you wish to add to the cluster nodes list♦

•

Actions

Enter the new node details

Public Node Name : must resolve via hosts and or DNS to the public IP address andmust be live

◊

Private Node Name : must resolve via hosts to the interconnect IP address and mustbe live

◊

Virtual Host Name : must resolve via hosts and or DNS to a new IP address and mustnot be live

◊

♦

Click OK to return to the node list for the cluster♦

•


Notes

If you have more nodes repeast the Add... cycle♦

•

Actions

Click Next♦

•


Notes

The installer lists all the Network adapters. You should have one Adapter correctly identifiedas type 'Public' and at least one adapter correctly identified as type 'Private'. The installer willtry and guess the use of an adapter based on the IP address bound. If it guesses incorrectlyyou must change the usage. Here it has guessed that all adapters are Private, which isincorrect.

♦

•

Actions

Select the Adapter PublicLAN♦ Click Edit...♦

•


Notes

Here you specify the ‘Interface type’ Oracle will use this specific network for♦

•

Actions

Select the Interface Type : Public radio button♦ Click OK♦

•


Notes

You may not have more than 2 Adapters so this step may not be necessary♦

•

Actions

Select the Adapter PublicLAN2♦ Click Edit...♦

•


Notes

Here you specify that Oracle will not use this network♦

•

Actions

Select the Interface Type : Do Not Use radio button♦ Click OK♦

•


Notes

Here you can see we have successfully configured the network adapter usage. Ideally you willhave only 1 adapter set as public and 1 adapter set as private. Other adapters, if available, setto ‘do not use’. If you have multiple public or multiple private adapters it is better to teamthem at the OS adapter driver level before commencing the install.Type : Private

♦

•

Actions

Click Next♦

•


Notes

Here we specify the shared storage devices that will be used by Oracle Clusterware. Ideallyyou will have 2 devices for the OCR, Oracle will mirror to these devices to protect you from asingle OCR device failure. Also you will have an additional 3 vote devices to protect yourcluster from the failure of a single vote device.

♦

If you do not see partitions listed here that you expect to see - It may be because you had aprevious failed install and have not cleaned up correctly - see My Oracle SupportNote:341214.1 : How To clean up after a Failed (or successful) Oracle ClusterwareInstallation on Windows for how to clean up a failed install.

♦

•

Actions

Select the device to be used for the First OCR♦ Click Edit...♦

•


Notes

Here we specify the usage for the selected device♦

•

Actions

Select the Place OCR (Primary) on this partition checkbox♦ Click OK♦

•


Notes

Here you can see the usage for the first OCR device has been set♦ Now we will set the usage for the second OCR device♦

•

Actions

Select the device to be used for the Mirror OCR♦ Click Edit...♦

•


Notes


•

Actions

Select the Place OCR (Mirror) on this partition checkbox♦ Click OK♦

•


Notes

Next we specify the devices to be used for the Oracle Clusterware vote disks♦

•

Actions

Select the device to be used for the First vote device♦ Click Edit...♦

•


Notes


•

Actions

Select the Place Voting Disk on this Partition checkbox♦ Click OK♦

•


Notes

Continue with the second vote device♦

•

Actions

Select the device to be used for the Second vote device♦ Click Edit...♦

•


Notes


•

Actions


•


Notes

Continue with the third vote device♦

•

Actions

Select the device to be used for the third vote device♦ Click Edit...♦

•


Notes


•

Actions


•


Notes

Now you can see that we have 2 OCR devices and 3 vote devices♦

•

Actions

Click Next♦

•


Notes

the installer lists a summary of the planned actions♦

•

Actions

Click Install♦

•


Notes

the installer installs the software onto the local node♦

•

Actions

none required♦

•


Notes

the installer installs the software onto the remote node♦

•

Actions

none required♦

•


Notes

a series of configuration assistants are run at the end of the install♦

•

Actions

none required♦

•


Notes

the installer configuration assistant VIPCA adds the Virtual IP addresses to the PublicLANadapter

♦

•

Actions

none required♦

•


Notes

The installer has completed installation and configuration of Oracle Clusterware♦

•

Actions

Click Exit♦

•


Actions

Click Yes♦

•

4.2.1. Oracle Clusterware has been installed

5. Oracle Clusterware patching

Before continuing with the install you should patch the Oracle Clusterware Home to the latest release. Youuse the same patchset for Oracle Clusterware, ASM and Database Homes. The Clusterware Home shouldhave the highest or equal release level to the other 2 homes.

For Microsoft Windows 2003, the current major patchset is 11.1.0.7 - available as part of patch 6890831For Microsoft Windows 2008, 11.1.0.7 patchset fixes have been included in the Oracle Clusterwareinstallation. No patchset needs to be applied for Microsoft Windows 2008.

For both Microsoft Windows 2003 and Microsoft Windows 2008, you should apply the latest available minipatch. The current mini patch is Patch 24 - available for x64 Windows as part of patch 9384497

So we need to :

Apply the latest major patchset (only for Microsoft Windows 2003)• Apply the latest mini patch•

First you can query the software and active versions of Oracle Clusterware

D:\product\11.1.0\crs\BIN>crsctl query crs softwareversion

4.2.1. Oracle Clusterware has been installed 59

Oracle Clusterware version on node [winnode1] is [11.1.0.6.0]

D:\product\11.1.0\crs\BIN>crsctl query crs activeversionOracle Clusterware active version on the cluster is [11.1.0.6.0]here you can see that the software version = active version = 11.1.0.6

5.1. Apply the latest major patchset

You should stage the patch on one of the nodes in the cluster. Clusterware patches can be applied in a rollingfashion. There is no need to stop the software to install the patch software.

You should read the steps in the readme for the patch very carefully.

For the current patch the steps are :

Install the patch software• Stop the Clusterware software on the first node• Stop any other Clusterware processes• run the patch111.bat file• repeat on the other nodes in the cluster•

5.1.1. Install the patch software

You should run setup from the base of the directory of the patchset on one node of the cluster only.

Notes•

5. Oracle Clusterware patching 60

The installer appears♦ Actions

Click Next♦

•

Notes

You should ensure that the Clusterware home is selected in the first drop down list box♦ The installer should default the directory to the correct location♦

•

Actions

Ensure the correct home is selected♦ Click Next♦

•

5.1.1. Install the patch software 61

Notes

the installer detects that this is a clustered home and automatically selects all the nodes in thecluster

♦

•

Actions

Click Next♦

•


Notes

Some parameters are validated by the installer♦

•

Actions

Click Next♦

•


Notes

This is a summary of the actions the installer will complete♦

•

Actions

Click Install♦

•


Notes

the installer stages the patch on all the nodes in the cluster♦

•

Actions

No action required♦

•


Notes

At the end of the install the installer lists the mandatory steps that must be completed to applythis patch

♦

•

Actions

Click exit♦

•

5.1.2. Stop the Clusterware software on the first node

The software has been staged on each node but it has not yet been applied to the Clusterware homes

5.1.2. Stop the Clusterware software on the first node 66

Notes

You must stop all of the Oracle Clusterware Services using the services.msc applet♦

•

Actions

Stop the following services

OracleObjectService◊ OracleClusterVolumeService◊ OracleCRService◊ OracleCSService◊ OracleEVMService◊

♦

•

5.1.3. Stop any other Clusterware processes

You will find that even though you appear to have stopped all the services the patch will fail unless youcomplete the following

5.1.3. Stop any other Clusterware processes 67

Notes

Using Windows task Manager - you should locate the ons.exe processes♦

•

Actions

No Action Required♦

•

5.1.3. Stop any other Clusterware processes 68

Notes

You should kill both the ons processes♦

•

Actions

Right Click on each process and select End Process♦

•

5.1.4. run the patch111.bat file

You can check the versions of Oracle Clusterware software

D:\product\11.1.0\crs\BIN>crsctl query crs softwareversionOracle Clusterware version on node [winnode1] is [11.1.0.6.0]

D:\product\11.1.0\crs\BIN>crsctl query crs activeversionOracle Clusterware active version on the cluster is [11.1.0.6.0]As you can see the versions are still showing as the base release. Next, run the patch111.bat file - this willupgrade the software on the current node and will restart the Oracle Clusterware processes.

|

D:\>cd \product\11.1.0\crs\install

D:\product\11.1.0\crs\install>patch111.batSuccessful validation check of Oracle CRS services statusSuccessful binary patch of the D:\product\11.1.0\crsSuccessful cleanup of patch subdirectorySuccessful startup of OracleCSServiceSuccessful startup of OracleEvmServiceSuccessful startup of OracleCRService

5.1.4. run the patch111.bat file 69

clscfg: EXISTING configuration version 4 detected.clscfg: version 4 is 11 Release 1.Successfully accumulated necessary OCR keys.Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.node <nodenumber>: <nodename> <private interconnect name> <hostname>node 1: winnode1 winnode1-priv winnode1Creating OCR keys for user 'administrator', privgrp ''..Operation successful.clscfg -upgrade completed succssfullySuccessful upgrade of this node to Oracle Cluster Ready Services 11107</pre>|

One again you can check the Oracle Clusterware software levels

|


D:\product\11.1.0\crs\BIN>crsctl query crs activeversionOracle Clusterware active version on the cluster is [11.1.0.6.0]

| As you can see the software version is now 11.1.0.7 however the active version is still 11.1.0.6. This meansthat the new software is in place on this node but is not yet active. It becomes active when the patch111.batfile completes on the last node in the cluster ---++++ 5.1.5. repeat on the other nodes in the cluster * Stop theClusterware software on the second node * Stop any other Clusterware processes * run the patch111.bat fileon the second node After completing the patch upgrade on the last node you should check the software andactive versions: |


D:\product\11.1.0\crs\BIN>crsctl query crs activeversionOracle Clusterware active version on the cluster is [11.1.0.7.0]

| As you can see the new 11.1.0.7 version is now active. ---++++ 5.1.6. Application of the Oracle Clusterwaremajor patchset is complete ---+++ 5.2. Mini Patch You should now apply the latest mini patch to theclusterware home in accordance with the instructions provided in the README for that patch ---++ 6. OracleASM Home Software Install In this section we establish the Oracle software for the ASM home. ---+++ 6.1.CVU check ---+++ 6.2. Oracle ASM Home Software Install You must launch the installer by runningsetup.exe from the staged installation software. --------------------------------


* Notes * Here we will create a ASM Software home on all the nodes in the cluster * Actions * Select the=Oracle Database 11g= radio button * Click Next --------------------------------

* Notes * Here we can choose the type of database software to be installed * Actions * Select the Enterprise


Edition radio button * Click Next --------------------------------

* Notes * Here we specify the location of various components. An 11g install makes more use of theORACLE_BASE. Most logs will be stored in sub directories under the oracle base. The oracle base will becommon to all installs. The installer will default the ORACLE_BASE to \app\Administrator. Modify asrequired. Also this is where you specify the location of the ASM software home. I usually modify the Homename and Home Path to include the word ASM. This makes it easier to identify later on. If you change thepath you should ensure that you do not use the exact same path as the Oracle Clusterware home * Actions *Confirm entries are OK * Click Next --------------------------------


* Notes * The installer has detected the presence of Oracle Clusterware and uses this to populate this dialogbox. To build a cluster which includes all nodes you must ensure that there are check-boxes next to the nodenames * Actions * Click Select All * Click Next --------------------------------


* Notes * The installer will then complete some Product-Specific Prerequisite checks. These should all passOK – as you have already run the CVU check * Actions * Click Next --------------------------------

* Notes * We are going to install a Software only home and then subsequently configure the software *Actions * Select the Install Software Only radio button * Click Next --------------------------------


* Notes * Here we can see a summary of the install. * Actions * Click Install --------------------------------

* Notes * Here the installer copies the software to all nodes in the cluster * Actions * =none required=--------------------------------


* Notes * After the software install completes you will see this End of Installation dialog * Actions * ClickExit --------------------------------

* Notes * Are you sure ? * Actions * Click Yes ---++++ 6.2.1. Oracle ASM software home has been installed


---++ 7. Oracle ASM Software Home Patching Next we must patch the ASM home to the latest release level.So we need to: * Apply the latest major patchset (only for Microsoft Windows 2003) * For MicrosoftWindows 2003, the current major patchset is 11.1.0.7 - Use the same staged patch as you used for the OracleClusterware Home. * For Microsoft Windows 2008, 11.1.0.7 patchset fixes have been included in the OracleClusterware installation. No patchset needs to be applied for Microsoft Windows 2008. * Apply the latestmini patch * For both Microsoft Windows 2003 and Microsoft Windows 2008, you should apply the latestavailable mini patch. The current mini patch is Patch 24 - available for x64 Windows as part of patch 9384497*IMPORTANT* It is critical that the !OracleRemExec Service is stopped on all nodes in the cluster beforecommencing patching ---+++ 7.1. Apply the latest Major patchset Start the installer by running setup.exe fromthe root of the patch directory on one of the nodes in the cluster. --------------------------------

*Notes * the Universal Installer screen appears * Actions * Click Next --------------------------------


*Notes * You are patching the ASM home. you need to make sure this is selected in the drop down list box *Actions * Select the ASM home in the drop down list box * Click Next --------------------------------

*Notes * here you can specify your metalik credentials for this install. If you leave both fields blank you can


opt out of notifications. * Actions * Enter your email address * Enter your Metalink password * Click Next--------------------------------

*Notes * the installer detects that this is a clustered home and automatically selects all the nodes in the cluster *Actions * Click Next --------------------------------


*Notes * Some parameters are validated by the installer * Actions * Click Next --------------------------------

*Notes * This is a summary of the actions the installer will complete * Actions * Click Install--------------------------------


*Notes * The installer copies the patch to all the nodes in the cluster * Actions * =No action required=--------------------------------

*Notes * The installation is complete * Actions * Click Exit --------------------------------


*Notes * Are you sure * Actions * Click Yes ---+++ 7.2. Run selecthome.bat on 'other' nodes in the cluster |

D:\app\Administrator\product\11.1.0\db_1\BIN>selecthome.batD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\BIN\OraOLEDB11.dllD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\bin\oip11.dllD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\bin\oradc.ocxD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\bin\oo4ocodewiz.dllD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\bin\odbtreeview.ocxD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\bin\oo4oaddin.dllD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\Oraconfig\oraconfigps11.dllD:\app\Administrator\product\11.1.0\db_1\BIN>D:\app\Administrator\product\11.1.0\db_1\OraConfig\oraconfig.exe -RegServerD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s "D:\app\Administrator\product\11.1.0\db_1\MMC Snap-Ins\Primary Snap-In\orammc11.dll"D:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s "D:\app\Administrator\product\11.1.0\db_1\MMC Snap-Ins\Administration Assistant\orammcadm11.dll"D:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s "D:\app\Administrator\product\11.1.0\db_1\MMC Snap-Ins\Administration Assistant\orammccfg11.dll"D:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s "D:\app\Administrator\product\11.1.0\db_1\MMC Snap-Ins\Performance Monitor\orammcpmon11.dll"D:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\bin\oip11.dllD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\bin\oradc.ocxD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\bin\oo4ocodewiz.dllD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\bin\odbtreeview.ocxD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s D:\app\Administrator\product\11.1.0\db_1\bin\oo4oaddin.dllD:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s "D:\app\Administrator\product\11.1.0\db_1\MMC Snap-Ins\Primary Snap-In\orammc11.dll"D:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s "D:\app\Administrator\product\11.1.0\db_1\MMC Snap-Ins\Administration Assistant\orammcadm11.dll"D:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s "D:\app\Administrator\product\11.1.0\db_1\MMC Snap-Ins\Administration Assistant\orammccfg11.dll"D:\app\Administrator\product\11.1.0\db_1\BIN>regsvr32 /s "D:\app\Administrator\product\11.1.0\db_1\MMC Snap-Ins\Performance Monitor\orammcpmon11.dll"

| ---+++ 7.3. Apply the latest Mini patch Next you should apply the latest mini patch in accordance with theinstructions provided in the README for that patch ---+++ 7.4. The ASM home is patched successfully.---++ 8. Oracle RAC Database Listener Creation ---+++ 8.1. Create Node specific network listeners TheOracle network listeners traditionally run from the ASM home. Here we are going to create the listeners usingnetca from the ASM home. --------------------------------


* Notes * You must use the NETCA from the ASM home to create the listeners * Actions * From the startmenu select Oracle – OraASM11g_home1->Configuration and Migration Tools -> Net ConfigurationAssistant --------------------------------


* Notes * Netca detects that the Oracle Clusterware layer is running and offers Cluster or Single Nodeconfiguration * Actions * Select the Cluster configuration radio button * Click Next--------------------------------

* Notes * Netca uses Oracle Clusterware to determine all the nodes in the cluster * Actions * Click Select allnodes * Click Next --------------------------------


* Notes * You get various options – we need to configure listeners * Actions * Select the Listenerconfiguration radio button * Click Next --------------------------------

* Notes * We need to add a listener * Actions * Select the Add radio button * Click Next


--------------------------------

* Notes * Here you get the opportunity to name the listener – Do not change this. The listeners will eventuallybe called LISTENER_nodename1 & LISTENER_nodename2. This is important for RAC * Actions * ClickNext --------------------------------


* Notes * Oracle Net supports various network protocols, although TCP is the most common. * Actions *Ensure the Selected Protocols list includes TCP * Click Next --------------------------------

* Notes * It is possible to choose a non-default Port – I do not recommend this * Actions * Ensure the Use the


Standard port number of 1521 radio button is set * Click Next --------------------------------

* Notes * After configuring the node listeners you get the opportunity to configure more network components* Actions * Select the No radio button * Click Next * Then Click the Finish button to exit the tool ---+++ 8.2.Completed Node specific network listeners creation You have now completed the RAC cluster nodes Networklistener configuration. A new managed resource will have been added to Oracle Clusterware OCR for eachlistener. ---++ 9. Oracle ASM Instance and diskgroup Creation ---+++ 9.1. Create ASM Instance and add the+DATA and +FLASH diskgroups --------------------------------


* Notes * We use the dbca from the ASM install to create the ASM instances * Actions * From the start menuselect Oracle – OraASM11g_home1->Configuration and Migration Tools -> Database ConfigurationAssistant --------------------------------


* Notes * dbca detects the Oracle Clusterware layer is running and offers to create either cluster or singleinstance database * Actions * Select the Oracle Real Application Clusters database radio button * Click Next--------------------------------

* Notes * We use dbca to create RAC databases and ASM instances * Actions * Select the ConfigureAutomatic Storage Management radio button * Click Next --------------------------------


* Notes * You need to make sure you create ASM instances on all the cluster nodes * Actions * Click SelectAll * Click Next --------------------------------

* Notes * Here we specify the password for the ASM Oracle SYS user * Actions * Enter the SYS password *


Enter the same password for the Confirm SYS password * Click Next --------------------------------

* Notes * dbca will create and start ASM instances * Actions * Click OK --------------------------------

* Notes * This should take a few seconds * Actions * =no action= --------------------------------


* Notes * ASM requires disks to be group together into diskgroups. This section will be used to create 2 diskgroups +DATA and +FLASH * Actions * Click Create New --------------------------------

* Notes * At the moment no disks are visible They must be stamped before they appear in the Member disk


list * Actions * Click Stamp Disks --------------------------------

* Notes * You will use asmtool to stamp the disks * Actions * Select the Add or change label radio button *Click Next --------------------------------


* Notes * Here you can see a list of the devices visible to asmtool. The first 2 are the OS C: and D: drives.The next 5 are the devices used by Oracle Clusterware. The next 9 disks are Candidate for ASM. We aregoing to use the first 6 disks for the +DATA diskgroup * Actions * Select the first 6 disks * Check thegenerate stamps with this prefix checkbox * Enter a prefix of DATA * Click Next --------------------------------

* Notes * This is a summary of the actions asmtool will carry out for the DATA disks * Actions * Click Next--------------------------------


* Notes * A final confirmation screen * Actions * Click Finish --------------------------------

* Notes * The ‘stamped’ disks are now visible. We need to stamp the remaining disks for the +FLASHdiskgroup * Actions * Click Stamp Disks --------------------------------


* Notes * Here we go through the same routine * Actions * Select the Add or change label radio button *Click Next --------------------------------

* Notes * You can see the same list as before. Notice the DATA diskgroup disk labels are visible * Actions *


Select the final 3 candidate devices * Check the generate stamps with this prefix checkbox * Enter a prefix ofFLASH * Click Next --------------------------------

* Notes * A final confirmation screen * Actions * Click Finish --------------------------------


* Notes * Now we will assign disks to specific disk groups and create the DATA diskgroup * Actions * In theDisk Group Name enter DATA * Select the External Redundancy radio button * Select the Show Candidatedisks radio button * Select the first 6 disks, the ones that were stamped \\.\ORCLDISKDATAn * Click OK--------------------------------

* Notes * A progress message – this should not take very long * Actions * =none= --------------------------------


* Notes * Here we can see the DATA diskgroup has been created and is mounted on 2/2 instances. We nowneed to create the FLASH diskgroup * Actions * Click Create New --------------------------------

* Notes * Now we will assign disks to specific disk groups and create the FLASH diskgroup For a change we


will create this diskgroup with Normal redundancy * Actions * In the Disk Group Name enter FLASH *Select the Normal radio button * Select the Show Candidate disks radio button * Select the remaining 3 disks,the ones that were stamped \\.\ORCLDISKFLASHn * Click OK --------------------------------

* Notes * A progress message – this should not take very long * Actions * =none= --------------------------------


* Notes * Here we can see the DATA and FLASH diskgroups have been created and are mounted on 2/2instances. This completed the ASM configuration. * Actions * Click Finish --------------------------------

* Notes * A confirmation dialog box * Actions * Click No -------------------------------- ---+++ 9.2. Completed


creation of ASM Instance and add of the +DATA and +FLASH diskgroups Congratulations you haveinstalled ASM, Network listeners and created 2 ASM diskgroups. ---++ 10. Oracle RAC Database HomeSoftware Install ---+++ 10.1. CVU check - Pre Database Install Before installing the RAC Database softwareyou should use the CVU utility to confirm the status of the cluster. |

Z:\Disk1>runcluvfy.bat stage -pre dbinst -n winnode1,winnode2 -r 11gR1 -verbose 1 file(s) copied.C:\WINDOWS\temp\cvtmphome\oui\lib\win32\msvcp71.dllC:\WINDOWS\temp\cvtmphome\oui\lib\win32\msvcr71.dll 2 file(s) copied.

Performing pre-checks for database installation

Checking node reachability...




Checking administrative privileges...

Administrative privileges check passed.


Interface information for node "winnode2" Interface Name IP Address Subnet Subnet Gateway Default Gateway Hardware Address ---------------- ------------ ------------ ------------ ------------ ------------ PublicLAN 10.10.10.61 10.10.10.0 127.0.0.1 192.168.1.254 00:0C:29:E3:82:6C PublicLAN 10.10.10.21 10.10.10.0 10.10.10.21 192.168.1.254 00:0C:29:E3:82:6C PrivateLAN 192.168.10.21 192.168.10.0 192.168.10.21 192.168.1.254 00:0C:29:E3:82:76 PublicLAN2 192.168.1.21 192.168.1.0 192.168.1.21 192.168.1.254 00:0C:29:E3:82:62

Interface information for node "winnode1" Interface Name IP Address Subnet Subnet Gateway Default Gateway Hardware Address ---------------- ------------ ------------ ------------ ------------ ------------ PublicLAN 10.10.10.51 10.10.10.0 127.0.0.1 192.168.1.254 00:0C:29:E3:81:6C PublicLAN 10.10.10.11 10.10.10.0 10.10.10.11 192.168.1.254 00:0C:29:E3:81:6C PrivateLAN 192.168.10.11 192.168.10.0 192.168.10.11 192.168.1.254 00:0C:29:E3:81:76 PublicLAN2 192.168.1.11 192.168.1.0 192.168.1.11 192.168.1.254 00:0C:29:E3:81:62

Check: Node connectivity of subnet "10.10.10.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- winnode2:PublicLAN winnode2:PublicLAN yes winnode2:PublicLAN winnode1:PublicLAN yes winnode2:PublicLAN winnode1:PublicLAN yes winnode2:PublicLAN winnode1:PublicLAN yes winnode2:PublicLAN winnode1:PublicLAN yes winnode1:PublicLAN winnode1:PublicLAN yesResult: Node connectivity check passed for subnet "10.10.10.0" with node(s) winnode2,winnode1.

Check: Node connectivity of subnet "192.168.10.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- winnode2:PrivateLAN winnode1:PrivateLAN yesResult: Node connectivity check passed for subnet "192.168.10.0" with node(s) winnode2,winnode1.


Check: Node connectivity of subnet "192.168.1.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- winnode2:PublicLAN2 winnode1:PublicLAN2 yesResult: Node connectivity check passed for subnet "192.168.1.0" with node(s) winnode2,winnode1.

WARNING:Could not find a suitable set of interfaces for VIPs.

WARNING:Could not find a suitable set of interfaces for the private interconnect.


Checking system requirements for 'database'...

Check: Operating system version Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- winnode2 Windows Server 2003 Windows Server 2003 passed winnode1 Windows Server 2003 Windows Server 2003 passedResult: Operating system version check passed.

Check: Total memory Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- winnode2 1.63GB (1707464KB) 512MB (524288KB) passed winnode1 1.63GB (1707464KB) 512MB (524288KB) passedResult: Total memory check passed.

Check: Swap space Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- winnode2 2.99GB (3131544KB) 1GB (1048576KB) passed winnode1 2.99GB (3131544KB) 1GB (1048576KB) passedResult: Swap space check passed.

Check: System architecture Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- winnode2 32-bit 32-bit passed winnode1 32-bit 32-bit passedResult: System architecture check passed.

Check: Free disk space in "C:\WINDOWS\TEMP" dir Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- winnode2 4.91GB (5150332KB) 400MB (409600KB) passed winnode1 4.7GB (4924256KB) 400MB (409600KB) passedResult: Free disk space check passed.

System requirement passed for 'database'

Checking CRS integrity...

Checking daemon liveness...

Check: Liveness for "CRS daemon" Node Name Running ------------------------------------ ------------------------ winnode2 yes winnode1 yesResult: Liveness check passed for "CRS daemon".


Check: Liveness for "CSS daemon" Node Name Running ------------------------------------ ------------------------ winnode2 yes winnode1 yesResult: Liveness check passed for "CSS daemon".



Check: Liveness for "EVM daemon" Node Name Running ------------------------------------ ------------------------ winnode2 yes winnode1 yesResult: Liveness check passed for "EVM daemon".

Liveness of all the daemons Node Name CRS daemon CSS daemon EVM daemon ------------ ------------------------ ------------------------ ---------- winnode2 yes yes yes winnode1 yes yes yes

Checking CRS health...

Check: Health of CRS Node Name CRS OK? ------------------------------------ ------------------------ winnode2 yes winnode1 yesResult: CRS health check passed.

CRS integrity check passed.

Pre-check for database installation was successful.

| ---+++ 10.2. Oracle RAC Database Home Software Install You must launch the installer by runningsetup.exe from the staged installation software. In this section we establish the Oracle software for the RACDatabase home. --------------------------------

* Notes * We use the same installer for Database homes as Clusterware homes * Actions * Select the =OracleDatabase 11g= radio button * Click Next --------------------------------


* Notes * Here we can choose the type of database software to be installed * Actions * Select the EnterpriseEdition radio button * Click Next --------------------------------

* Notes * Here we specify the location of various components. If you change the path you should ensure that


you do not use the exact same path as the Oracle Clusterware or ASM homes * Actions * Confirm entries areOK * Click Next --------------------------------

* Notes * The installer has detected the presence of Oracle Clusterware and uses this to populate this dialogbox. To build a cluster which includes all nodes you must ensure that there are check-boxes next to the nodenames * Actions * Click Select All * Click Next --------------------------------


* Notes * The installer will then complete some Product-Specific Prerequisite checks. These should all passOK - as you have already run the CVU check * Actions * Click Next --------------------------------

* Notes * We are going to install a Software only home and then subsequently configure the software *


Actions * Select the Install Software Only radio button * Click Next --------------------------------

* Notes * Here we can see a summary of the install. * Actions * Click Install --------------------------------

* Notes * After the software install completes you will see this End of Installation dialog * Actions * Click


Exit --------------------------------

* Notes * Are you sure ? * Actions * Click Yes ---++++ 10.2.1. Oracle RAC Database software home hasbeen installed ---++ 11. Oracle RAC Software Home Patching Next we must patch the RAC Software hometo the latest release level. So we need to: * Apply the latest major patchset (only for Microsoft Windows2003) * For Microsoft Windows 2003, the current major patchset is 11.1.0.7 - Use the same staged patch asyou used for the Oracle Clusterware and Oracle ASM Homes. * For Microsoft Windows 2008, 11.1.0.7patchset fixes have been included in the Oracle Clusterware installation. No patchset needs to be applied forMicrosoft Windows 2008. * Apply the latest mini patch * For both Microsoft Windows 2003 and MicrosoftWindows 2008, you should apply the latest available mini patch. The current mini patch is Patch 24 -available for x64 Windows as part of patch 9384497 *IMPORTANT* It is critical that the !OracleRemExecService is stopped on all nodes in the cluster before commencing patching ---+++ 11.1. Apply the latest Majorpatchset Start the installer by running setup.exe from the root of the patch directory on one of the nodes in thecluster. --------------------------------


*Notes * the Universal Installer screen appears * Actions * Click Next --------------------------------

*Notes * You are patching the ASM home. you need to make sure this is selected in the drop down list box *Actions * Select the ASM home in the drop down list box * Click Next --------------------------------


*Notes * here you can specify your metalik credentials for this install. If you leave both fields blank you canopt out of notifications. * Actions * Enter your email address * Enter your Metalink password * Click Next--------------------------------

*


Notes * the installer detects that this is a clustered home and automatically selects all the nodes in the cluster *Actions * Click Next --------------------------------

*Notes * Some parameters are validated by the installer * Actions * Click Next --------------------------------

*


Notes * This is a summary of the actions the installer will complete * Actions * Click Install--------------------------------

*Notes * The installer copies the patch to all the nodes in the cluster * Actions * =No action required= ---+++11.2. Apply the latest Mini patch Next you should apply the latest mini patch in accordance with theinstructions provided in the README for that patch ---+++ 11.3. The RAC home is patched successfully.---++ 12. Oracle RAC Database Creation ---+++ 12.1. use dbca to create the RAC database-------------------------------


* Notes * You must use the dbca from the RAC database home – not the ASM home--------------------------------

* Notes * dbca detects the Oracle Clusterware layer is running and offers to create either cluster or single


instance database * Actions * Select the Oracle Real Application Clusters database radio button * Click Next--------------------------------

* Notes * We use dbca to create RAC databases * Actions * Select the Create a Database radio button * ClickNext --------------------------------


* Notes * You need to make sure you create RAC database instances on all the cluster nodes * Actions *Click Select All * Click Next --------------------------------

* Notes * Here you get to select the type of database * Actions * Select the General Purpose... radio button *


Click Next --------------------------------

* Notes * Now you specify the preface for the SIDs for the RAC database instances – recommendation is tokeep it simple * Actions * Enter ERI in the Global Database name, The SID should autofill * Click Next--------------------------------


* Notes * Here you get to configure Oracle Enterprise Manager. If you have no Grid Control server then thebest method is to use dbcontrol as detailed here. * Actions * Check the Configure Enterprise managercheckbox * Select the Configure Database Control for local management radio button * Click Next--------------------------------


* Notes * Here we specify the password for the Oracle Database users. In this example we are setting thesame password for all users. You should set a password scheme that meets your requirements. * Actions *Select the Use the Same Administrative Password… radio button * Enter the password * Enter the samepassword for the Confirm password * Click Next --------------------------------


* Notes * Here you specify where you would like your database datafiles stored. We are going to use theASM diskgroups we created earlier. * Actions * Select the Automatic Storage Management (ASM) radiobutton * Click Next --------------------------------


* Notes * dbca displays the diskgroups we previously created. We are going to use the DATA diskgroup *Actions * Check the box on the DATA diskgroup line * Click Next --------------------------------

* Notes * Here we can adjust where various files are placed * Actions * Select the Use Oracle-managed Filesradio button * Ensure +DATA is in the Database Area field * Click Next --------------------------------


* Notes * Here we specify recovery configuration information. We are going to use a flash recovery area. *Actions * Check the Specify Flash Recovery Area checkbox * In the Flash recovery area enter +FLASH * Setthe flash recovery size – remember the size of the +FASH diskgroup * Check the Enable Archiving checkbox* Click Next --------------------------------


* Notes * Here you can choose to add the Oracle Sample schemas * Actions * Check the Sample schemascheckbox * Click Next --------------------------------

* Notes * Here you can modify the default initialisation parameters. * Actions * Click Next


--------------------------------

* Notes * 11g introduces enhanced security settings * Actions * Select the Keep the enhanced… radio button* Click Next --------------------------------


* Notes * 11g will set up some automatic maintenance tasks * Actions * Check the Enable automaticmaintenance tasks checkbox * Click Next --------------------------------

* Notes * Here you can review the placement of various database files * Actions * Click Next--------------------------------


* Notes * You can decide to generate database creation scripts * Actions * Check the Create Databasecheckbox * Click Next --------------------------------

* Notes * A summary screen * Actions * Click Next --------------------------------


* Notes * The database is created * Actions * =none= --------------------------------

* Notes * After the database is created the summary screen is displayed – note the URL for the DatabaseControl * Actions * Click Exit --------------------------------


* Notes * The Database instances will be started on all nodes * Actions * =none= ---+++ 12.2. RAC databasecreation is complete
