You are on page 1of 172

Table of Contents

Rac10gR2OnWindows ........................................................................................................................................1 1. *Introduction.......................................................................................................................................1 1.0.1. Software required for install............................................................................................1 1.0.2. Processor Model.................................................................................................1 1.1. *Installation steps ..........................................................................................................................................2 1.2. *Schematic....................................................................................................................................................2 1.2.1. Hardware/software configuration BEFORE Oracle software install............................................2 1.2.2. Hardware/software configuration AFTER Oracle software install..............................................3 1.3. *Installation Method.....................................................................................................................................3 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. Run the VIP Configuration Assistant manually to configure the VIPs.........................57 4.2.2. Oracle Clusterware has been installed and configured correctly ...................................64 5. Oracle Clusterware patching..........................................................................................................................64 5.1. Apply the latest major patchset......................................................................................................65 5.1.1. Install the patch software...............................................................................................65 5.1.2. Stop the Clusterware software on the first node............................................................71 5.1.3. Stop any other Clusterware processes...........................................................................72 5.1.4. run the patch102.bat file................................................................................................74 5.1.5. repeat on the other nodes in the cluster.........................................................................75 . 5.1.6. Application of the Oracle Clusterware major patchset is complete ...............................75 5.2. Mini Patch...................................................................................................................................................75 6. Oracle ASM Home Software Install..............................................................................................................75 6.1. CVU check.....................................................................................................................................76 6.2. Oracle ASM Home Software Install..............................................................................................76 6.2.1. Oracle ASM software home has been installed.............................................................85 7. Oracle ASM Software Home Patching..........................................................................................................85 7.1. Apply the latest Major patchset.....................................................................................................86 7.2. Apply the latest Mini patch............................................................................................................94 i

Table of Contents
Rac10gR2OnWindows 7.3. The ASM home is patched successfully........................................................................................94 8. Oracle RAC Database Listener Creation.......................................................................................................94 8.1. Create Node specific network listeners ..........................................................................................94 8.2. Completed Node specific network listeners creation ...................................................................104 9. Oracle ASM Instance and diskgroup Creation............................................................................................104 9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups........................................104 9.2. Completed creation of ASM Instance and add of the +DATA and +FLASH diskgroups..........129 10. Oracle RAC Database Home Software Install...........................................................................................129 10.1. CVU check.................................................................................................................................129 10.2. Oracle RAC Database Home Software Install...........................................................................129 10.2.1. Oracle RAC Database software home has been installed..........................................140 11. Oracle RAC Software Home Patching......................................................................................................140 11.1. Apply the latest Major patchset.................................................................................................141 11.2. Apply the latest Mini patch........................................................................................................149 11.3. The RAC Database home is patched successfully.....................................................................149 12. Oracle RAC Database Creation.................................................................................................................149 12.1. use DBCA to create the RAC database ......................................................................................149 12.2. RAC database creation is complete...........................................................................................170

ii

Rac10gR2OnWindows

1. *Introduction
1.0.1. Software required for install
Microsoft Windows 2003 For Microsoft Windows 2003 Service Pack 2 is strongly recommended, do not run with SP1 Base Oracle 10gR2 DVD The latest patchset (currently 10.2.0.4 available as patch 6810189 for x64) The latest mini patch (currently PATCH 34 available as patch 9393550 for x64) - These patches are cumulative - The latest mini patch will have all previous mini patch components with it. Use My Oracle Support ExtNote:373040.1 : 'How To Identify and Locate the Latest Windows MiniPatch For Your Patchset Version'. The latest Oracle Cluster verify Utility (CVU) from here : http://www.oracle.com/technology/products/database/clustering/cvu/cvu_download_homepage.html Microsoft Windows 2008 For Microsoft Windows 2008 Service Pack 2 is strongly recommended, do not run with SP1 Oracle Database 10g Release 2 (10.2.0.4.0) Enterprise/Standard Edition for Microsoft Windows Vista x64 and Microsoft Windows Server 2008 x64 The latest mini patch (currently PATCH 34 available as patch 9393550 for x64) - These patches are cumulative - The latest mini patch will have all previous mini patch components with it. Use My Oracle Support ExtNote:373040.1 : 'How To Identify and Locate the Latest Windows MiniPatch For Your Patchset Version'. 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 and Windows 2003 64bit Itanium IA64 on another

1.0.2. Processor Model


This paper covers both 32bit and 64bit install. Please note that The OS Version of Oracle you install must match the OS Chip Version. Microsoft Windows 2003 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 Oracle software. Microsoft Windows 2008 Windows 2008 32bit - you must install the 32bit versions of the Oracle software. Rac10gR2OnWindows 1

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

1.1. *Installation steps


To summarise the install steps are: Preparation Prerequisites 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 the cluster) 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.2. *Schematic
The following is a schematic of the software & hardware layout of a 2-node RAC cluster. As explained in this document the actual number of LUNs required will vary depending on your mirroring requirements.

1.2.1. Hardware/software configuration BEFORE Oracle software install

1.0.2. Processor Model

1.2.2. Hardware/software configuration AFTER Oracle software install

Notice that there are a number of LUNs presented 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 ASM diskgroup Also notice there is a dedicated switch on the cluster interconnect.

1.3. *Installation Method


This document details one method of installing a 2-node Oracle 10gR2 RAC cluster on Windows: NTFS_RAW_ASM: The Oracle Cluster, ASM & Oracle Database Homes are established on the local 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 up a 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 cover these methods: NTFS_RAW_RAW: The Oracle Cluster, ASM & Oracle Database Homes are established on the local 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 the local disk of each of the RAC nodes. The files required by Oracle Clusterware are on OCFS. The database data-files are also on OCFS. There are other possible combinations although Oracle recommends one of the above methods. 1.2.2. Hardware/software configuration AFTER Oracle software install 3

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 Show all Hide all

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

This installation routine presumes that you have a 2-node Windows cluster. There are a number of items that require checking before the install commences. Getting this bit right will enhance your install experience. 1. User Accounts 2. Installing using Remote desktop client 3. Environment Variables 4. Networking 5. Remote Registry Connect 6. Stopping Services that might impact the installation process 7. Time sync 8. Stage the Oracle Software 9. Run CVU 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 the same on both nodes. If you must use a domain account, then you must ensure that the domain user is explicitly declared as a member of the local Administrators (not granted membership to this group through another group) on each node in the cluster. Not using an administrator account that is explicitly declared by username in the Local administrators group will cause the install to fail Show the User Account setup information Hide the User Account setup information

