Step-By-Step Installation of Oracle 9i RAC on HP OpenVMS Cluster [ID 180012.

1] Modified 19-OCT-2010 Type BULLETIN Status PUBLISHED

Step-By-Step Installation of 9i RAC on HP OpenVMS Cluster

Purpose
This document will provide the reader with step-by-step instructions on how to install a Cluster, install Oracle RAC and start a Cluster Database on OpenVMS. For additional explanation or information on any of these steps, please see the references listed at the end of this document. Disclaimer: If there are any errors or issues prior to step 4, please contact HP Support for further assistance. 1. Configuring the Cluster Hardware 1.1 Minimal Hardware list / System Requirements 1.2 Setup Server Parameters 2. Software Requirements 2.1 Operating System and Layered Products 2.2 Operating System Patches 3. Configuring the Cluster 3.1 Install the OpenVMS Operating System 3.2 Install the Operating System Patches 3.3 Adding the Second Node 3.4 Configuring TCP/IP 3.5 Adjusting System Parameters 4. Installing RAC 4.1 Creating the ORACLE Account 4.2 Installing the Software 5. Setting up the Database 5.1 Create the Database 5.2 Configuring the Database for RAC 5.3 Reserving Memory for the SGA 6. References

1. Configuring the Clusters Hardware

1.1 Minimal Hardware list / System Requirements
Refer to the RAC/OpenVMS certification matrix for information on currently supported

hardware/software. One shared disk to install the operating system and layered products on. Using a shared disk simplifies management but this is not mandatory. We will assume a shared system disk which will also be used as the quorum disk in this article. Note: The quorum disk must be a shared disk. Additional disks as needed on the shared storage array to distribute oracle datafiles and separate redo logfiles. We will use one additional disk for this article. Standard network cards for user access. In certain configurations (example SCSI clusters), the network can be used for the cluster communication. OpenVMS also supports sharing disks via the network but this is not recommended for performance. A cluster interconnect. OpenVMS supports different means of sharing disks and cluster communication like Memory Channel, SCSI, CI, DSSI and LAN. For a moderate configuration SCSI is a good option. Cluster communication will use the network . More information about cluster interconnects is discussed in OPS/RAC VMS: Using alternate TCP Interconnects on 8i OPS and 9i RAC on OpenVMS. One CDROM drive to install the software.

1.2 Setup Server Parameters

You need to change the SCSI id for the shared SCSI bus controller on one of the systems and set the correct default boot parameters. Refer to your hardware documentation for assistance. On most Alphaservers this will be as documented below (using dkb200 as system disk). On NODE A >>> set bootdef_dev dkb200 >>> set boot_osflags 0,0 On NODE B >>> set pkb0_host_id 6 >>> set bootdef_dev dkb200 >>> set boot_osflags 10,0

2. Software Requirements
2.1 Operating System and Layered Products
You need licenses for the operating system (two base licenses, one for each node), the cluster software and TCP/IP services. Additionally, for V9.2+ you will need a license for DECwindows/Motif. Check the RAC/OpenVMS certification matrix for requirements.

2.2 Operating System Patches

For a list of the recommended patches, refer to OpenVMS patches (ECOs) required for Oracle RDBMS. To determine which patches have been installed, issue the following command: $ product show history

3.0 Configuring the Cluster

3.1 Install the OpenVMS Operating System
As mentioned before, we will use a shared system disk which also serves as quorum disk. The installation procedure will ask several questions related to your cluster configuration. We will be using a port allocation class on the shared SCSI bus. This naming scheme will introduce a difference in the device names as seen on the Alpha console prompt and VMS. NOTES: In our installation, the shared SCSI bus is pkb with disks dkb200, used as system disk and quorum disk, and dkb300 for our database. We set the port allocation class to 1 for this SCSI bus. OpenVMS will see the drives as $1$dka200 and $1$dka300.

