Академический Документы
Профессиональный Документы
Культура Документы
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
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.
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.
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
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
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.
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. $
/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>
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>]
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...]*.*;*
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]*.*;*
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.
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
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
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.
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.
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