2. Prepare the cluster nodes for Oracle RAC

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: 1. Open a command prompt and type secpol.msc to launch the Security Policy Console management utility. 2. From the Local Security Settings console tree, click Local Policies, and then Security Options 3. Scroll down to and double-click User Account Control: Behavior of the elevation prompt for administrators. 4. From the drop-down menu, select: Elevate without prompting (tasks requesting elevation will automatically run as elevated without prompting the administrator) 5. Click OK to confirm the changes. 6. Repeat steps 1-5 on ALL cluster nodes. You also must ensure that the Administrators group is listed under Manage auditing and security log: 1. Open a command prompt and type secpol.msc to launch the Security Policy Console management utility. 2. Click on Local Policies 3. Click on User Rights Assignment 4. Locate and double click the Manage auditing and security log in the listing of User Rights Assignments. 5. If the Administrators group is NOT listed in the Local Security Settings tab, add the group now. 6. Click OK to save the changes (if changes were made). 7. Repeat steps 1-6 on ALL cluster nodes.

2.1. User Accounts

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 invoke the mstsc.exe application with the /console parameter which connects to the console session of the specified Windows Server. From the Start-> run menu you must type mstsc /v:nodename /console For more information 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 with MS Terminal Services Client. From the Start-> run menu you must type mstsc /v:nodename /admin For 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 LocalSystem account are set to point at directories that do not contain spaces or other special characters. 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 will fail. Show the Enviroment Variable setup information Hide the Enviroment Variable setup information

2.2. Installing Using Windows Remote Desktop Client

2.4. Networking
You will need a minimum of 2 network adapters per machine, 1 adapter is the public interface. The other adapter, the private interface, is used for Oracle RAC node membership and inter-instance traffic. The private interface adapters should be connected to each other via a network switch which is used exclusively for the interconnect traffic. In 2 node environments do not be tempted to use a 'Crossover Cable' as these are not supported. Recommended best practice is to use more than 2 adapters. This is known as network teaming and is configured before installation of the Oracle software. In basic outline, you take 2 of the adapters on the private interface and team them together to create what looks like a single, highly available adapter for the interconnect traffic. You can then take the remaining 3rd adapter and use it for the public interface. You can also team the public adapters as well. In that case you would need to start with 4 adapters, 2 public & 2 private. Ensure you team the adapters before starting installation. Please be aware that even with a 2-node cluster you must use a dedicated network switch on the interconnect. 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. This address does not require registering in DNS but you should place an entry in the hosts file on each node. This IP Address should be bound to the private adapter before starting the install. It should be a static, not DHCP, address A VIP address, which should be from the same subnet as the public IP address and should be recorded in DNS and the hosts file on each node. This IP Address should NOT be bound to the public adapter before starting the install. Oracle Clusterware is responsible for binding this address. It should be 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 the relevant hosts files that are normally found in the %SystemRoot%\system32\drivers\etc\hosts file. Show Networking setup information Hide Networking setup information You should use ipconfig on each node to confirm the correct IP addresses are bound to the correct adapters C:\Documents and Settings\Administrator>ipconfig Windows IP Configuration Ethernet adapter PublicLAN: Connection-specific DNS Suffix IP Address. . . . . . . . . . . Subnet Mask . . . . . . . . . . Default Gateway . . . . . . . . Ethernet adapter PrivateLAN: Connection-specific DNS Suffix IP Address. . . . . . . . . . . Subnet Mask . . . . . . . . . . Default Gateway . . . . . . . . A sample hosts file
127.0.0.1 10.10.10.11 10.10.10.21 10.10.10.51 localhost winnode1 winnode2 winnode1-vip

. . . .

: : 10.10.10.11 : 255.255.255.0 :

. . . .

: : 192.168.10.11 : 255.255.255.0 :

# Also in DNS if available # Also in DNS if available # Also in DNS if available

2.4. Networking

10.10.10.61 192.168.10.11 192.168.10.21

winnode2-vip winnode1-priv winnode2-priv

# Also in DNS if available

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 should be checked. You should ensure that the public IP addresses resolve correctly and that the private addresses are of 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 return Node2's public IP address Pinging Node1 from Node2 should return Node1's public IP address Pinging Node2 from 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 from Node1 should return Node2's private IP address Pinging Node1 private from Node2 should return Node1's private 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 Clusterware install. If any of the above tests fail you should fix name/address resolution by updating the DNS or local hosts files on 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 Duplex and 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 will normally name the adapters "Local Area Connection" and "Local Area Connection 2". Take the opportunity to rename the adapters on each node at this point. It is important the names used for each class of adapter be consistent 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

As an example, rename the public adapter to PublicLAN and the private adapter to PrivateLAN. It is important that you use the same names on all nodes. If there are other adapters take the opportunity to rename them 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

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 private adapter is listed second. If they are not in this order: select the public adapter and use the up arrow button to the right of the Connections list box to move the public adapter to the top of the list. It is very important to confirm 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 should ensure that this procedure will be successful by testing the net use command On node1 issue the following command: C:\>net use \\winnode2\c$ The command completed successfully. This should return success On 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 when the 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 and right 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 remote node. You should check that this is possible. Whilst the registry editor is still open select the File->Connect Network 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) and click OK

2.5. Remote Registry Connect

14

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

2.5. Remote Registry Connect

15

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.5. Remote Registry Connect

16

2.6. Stopping Services


There can be issues with some of the services, which may already be running on the cluster nodes. Typically a Microsoft Service: Distributed Transaction Coordinator (MSDTC) can interact with Oracle software during install. It is recommended that this service is stopped and set to manual start using services.msc on both nodes. 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 the install, 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 can be achieved using Network Time Server protocol. At the very least you should ensure that the system clocks on 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 versions of the Oracle Software on a 64bit OS A suggested stage for Microsoft Windows 2003 is as follows Oracle 10g Release 2 EE (10.2.0.1) (1 DVD ) C:\stage\10gR2 The latest patch set 10.2.0.4 The latest mini patch : currently patch 34 A suggested stage for Microsoft Windows 2008 is as follows Oracle Database 10g Release 2 (10.2.0.4.0) Enterprise/Standard Edition for Microsoft Windows Vista x64 and Microsoft Windows Server 2008 x64 The latest mini patch : currently patch 34 If you download the software from OTN you will not get the integrated installer. You will have separate downloads for : 2.7. Time Sync 18

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 the installation media Show CVU output Hide CVU output Z:\Disk1>runcluvfy stage -post hwos -n winnode1,winnode2 -verbose
1 file(s) copied. C:\WINDOWS\temp\cvtmphome\oui\lib\win32\msvcp71.dll C:\WINDOWS\temp\cvtmphome\oui\lib\win32\msvcr71.dll 2 file(s) copied. Performing post-checks for hardware and operating system setup Checking node reachability... Check: Node reachability from node "winnode1" Destination Node Reachable? ------------------------------------ -----------------------winnode1 yes winnode2 yes Result: Node reachability check passed from node "winnode1". Checking user equivalence... Check: User equivalence for user "Administrator" Node Name Comment ------------------------------------ -----------------------winnode2 passed winnode1 passed Result: 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 Interface information for node "winnode1" Interface Name IP Address Subnet Subnet Gateway Default Gateway Hardware Address ---------------- ------------ ------------ ------------ ------------ -----------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 Check: Node connectivity of subnet "10.10.10.0" Source Destination -----------------------------winnode2:PublicLAN -----------------------------winnode1:PublicLAN