The OpenVMS installation procedure is based on OpenVMS 7.2, there might be slight differences for other versions. When installing Oracle V9.2, you will need at least OpenVMS 7.3. If you want to install the oracle software V9.2 on the system disk, choose ODS-5 as On-Disk Structure level for the system disk. The Oracle 9.2 software tree and inventory MUST be on an ODS-5 disk. Boot the OpenVMS installation CD. Usually the CDROM drive is DKA400 (on the internal SCSI bus) >>> boot dka400 The following lists most of the questions asked by the installation procedure with the answers you should supply. Note that this procedure might be slightly different depending on your configuration. <RET> indicates you should just press the return key. Typical answers are highlighted in bold. Enter choice or ? for help 1 (Upgrade, install or reconfigure OpenVMS Alpha) Do you want to INITIALIZE or to PRESERVE INITIALIZE Enter device name for target disk DKB200 (the name of the shared disk that will be used as system disk ) Do you want to keep this label <RET> (Accept the default) Is this OK Y Password for the system account <enter the password> Re-enter SYSTEM's password for verification <enter the same password again> Will this system be a member of an OpenVMS cluster Y Will this system be an instance in an OpenVMS Galaxy N Will the OpenVMS cluster use more than one system disk N Do you want to install DECWindows Motif Y/ N NOTE: Answer Y for V9.2+ , only the graphical installer is available Do you want to install DECNet Plus N Do you want to install DECNet Phase IV N Do you want to install DIGITAL TCP/IP Services Y (default) Enter SCSNODE NODEA (enter the name for your node) Do you plan to use DECNet N Enter SCSSYSTEMID 1200 - This must be a unique number in the cluster. When running DECNet, this should be calculated from the DECNet address like (area-number * 1024) + node-number. ** some questions on timezone configuration ** ** give the appropriate answers for your system ** Do you want to enter any Product Authorization keys Y

** please enter all your PAK's ** ** Since the base operating system licenses are not shared, you need 2 of them and you will need to restrict each one to a specific node ** Do you always want detailed descriptions N Do you want the defaults for all options Y Do you want to review options N Press Return to continue <RET> Please choose one of the following 8 (Shutdown this system) Boot from the new disk and the configuration of the first cluster node will start. >>> boot The following lists the questions asked by the cluster configuration procedure with the answers you should supply. Note that this procedure might be slightly different depending on your configuration. Typical answers are highlighted in bold. option 1 (Add NODEA to existing cluster or form a new cluster) Is the node to be a clustered node with a shared SCSI bus Y Enter this cluster's group number 1200 (This must be unique on your network, enter a number between 1 and 4095) Enter this cluster's password mycluster (Enter an alphanumeric string - up to 31 characters). Re-enter this cluster's password for verification mycluster (this must obviously be the same as the previous string) Will NODEA be a boot server N Will NODEA be a disk server N Enter a value for NODEA's ALLOCLASS parameter 0 Does this cluster contain a quorum disk Y What is the device name of the quorum disk $1$dka200 - (Enter the full name of your system disk remember we will set a port allocation class, so the DKB200 will become $1$DKA200) Enter [RETURN] to continue <RET> Assign port allocation class to which adapter pkb Port allocation class for PKB0 1 Assign port allocation class to which adapter <RET> Run AUTOGEN now Y

3.2 Install the Operating System Patches

>>> boot Install the latest version of the patches mentioned before. These are available on the OpenVMS website from HP with documentation on how to install them.

3.3 Adding the Second Node

Once the first node is configured, we can add the second system to the cluster. OpenVMS provides command procedures to assist you. sys$manager:cluster_config.com sys$manager:cluster_config_lan.com They only differ in boot protocol used for satellite nodes which we don't have. The output and menu options might be somewhat different depending on your systems configuration. $

Enter choice 1 (ADD an Alpha node to the cluster) Here you get a warning... Do you want to continue Y Is the node to be a clustered node with a shared SCSI bus Y Will the node be a satellite N What is the SCS node name for this node NODEB What is the node's SCSSYSTEMID 1201 Will NODEB be a boot server N What is the device name for NODEB's system root <RET> What is the name of NODEB's system root SYS10 (should be the default ) Will NODEB be a disk server N Enter a value for NODEB's ALLOCLASS parameter 0 Does this cluster contain a quorum disk Y What is the device name of the QUORUM disk <RET> ($1$dka200 should be the default) Size of pagefile for NODEB 1500000 Size of swap file for NODEB <RET> (Use the default size, swapping should be avoided) Size of temporary swap file <RET> Enter [RETURN] to continue <RET> Assign port allocation class to which adapter pkb Port allocation class for pkb0 1 Assign port allocation class to which adapter <RET> Will a disk local only to NODEB be used for paging and swapping N What is the device name for the page and swap files <RET> (Accept the default, this should be the system disk) You can now boot the second system from this disk. >>> boot The system will boot, run autogen and reboot