Connected? ---------------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 ------------------------------ -----------------------------winnode2:PrivateLAN winnode1:PrivateLAN

Connected? ---------------yes

Result: 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: Could not find a suitable set of interfaces for the private interconnect. Result: Node connectivity check passed.

2.8. Stage the Oracle Software

19

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 check the shared-ness of iSCSI disks. Also it could not automatically determine the distinct public and private network 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 1. Shared Disk Layout 2. Enable Automounting of disks 3. Clean the Shared Disks - Optional Step 4. Create Logical partitions inside Extended partitions 5. Drive Letters 6. View Disks

3.1. Shared Disk Layout


It is assumed that the two nodes have local disk primarily for the operating system and the local Oracle Homes. Labelled C: The Oracle Clusterware software also resides on the local disks on each node. The 2 nodes must also share some central disks. 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 protection then Oracle recommends that you use the built-in mirroring/redundancy capabilities provided by Oracle Clusterware for the required Clusterware RAW partitions Two for the Oracle Cluster Registry (OCR) Three for the vote devices All of these partitions should be a minimum of 256MB each. Because of space used by extended and logical partitions it is recommended that these LUNs be a minimum of 270MB. If you choose to use Oracle mirroring you 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 has provisioned 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 logical drives inside of extended partitions for the disks to be used by Oracle Clusterware and Oracle ASM. There must be no drive letters assigned to any of the Disks1 Disk14 on any node. For MIcrosoft Windows 2003 it is possible to use diskmgmt.msc instead of diskpart (as used in the following sections) to create these partitions. For Microsoft Windows 2008, diskmgmt.msc cannot be used instead of diskpart to create these partitions.

3.2. Enable Automount


You must enable automounting of disks for them to be visible to Oracle Clusterware. On each node log in as a user with explicit Administrator privileges then Click START->RUN and type diskpart C:\>diskpart Microsoft DiskPart version 5.2.3790.3959 Copyright (C) 1999-2001 Microsoft Corporation. On computer: WINNODE1 DISKPART>AUTOMOUNT ENABLE Repeat 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 any previous failed install. Please see a later Appendix for coping with failed installs. On Node1 from within diskpart you should clean each of the disks. WARNING: this will destroy all of the data on the disk. Do not select the disk containing the operating system or you will have to reinstall the OS. Cleaning 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 MB Now you should clean disks 1 14 (Not disk0 as this is the local C: drive) DISKPART>select disk 1 Disk 1 is now the selected disk. DISKPART> clean all DISKPART> select disk 2 Disk 2 is now the selected disk. DISKPART> clean all DISKPART> select disk 3 Disk 3 is now the selected disk. DISKPART> clean all DISKPART> select disk 4 Disk 4 is now the selected disk. DISKPART> clean all DISKPART> select disk 5 Disk 5 is now the selected disk. DISKPART> clean all DISKPART> select disk 6 Disk 6 is now the selected disk. DISKPART> clean all DISKPART> select disk 7 Disk 7 is now the selected disk. 3.3. Clean the Shared Disks - Optional Step 22

DISKPART> clean all DISKPART> select disk 8 Disk 8 is now the selected disk. DISKPART> clean all DISKPART> select disk 9 Disk 9 is now the selected disk. DISKPART> clean all DISKPART> select disk 10 Disk 10 is now the selected disk. DISKPART> clean all DISKPART> select disk 11 Disk 11 is now the selected disk. DISKPART> clean all DISKPART> select disk 12 Disk 12 is now the selected disk. DISKPART> clean all DISKPART> select disk 13 Disk 13 is now the selected disk. DISKPART> clean all DISKPART> select disk 14 Disk 14 is now the selected disk. 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 then a logical partition inside that partition. In the following example, for Oracle Clusterware, we have dedicated LUNS for each device. This is not strictly necessary, you can combine an OCR & vote device onto one physical LUN, creating 2 partitions inside the extended partition although it would be foolish for example to place the OCR and OCRMIRROR devices on the same LUN. DISKPART> select disk 1 Disk 1 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition. DISKPART> select disk 2 Disk 2 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition. DISKPART> select disk 3 Disk 3 is now the selected disk. 3.4. Create Logical partitions inside Extended partitions 23

DISKPART> create part DiskPart succeeded in DISKPART> create part DiskPart succeeded in

ext creating the specified partition. log creating the specified partition..

DISKPART> select disk 4 Disk 4 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition. DISKPART> select disk 5 Disk 5 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition. DISKPART> select disk 6 Disk 6 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition. DISKPART> select disk 7 Disk 7 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition. DISKPART> select disk 8 Disk 8 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition. DISKPART> select disk 9 Disk 9 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition. DISKPART> select disk 10 Disk 10 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart 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 ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition. DISKPART> select disk 12 Disk 12 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition. DISKPART> select disk 13 Disk 13 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition. DISKPART> select disk 14 Disk 14 is now the selected disk. DISKPART> create part ext DiskPart succeeded in creating the specified partition. DISKPART> create part log DiskPart succeeded in creating the specified partition.

3.4.1. View Created partitions


DISKPART> list disk Disk ### -------Disk 0 Disk 1 Disk 2 Disk 3 Disk 4 Disk 5 Disk 6 Disk 7 Disk 8 Disk 9 Disk 10 Disk 11 Disk 12 Disk 13 * Disk 14 Status ---------Online Online Online Online Online Online Online Online Online Online Online Online Online Online Online Size ------8189 MB 290 MB 290 MB 290 MB 290 MB 290 MB 1271 MB 1271 MB 1271 MB 1271 MB 1271 MB 1271 MB 1271 MB 1271 MB 1271 MB Free ------8033 KB 0 B 0 B 0 B 0 B 0 B 0 B 0 B 0 B 0 B 0 B 0 B 0 B 0 B 0 B Dyn --Gpt ---

3.5. List Drive Letters


Diskpart should not add drive letters to the partitions on the local node. The partitions on the other node may have 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 2008 do not suffer from this issue.

3.4.1. View Created partitions

25

Using diskpart on Node2


DISKPART>

list volume
Ltr --H J O M D L K C E N G F I P Q R Label ----------Fs ----RAW RAW RAW RAW RAW RAW NTFS RAW RAW RAW RAW RAW RAW RAW RAW Type ---------Partition Partition Partition Partition DVD-ROM Partition Partition Partition Partition Partition Partition Partition Partition Partition Partition Partition Size ------290 MB 1271 MB 1271 MB 1271 MB 0 B 1271 MB 1271 MB 8182 MB 290 MB 1271 MB 290 MB 290 MB 290 MB 1271 MB 1271 MB 1271 MB Status --------Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Info --------

Volume ### ---------Volume 0 Volume 1 Volume 2 Volume 3 Volume 4 Volume 5 Volume 6 Volume 7 Volume 8 Volume 9 Volume 10 Volume 11 Volume 12 Volume 13 Volume 14 Volume 15

System

Notice 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 10 11 12 13 14 15 Do NOT remove drive letters C & D which, in this case, are local disks (and CD-ROM drive) These relate to volumes 7 & 4 (In this example) DISKPART> select volume 0 Volume 0 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 1 Volume 1 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 2 Volume 2 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 3 Volume 3 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 5 Volume 5 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 6 Volume 6 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. 3.5. List Drive Letters 26

DISKPART> select volume 8 Volume 8 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 9 Volume 9 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 10 Volume 10 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 11 Volume 11 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 12 Volume 12 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 13 Volume 13 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 14 Volume 14 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point. DISKPART> select volume 15 Volume 15 is the selected volume. DISKPART> remov DiskPart successfully removed the drive letter or mount point.

3.5.2. List volumes on Second node


Check that none of the RAW partitions have drive letters assigned
DISKPART>

list vol
Ltr --Label ----------Fs ----RAW RAW RAW RAW RAW RAW NTFS RAW RAW RAW Type ---------Partition Partition Partition Partition DVD-ROM Partition Partition Partition Partition Partition Partition Size ------290 MB 1271 MB 1271 MB 1271 MB 0 B 1271 MB 1271 MB 8182 MB 290 MB 1271 MB 290 MB Status --------Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Healthy Info --------

Volume ### ---------Volume 0 Volume 1 Volume 2 Volume 3 Volume 4 Volume 5 Volume 6 Volume 7 Volume 8 Volume 9 Volume 10

System

3.5.1. Remove Drive Letters

27

Volume Volume Volume Volume * Volume

11 12 13 14 15

RAW RAW RAW RAW RAW

Partition Partition Partition Partition Partition

290 290 1271 1271 1271

MB MB MB MB MB

Healthy Healthy Healthy Healthy Healthy

You 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 Show all Hide all

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

Next we will install the Oracle Clusterware layer. Oracle Clusterware is an essential component of the Oracle RAC database infrastructure. Oracle Clusterware does not require any other clustering software. There is no need 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 3.5.2. List volumes on Second node 28

The Virtual Public IP names and IP addresses for the nodes to be used by the cluster

4.1. CVU Pre Oracle Clusterware install check


Before starting the Oracle Clusterware install it is prudent to complete a Cluster Verification Utility (CVU) check for this stage.
Z:\Disk1>runcluvfy.bat

stage -pre crsinst -n winnode1,winnode2 -r 10gR2 -verbose

Show CVU output

Hide CVU output

1 file(s) copied. C:\WINDOWS\temp\cvtmphome\oui\lib\win32\msvcp71.dll C:\WINDOWS\temp\cvtmphome\oui\lib\win32\msvcr71.dll 2 file(s) copied. Performing pre-checks for cluster services setup Checking node reachability... Check: Node reachability from node "winnode1" Destination Node Reachable? ------------------------------------ -----------------------winnode1 yes winnode2 yes Result: Node reachability check passed from node "winnode1".

Checking user equivalence... Check: User equivalence for user "Administrator" Node Name Comment ------------------------------------ -----------------------winnode2 passed winnode1 passed Result: User equivalence check passed for user "Administrator". Checking administrative privileges... Administrative privileges check passed. Checking node connectivity...

Interface information for node "winnode2" Interface Name IP Address Subnet ---------------- ------------ -----------PublicLAN 10.10.10.21 10.10.10.0 PrivateLAN 192.168.10.21 192.168.10.0 Interface information for node "winnode1" Interface Name IP Address Subnet ---------------- ------------ -----------PublicLAN 10.10.10.11 10.10.10.0 PrivateLAN 192.168.10.11 192.168.10.0

Subnet Gateway Default Gateway Hardware Address ------------ ------------ -----------10.10.10.21 192.168.1.254 00:0C:29:E3:82:6C 192.168.10.21 192.168.1.254 00:0C:29:E3:82:76

Subnet Gateway Default Gateway Hardware Address ------------ ------------ -----------10.10.10.11 192.168.1.254 00:0C:29:E3:81:6C 192.168.10.11 192.168.1.254 00:0C:29:E3:81:76

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 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.

4. Oracle Clusterware Installation and Configuration

29

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 system requirements for 'crs'... Check: Operating system version Node Name Available Required ------------ ------------------------ -----------------------winnode2 Windows Server 2003 Windows Server 2003 winnode1 Windows Server 2003 Windows Server 2003 Result: Operating system version check passed. Check: Total memory Node Name Available ------------ -----------------------winnode2 1.63GB (1707464KB) winnode1 1.63GB (1707464KB) Result: Total memory check passed. Check: Swap space Node Name Available ------------ -----------------------winnode2 2.99GB (3131544KB) winnode1 2.99GB (3131544KB) Result: Swap space check passed. Check: System architecture Node Name Available ------------ -----------------------winnode2 32-bit winnode1 32-bit Result: System architecture check passed.

Comment ---------passed passed

Required -----------------------512MB (524288KB) 512MB (524288KB)

Comment ---------passed passed

Required -----------------------1GB (1048576KB) 1GB (1048576KB)

Comment ---------passed passed

Required -----------------------32-bit 32-bit

Comment ---------passed passed