3.4 Configuring TCP/IP

OpenVMS provides the sys$manager:tcpip$config.com procedure to ease the configuration of TCP/IP. This procedure is fairly simple to use. The easiest way is to specify option A - Configure options 1 - 4 in the Configuration options menu. This will guide you through the complete configuration. The most important part is the interface configuration (core environment). This is where hostname , tcp/ip address, network mask and broadcast address are set. Your network manager should be able to provide these. He will also be able to tell you if a specific domainname needs to be configured and if BIND RESOLVERS (DNS servers) are available. Use the corresponding options in the Core environment menu to configure these. The other options are not needed for SQL*Net but most probably you will need some of the server options to allow telnet and/or rlogin access. You need to configure TCP/IP on both nodes. The following table shows a sample configuration on NODEA, you should use the correct internet addresses you got from your network manager. @sys$manager:tcpip$configure Do you want to grant world read access to non-privileged users N Enter configuration option 1 (Core Environment) Enter configuration option 1 (bind resolver)

Enter your bind server name DNS1 Enter internet address for DNS1 11.11.11.101 Enter bind server name <RET> Enter internet domain mydomain.com Enter configuration option 4 (interfaces) Do you want to configure [WE0] Y Enter unqualified host name NODEA Enter internet address for NODEA 11.11.11.106 Enter internet network mask for NODEA 255.255.248.0 Enter broadcast mask for NODEA 11.11.11.255 Is the above correct Y Define internet VMS cluster N Enter configuration option E (exit menu) Enter configuration option 6 (Startup TCP/IP services for OpenVMS) Enter configuration option E (exit) We have configured and started TCP/IP services for OpenVMS, but we want this to be started during system boot as well. Edit the file sys$startup:systartup_vms.com using your favorite editor and remove the comment delimiter ($!) from the following line: $!$ @sys$startup:tcpip$startup.com The line should look like: $ @sys$startup:tcpip$startup.com Don't forget to save the modified file.

3.5 Adjusting System Parameters

Before continuing with the installation of Oracle Real Application clusters, we will adjust some parameters on both nodes. As you might have noticed, the OpenVMS installation procedure didn't request sizes for the pagefile and swapfile when installing NODEA like it did when adding NODEB. Most likely, the default pagefile will be too small for us. On NODEA we will first create a bigger pagefile. Often, system managers prefer to move these files off the system disk. This is not documented here, the swapfiles procedure will allow you to resize the current files on the system disk, since the default size will be too small. You might want to contact the system manager on this issue. @sys$update:swapfiles Enter new size for paging file 1500000 Enter new size for system dump file <RET> Enter new size for swapping file <RET> The system will now suggest to reboot, don't do it yet. We will also update sys$system:modparams.dat and run autogen on both nodes. After this, the systems will be ready for the installation of Oracle Real Application Clusters. On both nodes, make sure you have at least the following in sys$system:modparams.dat (we will not discuss the entries already present) VOTES=1 EXPECTED_VOTES=3