Check: Free disk space in "C:\WINDOWS\TEMP" dir Node Name Available Required ------------ ------------------------ -----------------------winnode2 4.91GB (5150352KB) 400MB (409600KB) winnode1 4.7GB (4924284KB) 400MB (409600KB) Result: Free disk space check passed. System requirement passed for 'crs' Pre-check for cluster services setup was successful.

Comment ---------passed passed

4.2. Oracle Clusterware Install


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

4.1. CVU Pre Oracle Clusterware install check

30

Action Click Next

4.2. Oracle Clusterware Install

31

Notes The OUI will name the Oracle Clusterware Home 'OraCr10g_home'. If you change this you should 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 will use the path :\oracle\product\10.2.0\crs. If you change the drive you should make sure that there is enough free space on the selected drive on all the nodes for the home (which is currently some 600MB). As clusterware runs it will also create various log files inside the Clusterware Home. Actions If the defaults are not acceptable modify them Click Next

4.2. Oracle Clusterware Install

32

Notes The installer will validate the state of the cluster before continuing. If there are issues you should rectify them before continuing. Actions Click Next

4.2. Oracle Clusterware Install

33

Notes Each Cluster requires a name, this should be unique within your organization, The default is 'crs' you should change this to be unique within your organization This is where you specify details of all the nodes in the cluster. The installer will default names for the node it is running on. You must add other nodes manually. Oracle defaults the names to 'nodename', 'nodename-priv', 'nodename-vip' be sure to modify these names if needed using the 'Edit...' button Actions Enter a unique cluster name 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 and must be live Private Node Name : must resolve via hosts to the interconnect IP address and must be live Virtual Host Name : must resolve via hosts and or DNS to a new IP address and must not 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

4.2. Oracle Clusterware Install

34

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 and must be live Private Node Name : must resolve via hosts to the interconnect IP address and must be live Virtual Host Name : must resolve via hosts and or DNS to a new IP address and must not be live Click OK to return to the node list for the cluster

4.2. Oracle Clusterware Install

35

Notes If you have more nodes repeat the Add... cycle Actions Click Next

4.2. Oracle Clusterware Install

36

Notes The installer lists all the Network adapters. You should have one Adapter correctly identified as type 'Public' and at least one adapter correctly identified as type 'Private'. The installer will try and guess the use of an adapter based on the IP address bound. If it guesses incorrectly you must change the usage. Here it has guessed that all adapters are Private, which is incorrect. Actions Select the Adapter PublicLAN Click Edit...

4.2. Oracle Clusterware Install

37

Notes Here you specify the Interface type Oracle will use this specific network for Actions Select the Interface Type : Public radio button Click OK

4.2. Oracle Clusterware Install

38

Notes Here we specify the shared storage devices that will be used by Oracle Clusterware. Ideally you will have 2 devices for the OCR, Oracle will mirror to these devices to protect you from a single OCR device failure. Also you will have a total of 3 vote devices to protect your cluster 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 a previous failed install and have not cleaned up correctly - see My Oracle Support Note:341214.1 : How To clean up after a Failed (or successful) Oracle Clusterware Installation on Windows for how to clean up a failed install. Actions Select the device to be used for the First OCR Click Edit...

4.2. Oracle Clusterware Install

39

Notes Here we specify the usage for the selected device Actions Select the Place OCR (Primary) on this partition checkbox Click OK

4.2. Oracle Clusterware Install

40

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...

4.2. Oracle Clusterware Install

41

Notes Here we specify the usage for the selected device Actions Select the Place OCR (Mirror) on this partition checkbox Click OK

4.2. Oracle Clusterware Install

42

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...

4.2. Oracle Clusterware Install

43

Notes Here we specify the usage for the selected device Actions Select the Place Voting Disk on this Partition checkbox Click OK

4.2. Oracle Clusterware Install

44

Notes Continue with the second vote device Actions Select the device to be used for the Second vote device Click Edit...

4.2. Oracle Clusterware Install

45

Notes Here we specify the usage for the selected device Actions Select the Place Voting Disk on this Partition checkbox Click OK

4.2. Oracle Clusterware Install

46

Notes Continue with the third vote device Actions Select the device to be used for the third vote device Click Edit...

4.2. Oracle Clusterware Install

47

Notes Here we specify the usage for the selected device Actions Select the Place Voting Disk on this Partition checkbox Click OK

4.2. Oracle Clusterware Install

48

Notes Now you can see that we have 2 OCR devices and 3 vote devices Actions Click Next

4.2. Oracle Clusterware Install

49

Notes the installer lists a summary of the planned actions Actions Click Install

4.2. Oracle Clusterware Install

50

Notes the installer installs the software onto the local node Actions none required

4.2. Oracle Clusterware Install

51

Notes a series of configuration assistants are run at the end of the install Actions none required

4.2. Oracle Clusterware Install

52

Notes the VIP Configuration assistant will fail if the public IP address is not from within a routable range - we can fix this later. Actions Click OK

4.2. Oracle Clusterware Install

53

Notes here you can see that the installer shows the status canceled for the VIP Configuration Assistant Actions Click Cancel

4.2. Oracle Clusterware Install

54

Notes The OUI detects that not all the assistants completed successfully Actions Click OK

4.2. Oracle Clusterware Install

55

Notes The installer has completed installation and configuration of Oracle Clusterware Actions Click Exit

4.2. Oracle Clusterware Install

56

Actions Click Yes

4.2.1. Run the VIP Configuration Assistant manually to configure the VIPs

4.2.1. Run the VIP Configuration Assistant manually to configure the VIPs

57

Notes here we need to run the vip configuration assistant manually Actions Select the Start->Run button Enter the full path to the vipca.bat file Click OK

4.2.1. Run the VIP Configuration Assistant manually to configure the VIPs

58

Notes The VIP Configuration Assistant appears Actions Click Next

4.2.1. Run the VIP Configuration Assistant manually to configure the VIPs

59

Notes Here we identify which adapter will host the Virtual IP Actions Select the PublicLAN? Adapter Click Next

4.2.1. Run the VIP Configuration Assistant manually to configure the VIPs

60

Notes here we enter the IP Alias names for the virtual IP Addresses * Take care here to manually enter both the IP Alias names Actions Enter the Alias name for the first node in the cluster Enter the Alias name for the second node in the cluster - repeat for all nodes in the cluster if you have more than 2 Click Next

4.2.1. Run the VIP Configuration Assistant manually to configure the VIPs

61

Notes here you can see a summary of the VIP Configuration Actions Click Finish

4.2.1. Run the VIP Configuration Assistant manually to configure the VIPs

62

Notes The VIP, GSD, and ONS resources get configured inside Oracle Clusterware Actions none required

4.2.1. Run the VIP Configuration Assistant manually to configure the VIPs

63

Notes The Configuration is complete Actions Click Exit

4.2.2. Oracle Clusterware has been installed and configured correctly

5. Oracle Clusterware patching


Before continuing with the install you should patch the Oracle Clusterware Home to the latest release. You use the same patchset for Oracle Clusterware, ASM and Database Homes. The Clusterware Home should have the highest or equal release level to the other 2 homes. For Microsoft Windows 2003, the current major patchset is 10.2.0.4 - available as part of patch 6810189 For Microsoft Windows 2008, 10.2.0.4 patchset fixes have been included in the Oracle Clusterware installation. 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 mini patch. The current mini patch is Patch 34 - available for x64 Windows as part of patch 9393550 So we need to : Apply the latest major patchset (only for Microsoft Windows 2003) Apply the latest mini patch

4.2.2. Oracle Clusterware has been installed and configured correctly

64

First you can query the software and active versions of Oracle Clusterware D:\oracle\product\10.2.0\crs\BIN>crsctl query crs softwareversion CRS software version on node [winnode1] is [10.2.0.1.0] D:\oracle\product\10.2.0\crs\BIN>crsctl query crs activeversion CRS active version on the cluster is [10.2.0.1.0] here you can see that the software version = active version = 10.2.0.1

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 rolling fashion. 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 patch102.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.

5. Oracle Clusterware patching

65

Notes 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

66

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

5.1.1. Install the patch software

67

Notes Some parameters are validated by the installer Actions Click Next

5.1.1. Install the patch software

68

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

5.1.1. Install the patch software

69

Notes the installer stages the patch on all the nodes in the cluster Actions No action required

5.1.1. Install the patch software

70

Notes At the end of the install the installer lists the mandatory steps that must be completed to apply this 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

71

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 you complete the following

5.1.3. Stop any other Clusterware processes

72

Notes Using Windows task Manager - you should locate the ons.exe processes Actions No Action Required

5.1.3. Stop any other Clusterware processes

73

Notes You should kill both the ons processes Actions Right Click on each process and select End Process

5.1.4. run the patch102.bat file


You can check the versions of Oracle Clusterware software D:\oracle\product\10.2.0\crs\BIN>crsctl query crs softwareversion CRS software version on node [winnode1] is [10.2.0.1.0] D:\oracle\product\10.2.0\crs\BIN>crsctl query crs activeversion CRS active version on the cluster is [10.2.0.1.0] As you can see the versions are still showing as the base release. Next, run the patch102.bat file - this will upgrade the software on the current node and will restart the Oracle Clusterware processes. D:\>cd \oracle\product\10.2.0\crs\install D:\oracle\product\10.2.0\crs\install>patch102.bat
Successful validation check of Oracle CRS services status Successful binary patch of the D:\oracle\product\10.2.0\crs Successful cleanup of patch subdirectory D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\bin\cluvfy.bat -> D:\oracle\product\10.2.0\crs\inventory\Templates\bin\cluvfy.bat D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\bin\gsd.bat -> D:\oracle\product\10.2.0\crs\inventory\Templates\bin\gsd.bat D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\bin\gsdctl.bat -> D:\oracle\product\10.2.0\crs\inventory\Templates\bin\gsdctl.bat D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\bin\gsdstop.bat -> D:\oracle\product\10.2.0\crs\inventory\Templates\bin\gsdstop.bat D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\bin\instOracle.key -> D:\oracle\product\10.2.0\crs\inventory\Templates\bin\instOracle.key D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\bin\localconfig.bat -> D:\oracle\product\10.2.0\crs\inventory\Templates\bin\localconfig.bat D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\bin\racgwrap.bat.sbs -> D:\oracle\product\10.2.0\crs\inventory\Templates\bin\racgwrap.bat.sbs D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\bin\srvctl.bat -> D:\oracle\product\10.2.0\crs\inventory\Templates\bin\srvctl.bat D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\bin\usrvip.bat -> D:\oracle\product\10.2.0\crs\inventory\Templates\bin\usrvip.bat D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\bin\vipca.bat-> D:\oracle\product\10.2.0\crs\inventory\Templates\bin\vipca.bat

5.1.4. run the patch102.bat file

74

D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\cv\remenv\exectask.bat -> D:\oracle\product\10.2.0\crs\inventory\Templates\cv\remenv\exectask.bat D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\evm\admin\conf\evm.auth -> D:\oracle\product\10.2.0\crs\inventory\Templates\evm\admin\conf\evm.auth D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\evm\admin\conf\evmdaemon.conf -> D:\oracle\product\10.2.0\crs\inventory\Templates\evm\admin\conf\evmdaemon.conf D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\evm\admin\conf\evmlogger.conf -> D:\oracle\product\10.2.0\crs\inventory\Templates\evm\admin\conf\evmlogger.conf D:\oracle\product\10.2.0\crs\inventory\Templates\install\patch102\install\preupdate.bat -> D:\oracle\product\10.2.0\crs\inventory\Templates\install\preupdate.bat 15 File(s) copied Successful startup of OracleCSService Successful startup of OracleEvmService Successful startup of OracleCRService Setting up OPMD process OpmdInstall: OPM service successfully installed OpmdFixupService: Oracle Object Service set to manual startup and added to list OpmdFixupService: OracleCSService set to manual startup and added to list OpmdFixupService: OracleEVMService set to manual startup and added to list OpmdFixupService: OracleCRService set to manual startup and added to list clscfg: EXISTING configuration version 3 detected. clscfg: version 3 is 10G Release 2. 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 winnode1 Creating OCR keys for user 'administrator', privgrp ''.. Operation successful. clscfg -upgrade completed successfully Successful upgrade of this node to Oracle Cluster Ready Services 10204

Once again you can check the Oracle Clusterware software levels D:\oracle\product\10.2.0\crs\BIN>crsctl query crs softwareversion CRS software version on node [winnode1] is [10.2.0.4.0] D:\oracle\product\10.2.0\crs\BIN>crsctl query crs activeversion CRS active version on the cluster is [10.2.0.1.0] As you can see the software version is now 10.2.0.4 however the active version is still 10.2.0.1. This means that the new software is in place on this node but is not yet active. It becomes active when the patch102.bat file completes on the last node in the cluster

5.1.5. repeat on the other nodes in the cluster