MIN_GBLPAGES=500000 MIN_GBLSECTIONS=500 PAGEFILE=0 (optional, most people don't want autogen to resize these files) DUMPFILE=0 SWAPFILE=0 NOTE: These values for MIN_GBLPAGES and MIN_GBLSECTIONS should be adequate to get started. We can calculate what we need but we have to know the SGA size for this. We don't actually know yet (It will be about 100Mb for v9.0 and 350MB for v92). The formula's to calculate these are available in ORA_ROOT:[RDBMS]READMEVMS.DOC after the installation of Oracle software. Also check this file for additional parameter settings in relation to your database(s) needs. Also refer to System tuning recommendations for new 8i/9i RDBMS Installations. Now, we are ready to run autogen to adjust the system parameters. This must be done on both nodes. After creating and customizing your database, you'll probably want to run autogen again. $

4.0 Installing RAC

4.1 Creating the ORACLE account
You need to create a account for installing and administering Oracle. The UIC must be higher than MAXSYSGROUP, we also need to assign appropriate quota and privileges. $ set default sys$system $ run authorize

For Oracle RAC V9.0.1:

UAF> ADD Oracle /PASSWORD=ORACLEPASSWORD/UIC=[277,100]/DEVICE=$1$dka200/DIRECTORY=[Oracle]/OWNER="ORACLE DBA"/PRIVILEGE=(CMKRNL,NETMBX,PFNMAP,PRMGBL,PRMMBX,SYSGBL, SYSNAM,TMPMBX,IMPERSONATE,LOG_IO,WORLD,SYSLCK, SYSPRV) /DEFPRIVILEGE=(CMKRNL,NETMBX,PFNMAP,PRMGBL,PRMMBX,SYSGBL, SYSNAM,TMPMBX,IMPERSONATE,LOG_IO,WORLD,SYSLCK, SYSPRV)/bytlm=160000

For Oracle RAC V9.2+:

UAF> ADD Oracle /PASSWORD=ORACLEPASSWORD/UIC=[277,100]/DEVICE=$1$dka200/DIRECTORY=[Oracle]/OWNER="ORACLE DBA"/PRIVILEGE=(GROUP,GRPNAM,OPER,SHARE,CMKRNL,NETMBX,PFNMAP, PRMGBL,PRMMBX,SYSGBL,SYSNAM,TMPMBX,IMPERSONATE,LOG_IO, WORLD,SYSLCK, SYSPRV) /DEFPRIVILEGE=(GROUP,GRPNAM,OPER,SHARE,CMKRNL,NETMBX,PFNMAP, PRMGBL,PRMMBX,SYSGBL,SYSNAM,TMPMBX,IMPERSONATE,LOG_IO, WORLD,SYSLCK, SYSPRV)/bytlm=300000

For Oracle RAC All Versions:

UAF> modify oracle/astlm=250/enqlm=2000/fillm=100/jtquota=8192 -

/pgflquo=1500000/wsdefault=2048/wsextent=8192/wsquota=4096 /flags=nodisuser/nopwdexpired UAF> add/identifier ora_dba UAF> grant/identifier ora_dba oracle UAF> ADD/IDENTIFIER/ATTRIBUTES=SUBSYSTEM ORA_SGA NOTE: A pagefile quota of 1500000 will be required for use of the univeral installer. We don't use the universal installer in this sample installation for V9.0, only for V9.2+ . More information about process quota on OpenVMS is available here. We have specified $1$dka200:[oracle] as the login directory for the new oracle user. We have to create this directory as well as a directory for our database files on $1$dka300. Assuming this is a new, thus empty, disk, we must first initialize it. We will create a directory [oracle.V9] to hold the oracle software on $1$dka200 as well. Note: For Oracle V9.2+, we need an ODS-5 disk to hold the software tree and the inventory. This is not required for V9.0 $ initialize/structure=5 $1$dka300 Oracledb $ mount/cluster $1$dka300 oracledb disk$oracle $ create/directory $1$dka200:[oracle]/owner=oracle $ create/directory $1$dka300:[oracledb]/owner=oracle $ create/directory $1$dka200:[oracle.V9]/owner=oracle Don't forget to make sure that $1$dka300 gets mounted system wide during system boot by adding the mount command above to your systartup_vms.com file. Optionally, to use the Intelligent Agent, you must add the ORA_AGENT_ID identifier to your system and grant it to all users submitting jobs. UAF > ADD/IDENTIFIER ORA_AGENT_ID UAF > GRANT/IDENTIFIER ORA_AGENT_ID <user name>

4.2 Installing the Software

Now the systems are ready for the installation of the Oracle software. Oracle version 9.0 on OpenVMS Alpha provides two installation tools : oracleins which is a character cell based interface and Oracle Universal Installer which is a JAVA based graphical tool. Only the graphical tool is available from v9.2+. If you decided to install DECWindows (required for V9.2+), you will be able to use the GUI. Most of the actions in the remainder of this article are performed with the ORACLE account. If not, we will clearly state which account to use. The Oracle9 server software comes on multiple CD's. To avoid having to switch CD's during the installation, copy the CD's to a temporary location on a hard disk. and then start the installation.

For Oracle RAC V9.2+:

NOTES: 1. If your default temporary directory (SYS$SCRATCH) points to an ODS-5 disk, you don't have to use the -scratchPath <ODS-5 tempdir> option. 2. We will be using the graphical installer, so you need to set your DISPLAY correctly.

3. We will copy the CD's to the hard disk to avoid having to switch CD's during the installation. This must be an ODS-5 disk. $ create/directory $1$dka300:[oracledb.disk1] $ create/directory $1$dka300:[oracledb.disk2] $ mount/override=identification dka400 ! first CD $ backup dka400:[000...] $1$dka300:[oracledb.disk1...] $ dismount dka400 $ mount/override=identification dka400 ! second CD $ backup dka400:[000...] $1$dka300:[oracledb.disk2...] $ dismount dka400 We are ready to start the installation. We will install the oracle software on the system disk and we already created a directory for it. $ set default $1$dka200:[Oracle.V9] $ set display/create/node=<workstation>/transport=tcpip $ @$1$dka300:[oracledb.disk1]runInstaller [- scratchPath <ODS-5 tempdir>]

For a CUSTOM installation:

At the Welcome screen, click Next. When this is your first installation,you get the Inventory Location screen. Make sure this points to the desired ODS-5 directory ($1$dka200:[Oracle.V9.oraInventory]). Click Done. You will be returned to the Welcome screen. Click Next. At the File Locations screen, enter the desired name and path ($1$dka200: [Oracle.V9] )(ODS-5 disk). Press Next. You get the Available Products screen. Oracle 9i Database is selected, press Next. Installation Types, select Custom and press Next. Available Product Components. Choose the required options, be sure to include the Real Application Clusters option. For the HTTP server, an additional account will be required, refer to the installation guide. In this installation, we selected only the database with real application clusters and partitioning option together with the Oracle net listener.Press Next. On the Component Locations screen, you have the possibility to relocate some components. Click Next. Accept to enable the real application clusters by clicking Yes. Press Next. Summary screen, press Install. The Install screen displays the progress of the installation. At the End of Installation screen, press Exit. Confirm by clicking Yes.

For the default ENTERPRISE EDITION installation:

At the Welcome screen, click Next. When this is your first installation,you get the Inventory Location screen. Make sure this points to the desired ODS-5 directory. Click Done. You will be returned to the Welcome screen. Click Next. At the File Locations screen, enter the desired name and path (ODS-5 disk). Press Next. You get the Available Products screen.Oracle 9i Database is selected, press Next.

Installation Types, Enterprise Edition is selected, press Next. Accept to enable the Real Application Clusters option by clicking Yes. Press Next. Summary screen, press Install. The Install screen displays the progress of the installation. At the End of Installation screen, press Exit. Confirm by clicking Yes.

After the installation, we can cleanup the temporary directory on $1$dka300. We will use this directory as our oracle database administration directory. $ delete $1$dka300:[oracledb...]*.*;*

For Oracle RAC V9.0.1:

$ mount/override=identification dka400 ! first CD $ copy dka400:[server]*.* $1$dka300:[oracledb] $ dismount dka400 $ mount/override=identification dka400 ! second CD $ copy dka400:[server]*.* $1$dka300:[oracledb] $ dismount dka400 We are ready to start the installation. We will install the oracle software on the system disk and we already created a directory for it. $ set default $1$dka200:[Oracle.V9] $ backup/log $1$dka300:[oracledb]boot.bck/save_set []/new_version/by_owner=parent $ The following describes the installation, only the minimum options are installed, you can of course install all the products you are licensed for. Typical answers are highlighted in bold. Choose an option please 1 (Create a new ORACLE system) Root directory? <RET> (the default is the current working directory which is ok) Save set location or [RETURN] $1$dka300:[oracledb] Press [RETURN] to continue <RET> Enter a number or (E)XIT to exit installation procedure 1 (Software Installation and Upgrade Menu) Enter a number or (E)XIT to return to the Main Menu 1 ( Select Licensed Products to Load) Enter the number of the product that you want to load Here you should enter all options, one by one, you want to install. Make sure you have RDBMS NETCONFIG SQLPLUS PSOPT UTIL Copy from ( ORA_SOURCE:RDBMS.BCK ) <RET> ...... ...... Enter the number of the product that you want to load E (when you have selected all products you wish to load) Enter a number or (E)XIT to return to the Main Menu 2 (Select Build Configuration Options) Enter the number of the product that you want to configure Here you enter the same products you have loaded. You will get a screen with configuration options for the product. For most products the defaults are fine but be careful for RDBMS, you need to include the Real Application Cluster option. If you have not selected JAVAVM/DBJAVA, do not include the Java Aurora external option. Enter the number of the option that you want to change 8 (Include Real Application Cluster

option) New value Y Enter the number of the option that you want to change E (when you have selected all options you wish to change) Enter the number of the product that you want to configure: E (when you have selected all products you wish to build) Enter a number or (E)XIT to return to the Main Menu 3 (Load and Build Selected Licensed Products) Enter the number of the option you want [2] 1 (Build the Oracle products loaded) Press [RETURN] to continue <RET> Enter a number or (E)XIT to return to the Main Menu E Enter a number or (E)XIT to exit installation procedure E After the installation, we can cleanup the temporary directory on $1$dka300. We will use this directory as our oracle database administration directory. $ delete $1$dka300:[oracledb]*.*;*

5.0 Setting up the Database

5.1 Create the Database
NOTE: On OpenVMS, the oracle SID is limited to 6 characters. Since we will add the instance number to the database name, the latter should not be more than 5 characters. Remember that the global database name consists of <database name>.<domain name>.

For Oracle RAC V9.2+:

The database assistant will allow you to create a completely new database or to use a seed database. These are pre configured databases which will be copied and configured for you, which will be faster than creating a completely new database $ set default $1$dka200:[Oracle.V9] $ @orauser $ @[.bin]dbca

For a non-seed database:

At the Welcome screen, press Next. You will get the Operations screen, Create a database is the default, press Next. Database Templates, select New Database and click Next. Database Identification screen, enter the Global Database Name, the SID will be automatically entered, but add the instance number at the end (1). Press Next. On the Database Features screen, select the features you need, by default, only Oracle JVM is selected (in the Standard Database Features). Press Next. Database Connection Options, select the preferred option and click Next. Initialization Parameters, adapt to your needs and click Next. At the Database Storage screen, you can adapt things to your needs (file location and sizes), press Next.

Creation Options, click Finish. The Summary screen pops up, click OK. You get a screen showing the progress, be patient. Password Management, enter the desired passwords, click Exit. At the Welcome screen, press Next. You will get the Operations screen, Create a database is the default, press Next. Database Templates, select General Purpose and click Next. Database Identification screen, enter the Global Database Name, the SID will be automatically entered, but add the instance number at the end (1). Press Next. Database Connection Options, select the preferred option and click Next. Initialization Parameters, adapt to your needs and click Next. At the Database Storage screen, you can adapt things to your needs (file locations, sizes are fixed), press Next. Creation Options, click Finish. The Summary screen pops up, click OK. You get a screen showing the progress, be patient. Password Management, enter the desired passwords, click Exit.

Using the General Purpose seed database:

Create an additional UNDO tablespace for the second instance. SQL> create undo tablespace undotbs2 datafile 'ora_db:undotbs02.dbf' size 200m; We will also add some views specific for Real Application Clusters. SQL> @ora_rdbms_admin:catclust

For Oracle RAC V9.0.1:

We will also have to use oracleins to create a database. $ oracleins Choose an option please 3 (Reconfigure existing products, manage the database, or load demo tables) Root directory? <RET> Save set location or [RETURN] <RET> Press [RETURN] to continue <RET> Enter a number or (E)XIT to exit installation procedure 2 (Instance Creation, Startup, and Shutdown Menu) Enter a number or (E)XIT to return to Main Menu 1 (Create a New Instance and Database) What is the SID for the instance you want to create? RACV91 What is the name of the database you want to create? RACV9 Enter the number of the option that you want to change 2 (Root directory for database administration directory (ORA_DB)) New Value $1$DKA300:[oracledb] (this will hold our database files) Enter the number of the option that you want to change ** change the options as needed, most are ok for a small database. I would modify the character set to an 8 bit set like WE8ISO8859P1. When all options are set as needed enter E to exit this menu ** Do you want to continue (Y/N)? Y

The database creation will take a while, when it is finished you can exit oracleins and prepare the files for using Real Application Clusters. Oracleins will only create a very basic database with no additional tablespaces. The database initialization files in ORA_DB also need to be adapted. Set the parameter COMPATIBLE = 9.0.1.0.0 in ora_db:init.ora, this will allow us to use the automatic undo management and restart the instance. SQL> shutdown immediate; SQL> startup After restarting the instance, create the additional tablespaces. Use realistic sizes for your datafiles. SQL> create temporary tablespace TEMP tempfile 'ora_db:temp.dbs' size 100m; SQL> create undo tablespace rollbacka datafile 'ora_db:rollbacka.dbs' size 100m; SQL> create undo tablespace rollbackb datafile 'ora_db:rollbackb.dbs' size 100m; SQL> create tablespace users datafile 'ora_db:users.dbf' size 500m; We will also add some views specific for Real Application Clusters. SQL> @ora_rdbms_admin:catclust

5.2 Configuring the database for RAC For Oracle RAC V9.0.1:
Assuming the database has been created on NODEA, you should find the following initialization files in ORA_DB: INIT.ORA : the common initialization file for all instances NODEA_RACV91_INIT.ORA : the initialization file specific for this database instance on NODEA. We will first modify these files to allow this instance to be started as a cluster database: INIT.ORA : add CLUSTER_DATABASE = TRUE add UNDO_MANAGEMENT = AUTO add SERVICE_NAMES = RACV9 NODEA_RACV91_INIT.ORA add INSTANCE_NUMBER = 1 add THREAD = 1 add UNDO_TABLESPACE = ROLLBACKA Shutdown and startup the instance again. You are now running in Real Application Cluster mode on NODEA. We will have to add additional redo log files for the second instance (thread 2). The required undo tablespace has already been created.

SQL> alter database add logfile thread 2 group 3 'ora_db:ora_log3.rdo' size 2m, group 4 'ora_db:ora_log4.rdo' size 2m; SQL> alter database enable public thread 2; After creating the redolog files for the second instance, you can use oracleins on the second node to prepare the instance specific files: $@$1$dka300:[oracle.V9.util]orauser $ oracleins Choose an option please 3 (Reconfigure existing products, manage the database, or load demo tables) Root directory? <RET> Save set location or [RETURN] <RET> Press [RETURN] to continue <RET> Enter a number or (E)XIT to exit installation procedure 2 (Instance creation, Startup and Shutdown Menu) Enter a number or (E)XIT to return to Main Menu 3 (Set up a Parallel Server Instance) What is the SID for the instance you want to setup RACV92 What is the name of the database you want to setup RACV9 Press [RETURN] to continue <RET> Enter a number or (E)XIT to return to Main Menu E Enter a number or (E)XIT to exit installation procedure E Finally, add the instance specific parameters to NODEB_RACV92_INIT.ORA add INSTANCE_NUMBER = 2 add THREAD = 2 add UNDO_TABLESPACE = ROLLBACKB

For Oracle RAC V9.2+:

NOTE: We are creating instance specific passwordfiles in this setup, so there is no need to set remote_login_passwordfile to SHARED as mentioned in the installation guide. Assuming the database has been created on NODEA, you should find the following initialization file in ORA_ROOT:[dbs] INITRACV91.ORA : the initialization file specific for this database instance on NODEA. We will first modify this file to allow this instance to be started as a cluster database: INITRACV91.ORA add INSTANCE_NUMBER = 1 add THREAD = 1 add CLUSTER_DATABASE = TRUE add SERVICE_NAMES = RACV9 Shutdown and startup the instance again. You are now running in Real Application Cluster mode

on NODEA. We will have to add additional redo log files for the second instance (thread 2). The required undo tablespace has already been created. SQL> alter database add logfile thread 2 group 4 'ora_db:redo04.rdo' size 100m, group 5 'ora_db:redo05.rdo' size 100m, group 6 'ora_db:redo06.rdo' size 100m; SQL> alter database enable public thread 2; After creating the redolog files for the second instance, we have to prepare the instance specific files for the second node. Execute these commands on NODEA. Use the pathname for ORA_DB when running create_orasrv_beq.com. $ set default ora_root:[network] $ show logical ora_db "ORA_DB" = "$1$dka200:[ORACLE.V9.ORADATA.RACV9]" ... $ @create_orasrv_beq $1$dka200:[ORACLE.V9.ORADATA.RACV9] RACV92 RACV9 $ set default ora_root:[dbs] $ copy orapwracv91. orapwracv92. $ copy initracv91.ora initracv92.ora $ copy sid_racv91.properties sid_racv92.properties These files will need to be edited for the second instance, initracv92.ora: INSTANCE_NAME = RACV92 UNDO_TABLESPACE = UNDOTBS2 INSTANCE_NUMBER = 2 THREAD = 2 SERVICE_NAMES = RACV9 sid_racv92.properties NODE = NODEB You are now ready to startup your second instance in shared mode on NODEB. $ set default $1$dka200:[Oracle.V9] $ @orauser RACV92 $ sqlplus /nolog SQL> connect / as sysdba SQL> startup With Oracle 9i it is possible to use a server parameter file (spfile) which has advantages over the init.ora files as used in this guide. Click here for information about spfile usage on OpenVMS.

5.3 Reserving Memory for the SGA

OpenVMS allows you to reserve memory for the SGA. This ensures the memory to be available and contiguous for the System Global Area. Since you need to run autogen after reserving memory and the area allocated must be big enough to hold the SGA, i would recommend doing

this after some initial tuning has been done. Also allow the reserved memory to be about 20% bigger than the actual SGA size to avoid the need to recreate the reservation when increasing some init.ora parameters influencing SGA size like db_block_buffers. Memory should be reserved on both nodes.

For Oracle RAC V9.0.1:

$ search ora_dump:nodea_racv91_alert.log allocated ** OpenVMS reserved memory was not pre-allocated for the SGA. SGA size = 92463104 **

For Oracle RAC V9.2+:

$ sea ORA_ROOT:[admin.racv9.bdump]NODEA_RACV91_alert.log alloc ** OpenVMS reserved memory was not pre-allocated for the SGA. SGA size = 336363520 ** This tells us the SGA is about 100 for V9.0.1 (340 for V9.2+) Mb. We will reserve 120 for V9.0.1 (400 for V9.2+)Mb. The reservation and autogen need to be performed using the system account. Remember we used the SID RACV91 on NODEA and RACV92 on NODEB, so for NODEB use ORA_RACV92_SGA for the memory reservation.

The following commands reserve the memory for a V9.0.1 database, please specify 400 instead of 120 for a V9.2+ database or, even better, choose appropriate values based upon the searches above and predicted growth.
$ mc SYSMAN SYSMAN> reserved_memory add ORA_RACV91_SGA/size=120/allocate/zero/page SYSMAN> exit $ NOTE: The unit for reserved memory reservation is Mb. Be careful not to specify a wrong amount of memory since the system might not be able to boot.

6.0 References
Oracle9i Real Application Clusters Installation and Configuration Release 1 (9.0.1) Oracle9i Real Application Clusters Concepts Oracle9i Real Application Clusters Administration Oracle9i for Alpha OpenVMS Release Notes Oracle9i Installation Guide for Alpha OpenVMS Oracle9i Administrator's Reference for Alpha OpenVMS Oracle Real Application Cluster Addendum Note 184875.1 RAC/OpenVMS certification matrix Note 170199.1 OpenVMS patches (ECOs) required for Oracle RDBMS. Note 156484.1 System tuning recommandations for RDBMS Installations

Related Products Oracle Database Products > Oracle Database > Oracle Database > Oracle Server Enterprise Edition Keywords CONFIGURATION; INSTALLATION; DATABASE CONFIGURATION; DATABASE INSTALLATION; ORAVMS Errors AURORA; DS-5