Stop the Clusterware software on the second node Stop any other Clusterware processes run the patch102.bat file on the second node After completing the patch upgrade on the last node you should check the software and active versions: D:\oracle\product\10.2.0\crs\BIN>crsctl query crs softwareversion CRS software version on node [winnode1] is [10.2.0.4.0] D:\oracle\product\10.2.0\crs\BIN>crsctl query crs activeversion CRS active version on the cluster is [10.2.0.4.0] As you can see the new 10.2.0.4 version is now active.

5.1.6. Application of the Oracle Clusterware major patchset is complete

5.2. Mini Patch


You should now apply the latest mini patch to the clusterware home in accordance with the instructions provided in the README for that patch

6. Oracle ASM Home Software Install


In this section we establish the Oracle software for the ASM home.

5.1.5. repeat on the other nodes in the cluster

75

6.1. CVU check 6.2. Oracle ASM Home Software Install


You must launch the installer by running setup.exe from the staged installation software.

Notes Here we will create an ASM Software home on all the nodes in the cluster Actions Click Next

6.1. CVU check

76

Notes Here we can choose the type of database software to be installed Actions Select the Enterprise Edition radio button Click Next

6.2. Oracle ASM Home Software Install

77

Notes This is where you specify the location of the ASM software home. Modify the Home name and Home Path to include the word ASM. This makes it easier to identify later on. If you change the path you should ensure that you do not use the exact same path as the Oracle Clusterware home. Actions Confirm entries are OK Click Next

6.2. Oracle ASM Home Software Install

78

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

6.2. Oracle ASM Home Software Install

79

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

6.2. Oracle ASM Home Software Install

80

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

6.2. Oracle ASM Home Software Install

81

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

6.2. Oracle ASM Home Software Install

82

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

6.2. Oracle ASM Home Software Install

83

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

6.2. Oracle ASM Home Software Install

84

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 Microsoft Windows 2003, the current major patchset is 10.2.0.4 - available as part of patch 6810189. Use the same staged patch as you used for the Oracle Clusterware Home. For Microsoft Windows 2008, 10.2.0.4 patchset fixes have been included in the Oracle Clusterware installation. No patchset needs to be applied for Microsoft Windows 2008. Apply the latest mini patch For both Microsoft Windows 2003 and Microsoft Windows 2008, you should apply the latest available mini patch. The current mini patch is Patch 34 - available for x64 Windows as part of patch 9393550

6.2.1. Oracle ASM software home has been installed

85

7.1. Apply the latest Major patchset


Start the installer by running setup.exe from the root of the patch directory on one of the nodes in the cluster.

Notes the Universal Installer screen appears Actions Click Next

7.1. Apply the latest Major patchset

86

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

7.1. Apply the latest Major patchset

87

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

7.1. Apply the latest Major patchset

88

Notes Some parameters are validated by the installer Actions Click Next

7.1. Apply the latest Major patchset

89

Notes Here you can setup the Oracle Configuration Manager Actions Click Next

7.1. Apply the latest Major patchset

90

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

7.1. Apply the latest Major patchset

91

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

7.1. Apply the latest Major patchset

92

Notes The installation is complete Actions Click Exit

7.1. Apply the latest Major patchset

93

Notes Are you sure Actions Click Yes

7.2. Apply the latest Mini patch


Next you should apply the latest mini patch in accordance with the instructions provided in the README for that patch

7.3. The ASM home is patched successfully.

8. Oracle RAC Database Listener Creation


8.1. Create Node specific network listeners
The Oracle network listeners traditionally run from the ASM home. Here we are going to create the listeners using Net Configuration Assistant (NETCA) from the ASM home.

7.2. Apply the latest Mini patch

94

Notes You must use the NETCA from the ASM home to create the listeners Actions From the start menu select Oracle - OraDb10g_home1->Configuration and Migration Tools -> Net Configuration Assistant

8.1. Create Node specific network listeners

95

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

8.1. Create Node specific network listeners

96

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

8.1. Create Node specific network listeners

97

Notes You get various options we need to configure listeners Actions Select the Listener configuration radio button Click Next

8.1. Create Node specific network listeners

98

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

8.1. Create Node specific network listeners

99

Notes Here you get the opportunity to name the listener Do not change this. The listeners will automatically be called LISTENER_nodename1 & LISTENER_nodename2. This is important for RAC. Actions Click Next

8.1. Create Node specific network listeners

100

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

8.1. Create Node specific network listeners

101

Notes It is possible to choose a non-default Port this is not recommended Actions Ensure the Use the 'Standard port number of 1521' radio button is set Click Next

8.1. Create Node specific network listeners

102

Notes After configuring the node listeners you get the opportunity to configure additional listeners Actions Select the 'No' radio button Click Next

8.1. Create Node specific network listeners

103

Notes The Listeners are configured on all nodes Actions Click Finish

8.2. Completed Node specific network listeners creation


You have now completed the RAC cluster nodes Network listener configuration. A new managed resource will have been added to Oracle Clusterware Registry file (OCR) for each listener.

9. Oracle ASM Instance and diskgroup Creation


9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

8.2. Completed Node specific network listeners creation

104

Notes We use the DBCA from the ASM install to create the ASM instances Actions From the start menu select Oracle - OraASM10g_home1->Configuration and Migration Tools -> Database Configuration Assistant

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

105

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

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

106

Notes We use DBCA to create RAC databases and ASM instances Actions Select the 'Configure Automatic Storage Management' radio button Click Next

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

107

Notes You need to make sure you create ASM instances on all the cluster nodes Actions Click Select All Click Next

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

108

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 Select 'Create initialization parameter file (IFILE)' Click Next

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

109

Notes dbca will create and start ASM instances Actions Click OK

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

110

Notes This should take a few seconds Actions no action

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

111

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

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

112

Notes At the moment no disks are visible They must be stamped before they appear in the Member disk list. Actions Click 'Stamp Disks'

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

113

Notes DBCA will use asmtool to stamp the disks Actions Select the 'Add or change label' radio button Click Next

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

114

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 devices for ASM usage. We are going to use the first 6 disks for the +DATA diskgroup Actions Select the first 6 disks Check the 'generate stamps with this prefix' checkbox Enter a prefix of DATA Click Next

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

115

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

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

116

Notes A final confirmation screen Actions Click Finish

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

117

Notes The stamped disks are now visible. We need to stamp the remaining disks for the +FLASH diskgroup Actions Click 'Stamp Disks'

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

118

Notes Here we go through basically the same steps once more Actions Select the Add or change label radio button Click Next

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

119

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 of FLASH Click Next

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

120

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

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

121

Notes A final confirmation screen Actions Click Finish

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

122

Notes Now we will assign disks to specific diskgroups and create the DATA diskgroup Actions For the Disk Group Name enter DATA Select the 'External Redundancy' radio button Select the 'Show Candidates' radio button Select the first 6 disks, the ones that were stamped \\.\ORCLDISKDATAn Click OK

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

123

Notes A progress message this should not take very long Actions none

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

124

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

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

125

Notes Now we will assign disks to specific diskgroups and create the FLASH diskgroup For a change we will create this diskgroup with Normal redundancy Actions For the Disk Group Name enter FLASH Select the 'Normal' radio button Select the 'Show Candidates' radio button Select the remaining 3 disks, the ones that were stamped \\.\ORCLDISKFLASHn Click OK

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

126

Notes A progress message this should not take very long Actions none

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

127

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

9.1. Create ASM Instance and add the +DATA and +FLASH diskgroups

128

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 have installed ASM, Network listeners and created 2 ASM diskgroups.

10. Oracle RAC Database Home Software Install


10.1. CVU check 10.2. Oracle RAC Database Home Software Install
You must launch the installer by running setup.exe from the staged installation software. In this section we establish the Oracle software for the RAC Database home.

9.2. Completed creation of ASM Instance and add of the +DATA and +FLASH diskgroups

129

Notes Here we will create a RAC Database Software home on all the nodes in the cluster Actions Click Next

10.2. Oracle RAC Database Home Software Install

130

Notes Here we can choose the type of database software to be installed Actions Select the 'Enterprise Edition' radio button Click Next

10.2. Oracle RAC Database Home Software Install

131

Notes This is where you specify the location of the RAC Database software home. If you change the path you should ensure that you do not use the exact same path as the Oracle Clusterware home or the ASM Home. Actions Confirm entries are OK Click Next

10.2. Oracle RAC Database Home Software Install

132

Notes The installer has detected the presence of Oracle Clusterware and uses this to populate this dialog box. To build a cluster which includes all nodes you must ensure that that you check the checkboxes next to the node names. Actions Click Select All Click Next

10.2. Oracle RAC Database Home Software Install

133

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

10.2. Oracle RAC Database Home Software Install

134

Notes The installer detects you already have a Database home installed Actions ensure the 'No' radio button is selected Click Next

10.2. Oracle RAC Database Home Software Install

135

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

10.2. Oracle RAC Database Home Software Install

136

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

10.2. Oracle RAC Database Home Software Install

137

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

10.2. Oracle RAC Database Home Software Install

138

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

10.2. Oracle RAC Database Home Software Install

139

Notes Are you sure ? Actions Click Yes

10.2.1. Oracle RAC Database software home has been installed

11. Oracle RAC 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 Microsoft Windows 2003, the current major patchset is 10.2.0.4 - available as part of patch 6810189. Use the same staged patch as you used for the Oracle Clusterware Home. For Microsoft Windows 2008, 10.2.0.4 patchset fixes have been included in the Oracle Clusterware installation. No patchset needs to be applied for Microsoft Windows 2008. Apply the latest mini patch For both Microsoft Windows 2003 and Microsoft Windows 2008, you should apply the latest available mini patch. The current mini patch is Patch 34 - available for x64 Windows as part of patch 9393550

10.2.1. Oracle RAC Database software home has been installed

140

11.1. Apply the latest Major patchset


Start the installer by running setup.exe from the root of the patch directory on one of the nodes in the cluster

Notes the Universal Installer screen appears Actions Click Next

11.1. Apply the latest Major patchset

141

Notes You are patching the RAC Database home. Make sure this is selected in the drop down list box. Actions Select the RAC Database home in the drop down list box Click Next

11.1. Apply the latest Major patchset

142

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

11.1. Apply the latest Major patchset

143

Notes Some parameters are validated by the installer Actions Click Next

11.1. Apply the latest Major patchset

144

Notes Here you can setup the Oracle Configuration Manager Actions Click Next

11.1. Apply the latest Major patchset

145

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

11.1. Apply the latest Major patchset

146

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

11.1. Apply the latest Major patchset

147

Notes The installation is complete Actions Click Exit

11.1. Apply the latest Major patchset

148

Notes Are you sure? Actions Click Yes

11.2. Apply the latest Mini patch


Next you should apply the latest mini patch in accordance with the instructions provided in the README for that patch

11.3. The RAC Database home is patched successfully.

12. Oracle RAC Database Creation


12.1. use DBCA to create the RAC database

11.2. Apply the latest Mini patch

149

Notes You must use the DBCA from the RAC database home not the ASM home

12.1. use DBCA to create the RAC database

150

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

12.1. use DBCA to create the RAC database

151

Notes We use DBCA to create RAC databases Actions Select the 'Create a Database' radio button Click Next

12.1. use DBCA to create the RAC database

152

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

12.1. use DBCA to create the RAC database

153

Notes Here you get to select the type of database Actions Select the 'General Purpose' radio button Click Next

12.1. use DBCA to create the RAC database

154

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

12.1. use DBCA to create the RAC database

155

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

12.1. use DBCA to create the RAC database

156

Notes Here we specify the password for the Oracle Database users. In this example we are setting the same 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 same password for the Confirm password Click Next

12.1. use DBCA to create the RAC database

157

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

12.1. use DBCA to create the RAC database

158

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

12.1. use DBCA to create the RAC database

159

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

12.1. use DBCA to create the RAC database

160

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 Set the flash recovery size remember the size of the +FLASH diskgroup Check the 'Enable Archiving' checkbox Click Next

12.1. use DBCA to create the RAC database

161

Notes Here you can choose to add the Oracle Sample schemas Actions Check the 'Sample schemas' checkbox Click Next

12.1. use DBCA to create the RAC database

162

Notes Here you can choose to create additional database Services Actions Click Next

12.1. use DBCA to create the RAC database

163

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

12.1. use DBCA to create the RAC database

164

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

12.1. use DBCA to create the RAC database

165

Notes You can decide to generate database creation scripts Actions Check the Create Database checkbox Click Next

12.1. use DBCA to create the RAC database

166

Notes A summary screen Actions Click Next

12.1. use DBCA to create the RAC database

167

Notes The database is created Actions none

12.1. use DBCA to create the RAC database

168

Notes After the database is created the summary screen is displayed note the URL provided for Database Control Actions Click Exit

12.1. use DBCA to create the RAC database

169

Notes The Database instances will be started on all nodes Actions none

12.2. RAC database creation is complete

12.2. RAC database creation is complete

170

You might also like