Name Revision Information Size(Kb) Architecture Category A5158A -> B.11.00.10 PCI Tachyon TL/TS Fibre Channel 1747 HP-UX_B.11.00_32/64 OrderedApps A5230A -> B.11.00.05 100BT/9000 PCI 499 HP-UX_B.11.00_32/64 OrderedApps B2491BA -> B.11.00 MirrorDisk/UX 5046 HP-UX_B.11.00_32/64 OrderedApps B5161EA -> A.11.09 ServiceGuard OPS Edition Bundle 36447 HP-UX_B.11.00_32/64 OrderedApps B7609BA -> A.03.20 Event Monitoring Service 1584 HP-UX_B.11.00_32/64 category HPUXEng64RT -> B.11.00.01 English HP-UX 64-bit Runtime Environment 390733 HP-UX_B.11.00_64 HPUXEnvironments HWE1100 -> B.11.00.0206. Hardware Enablement Patches for HP-UX 11.00, June 2002 186773 HP-UX_B.11.00_32/64 HPUXAdditions LSM -> 5.5.lsm.Build LSM for HP-UX 10.XX and 11.xx 56969 HP-UX_B.1XX.XX_7XX/8XX system_management PHCO_26823 -> B.11.00.16 HP Array Manager/60 cumulative patch 10682 HP-UX_B.11.00_32/64 patch PHSS_21947 -> 1.0 ld(1) and linker tools cumulative patch 14492 HP-UX_B.11.00_32/64 patch UnlimUserLic -> B.11.00.02 HP-UX Unlimited-User License 12 HP-UX_B.11.00_32/64 UserLicenses XSWGR1100 -> B.11.00.47.08 General Release Patches, November 1999 (ACE) 260032 HP-UX_B.11.00_32/64 HPUXAdditions 安装的文件集。 VG Name /dev/rac VG Write Access read/write VG Status available, shared, server Max LV 255 Cur LV 34 Open LV 34 Max PV 16 Cur PV 2 Act PV 2 Max PE per PV 8643 VGDA 4 PE Size (Mbytes) 4 Total PE 17282 Alloc PE 9480 Free PE 7802 Total PVG 0 Total Spare PVs 0 Total Spare PVs in use 0 vg RAC的信息 另一台上的VG信息。 VG Name /dev/rac VG Write Access read/write VG Status available, shared, client Max LV 255 Cur LV 34 Open LV 34 Max PV 16 Cur PV 2 Act PV 2 Max PE per PV 8643 VGDA 4 PE Size (Mbytes) 4 Total PE 17282 Alloc PE 9480 Free PE 7802 Total PVG 0 Total Spare PVs 0 DBCA_RAW_CONFIG的内容    control1=/dev/rac/rctrl01 control2=/dev/rac/rctrl02 control3=/dev/rac/rctrl03 indx=/dev/rac/rindex redo1_1=/dev/rac/rredo11 redo1_2=/dev/rac/rredo12 redo1_3=/dev/rac/rredo13 redo1_4=/dev/rac/rredo14 redo2_1=/dev/rac/rredo21 redo2_2=/dev/rac/rredo22 redo2_3=/dev/rac/rredo23 redo2_4=/dev/rac/rredo24 undotbs1=/dev/rac/rundo01 undotbs2=/dev/rac/rundo02 spfile=/dev/rac/rspfile system=/dev/rac/rsystem temp=/dev/rac/rtemp tools=/dev/rac/rtools users=/dev/rac/ruser 内核的参数： Current Pending Associated Name Value Value Type Module Description NSTREVENT 50 50 Static N/A Max Number of Outstanding Streams bufcalls NSTRPUSH 16 16 Static N/A Max Number of Streams Modules in Single Stream NSTRSCHED 0 0 Static N/A Number of Streams Scheduler Daemons to Run STRCTLSZ 1024 1024 Static N/A Max Size of Streams Message Control (Bytes) STRMSGSZ 65535 65535 Static N/A Max Size of Streams Message Data (Bytes) acctresume 4 4 Static N/A Threshold to Resume Accounting acctsuspend 2 2 Static N/A Threshold to Suspend Accounting aio_listio_max 256 256 Static N/A Max No. of AIO Ops That Can Be Specified in lio_list Call aio_max_ops 2048 2048 Static N/A Maximum No. of AIO Ops That Can Be Queued At Any Time aio_physmem_pct 10 10 Static N/A Percentage of Physical Memory Lockable for Request Call-Back Operations aio_prio_delta_max 20 20 Static N/A Max Slowdown Factor; Greatest Delta Allowed in aiocb's aio_reqprio Field allocate_fs_swapmap 0 0 Static N/A Allocate Swapmap Space at swapon alwaysdump 0 0 Static N/A Bit-Mask of Kernel Memory Pages Included in Dumps bufcache_hash_locks 128 128 Static N/A Buffer Cache Spinlock Pool Size bufpages 1992 1992 Static N/A Number of Buffer Pages chanq_hash_locks 256 256 Static N/A Channel Queue Spinlock Pool Size create_fastlinks 0 0 Static N/A Create Fast Symbolic Links dbc_max_pct 2 2 Static N/A Max Dynamic Buffer Cache Size as Percent of System RAM Size dbc_min_pct 2 2 Static N/A Min Dynamic Buffer Cache Size as Percent of System RAM Size default_disk_ir 0 0 Static N/A Immediate Report (Write Cache Enable) Behavior for SCSI Disks dnlc_hash_locks 64 64 Static N/A Number of Locks For Directory Cache Synchronization dontdump 0 0 Static N/A Bit-Mask of Kernel Memory Pages Excluded From Dumps dskless_node 0 0 Static N/A Diskless Node Flag dst 1 1 Static N/A Daylight Savings Time Policy eqmemsize 15 15 Static N/A Minimum Number of Equivalently Mapped Memory Pages on the Reserve List fcp_large_config 0 0 Static N/A Boolean; 0 If Small (<=64 Nodes) Loop, 1 if Large (<=126 Nodes) Loop fs_async 1 1 Static N/A Select Asynchronous Writes ftable_hash_locks 64 64 Static N/A File Table Spinlock Pool Size hdlpreg_hash_locks 128 128 Static N/A Number (Given As Power of Two) of Spinlocks Allocated to Pregion Hash Table Objects hfs_max_ra_blocks 8 8 Static N/A Maximum Number of Read-Ahead Blocks Outstanding for HFS File Systems, in Blocks hfs_ra_per_disk 64 64 Static N/A Amount of HFS File System Read-Ahead, in Kbytes initmodmax 50 50 Static N/A Max No. of Kernel Modules Saved By System Crash Dump io_ports_hash_locks 64 64 Static N/A I/O Ports Spinlock Pool Size ksi_alloc_max 5312 5312 Static N/A System-wide Limit of Queued Signal That Can be Allocated ksi_send_max 32 32 Static N/A Max No. of Queued Signals a Process May Send and Have Pending at Receiver(s) max_async_ports 50 50 Static N/A Maximum Number of asyncdsk Ports That Can be Open At One Time max_fcp_reqs 512 512 Static N/A Maximum Number of Concurrent Fiber Channel Requests Per Adapter max_mem_window 0 0 Static N/A Maximum Number of Simultaneous Memory Windows max_thread_proc 256 256 Static N/A Max No. of Threads Allowed in Each Process maxdsiz 1073741824 1073741824 Static N/A Max Data Segment Size For 32-bit Processes (Bytes) maxdsiz_64bit 1073741824 1073741824 Static N/A Max Data Segment Size For 64-bit Processes (Bytes) maxfiles 2048 2048 Static N/A Soft File Limit Per Process maxfiles_lim 2048 2048 Static N/A Hard File Limit Per Process maxssiz 8388608 8388608 Static N/A Max Stack Segment Size For 32-bit Processes (Bytes) maxssiz_64bit 8388608 8388608 Static N/A Max Stack Segment Size For 64-bit Processes (Bytes) maxswapchunks 4096 4096 Static N/A Max Number of Swap Chunks maxtsiz 1073741824 1073741824 Static N/A Max Text Segment Size For 32-bit Processes (Bytes) maxtsiz_64bit 1073741824 1073741824 Static N/A Max Text Segment Size For 64-bit Processes (Bytes) maxuprc 597 597 Static N/A Max Number of User Processes maxusers 200 200 Static N/A Value of MAXUSERS Macro (Does Not Affect Max. User Logins) maxvgs 80 80 Static N/A Max Number of Volume Groups mesg 1 1 Static N/A Enable Sys V Messages modstrmax 500 500 Static N/A Max Size (Bytes) of Kernel-Module Savecrash Table msgmap 6642 6642 Static N/A Max Number of Message Map Entries msgmax 32768 32768 Static N/A Message Max Size (bytes) msgmnb 65535 65535 Static N/A Max Number of Bytes on Message Queue msgmni 664 664 Static N/A Number of Message Queue Identifiers msgseg 26560 26560 Static N/A Number of Segments Available for Messages msgssz 128 128 Static N/A Message Segment Size msgtql 6640 6640 Static N/A Number of Message Headers nbuf 0 0 Static N/A Number of Buffer Cache Headers ncallout 680 680 Static N/A Max Number of Pending Timeouts ncdnode 150 150 Static N/A Max Number of Open CDFS Files nclist 3300 3300 Static N/A Number of cblocks for pty and tty Data Transfers ncsize 8384 8384 Static N/A Directory Name Lookup Cache (DNLC) Space Needed for Inodes ndilbuffers 30 30 Static N/A Number of DIL Buffers nfile 12008 12008 Static N/A Max Number of Open Files nflocks 664 664 Static N/A Max Number of File Locks ninode 7360 7360 Static N/A Max Number of Open Inodes nkthread 1178 1178 Static N/A Max Number of Kernel Threads Supported by the System no_lvm_disks 0 0 Static N/A Boolean; Set Only If System Has No LVM Disks nproc 664 664 Static N/A Max Number of Processes npty 60 60 Static N/A Number of ptys (Pseudo ttys) nstrpty 60 60 Static N/A Max Number of Streams-Based PTYs nstrtel 200 200 Static N/A Number of Telnet Session Device Files nswapdev 25 25 Static N/A Max Devices That Can be Enabled for Swap nswapfs 10 10 Static N/A Max File Systems That Can be Enabled for Swap num_tachyon_adapters 0 0 Static N/A Number of Tachyon-based Fiber Channel Adapters in the System o_sync_is_o_dsync 0 0 Static N/A Enable/Disable Translation of O_SYNC to O_DSYNC in open(2)/fcntl(2) Calls page_text_to_local 0 0 Static N/A Enable/Disable Swapping of Program Text Segments to Local Swap pfdat_hash_locks 128 128 Static N/A Pfdat Spinlock Pool Size public_shlibs 1 1 Static N/A Public Shared Libraries region_hash_locks 128 128 Static N/A Region Spinlock Pool Size remote_nfs_swap 0 0 Static N/A Enable Swapping Across NFS rtsched_numpri 32 32 Static N/A Number of POSIX.1b Realtime Priorities to Support scroll_lines 100 100 Static N/A Number of ITE Off Screen Lines scsi_max_qdepth 8 8 Static N/A Maximum Number of SCSI Commands Queued Up For SCSI Devices scsi_maxphys 1048576 1048576 Static N/A Maximum Record Size For SCSI I/O Subsystem, In Bytes sema 1 1 Static N/A Enable Sys V Semaphores semaem 16384 16384 Static N/A Max Value for Adjust on Exit Semaphores semmap 3322 3322 Static N/A Max Number of Semaphore Map Entries semmni 3320 3320 Static N/A Number of Semaphore Identifiers semmns 6640 6640 Static N/A Max Number of Semaphores semmnu 660 660 Static N/A Number of Semaphore Undo Structures semume 64 64 Static N/A Semaphore Undo Entries Per Process semvmx 32768 32768 Static N/A Semaphore Maximum Value sendfile_max 0 0 Static N/A Max No. of Buffer Cache Pages Usable by sendfile System Call shmem 1 1 Static N/A Enable Sys V Shared Memory shmmax 1073741824 1073741824 Static N/A Max Shared Mem Segment (Bytes) shmmni 512 512 Static N/A Number of Shared Memory Identifiers shmseg 32 32 Static N/A Shared Memory Segments Per Process st_ats_enabled 0 0 Static N/A Unknown st_fail_overruns 0 0 Static N/A Boolean; If Set, SCSI Tape Read Resulting In Data Overrun Causes Failure st_large_recs 0 0 Static N/A Boolean; If Set, Enables Large Record Support For SCSI Tape streampipes 0 0 Static N/A Force All Pipes to be Streams-Based swapmem_on 0 0 Static N/A Allow Memory to Exceed Swap Space swchunk 2048 2048 Static N/A Swap Chunk Size (1K Blocks) sysv_hash_locks 128 128 Static N/A System V IPC Spinlock Pool Size tcphashsz 0 0 Static N/A TCP Hash Table Size, in Bytes timeslice 1 1 Static N/A Scheduling Interval (10 mS Ticks) timezone 420 420 Static N/A Minutes West of Greenwich unlockable_mem 2000 2000 Static N/A Non-Lockable Memory (4096-Byte Pages) vnode_cd_hash_locks 128 128 Static N/A Vnode Clean/Dirty Spinlock Pool Size vnode_hash_locks 128 128 Static N/A Vnode Spinlock Pool Size vps_ceiling 16 16 Static N/A Maximum System-Selected Page Size (in Kbytes) vps_chatr_ceiling 65536 65536 Static N/A Maximum chatr-Selected Page Size (in Kbytes) vps_pagesize 4 4 Static N/A Default User Page Size (in Kbytes) vx_ncsize 1024 1024 Static N/A Directory Name Lookup Cache (DNLC) Space Needed for VxFS Inodes vx_ninode 0 0 Static N/A Maximum Number of Inodes In VxFS Inode Cache (0 = Tune According to Physical Memory) vx_noifree 0 0 Static N/A Boolean; If Non-Zero, Memory Is Never Freed From VxFS Inode Cache vxfs_max_ra_kbytes 1024 1024 Static N/A Maximum Amount of VxFS File System Read-Ahead Outstanding, in Kbytes vxfs_ra_per_disk 1024 1024 Static N/A Amount of VxFS File System Read-Ahead, in Kbytes ============================ LISTENER_N40002 = (ADDRESS = (PROTOCOL = TCP)(HOST = n4000a)(PORT = 1521)) LISTENER_N40001 = (ADDRESS = (PROTOCOL = TCP)(HOST = n4000b)(PORT = 1521)) INST1_HTTP = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = n4000b)(PORT = 1521)) ) (CONNECT_DATA = (SERVER = SHARED) (SERVICE_NAME = MODOSE) (PRESENTATION = http://HRService) ) ) N4000 = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = n4000b)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = n4000a)(PORT = 1521)) (LOAD_BALANCE = yes) ) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = n4000) ) ) EXTPROC_CONNECTION_DATA = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC)) ) (CONNECT_DATA = (SID = PLSExtProc) (PRESENTATION = RO) ) ) N40002 = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = n4000a)(PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = n4000) (INSTANCE_NAME = n40002) ) ) N40001 = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = n4000b)(PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = n4000) (INSTANCE_NAME = n40001) ) ) LISTENERS_N4000 = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = n4000b)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = n4000a)(PORT = 1521)) ) cmclconfig.ascii 文件和ORACLE 的连接状态    # ********************************************************************** # ********* HIGH AVAILABILITY CLUSTER CONFIGURATION FILE *************** # ***** For complete details about cluster parameters and how to **** # ***** set them, consult the cmquerycl(1m) manpage or your manual. **** # ********************************************************************** # Enter a name for this cluster. This name will be used to identify the # cluster when viewing or manipulating it. CLUSTER_NAME cluster1 # Cluster Lock Device Parameters. This is the volume group that # holds the cluster lock which is used to break a cluster formation # tie. This volume group should not be used by any other cluster # as cluster lock device. FIRST_CLUSTER_LOCK_VG /dev/rac # Definition of nodes in the cluster. # Repeat node definitions as necessary for additional nodes. NODE_NAME n4000a NETWORK_INTERFACE lan0 HEARTBEAT_IP 192.168.100.115 NETWORK_INTERFACE lan1 HEARTBEAT_IP 172.18.100.115 FIRST_CLUSTER_LOCK_PV /dev/dsk/c3t0d0 # List of serial device file names # For example: # SERIAL_DEVICE_FILE /dev/tty0p0 # Warning: There are no standby network interfaces for lan0. # Warning: There are no standby network interfaces for lan1. NODE_NAME n4000b NETWORK_INTERFACE lan0 HEARTBEAT_IP 192.168.100.116 NETWORK_INTERFACE lan1 HEARTBEAT_IP 172.18.100.116 FIRST_CLUSTER_LOCK_PV /dev/dsk/c7t0d0 # List of serial device file names # For example: # SERIAL_DEVICE_FILE /dev/tty0p0 # Warning: There are no standby network interfaces for lan0. # Warning: There are no standby network interfaces for lan1. # Cluster Timing Parmeters (microseconds). HEARTBEAT_INTERVAL 1000000 NODE_TIMEOUT 2000000 # Configuration/Reconfiguration Timing Parameters (microseconds). AUTO_START_TIMEOUT 600000000 NETWORK_POLLING_INTERVAL 2000000 # Package Configuration Parameters. # Enter the maximum number of packages which will be configured in the cluster. # You can not add packages beyond this limit. # This parameter is required. MAX_CONFIGURED_PACKAGES 1 # List of cluster aware Volume Groups. These volume groups will # be used by package applications via the vgchange -a e command. # For example: # VOLUME_GROUP /dev/vgdatabase. # VOLUME_GROUP /dev/vg02. # List of OPS Volume Groups. # Formerly known as DLM Volume Groups, these volume groups # will be used by OPS cluster applications via # the vgchange -a s command. (Note: the name DLM_VOLUME_GROUP # is also still supported for compatibility with earlier versions.) # For example: # OPS_VOLUME_GROUP /dev/vgdatabase. # OPS_VOLUME_GROUP /dev/vg02. OPS_VOLUME_GROUP /dev/rac # DLM parameters. # When using Oracle Parallel Server versions prior to 8.0, set # DLM_ENABLED to YES, enter values for the other parameters as # specified in your Oracle documentation, and set GMS_ENABLED to NO below. DLM_ENABLED NO DLM_CONNECT_TIMEOUT 30000000 DLM_PING_INTERVAL 20000000 DLM_PING_TIMEOUT 60000000 DLM_RECONFIG_TIMEOUT 300000000 DLM_COMMFAIL_TIMEOUT 270000000 DLM_HALT_TIMEOUT 240000000 # GMS parameters. # When using Oracle Parallel Server version 8.0x or later, set # DLM_ENABLED to NO above, set GMS_ENABLED to YES below, and # enter values for the other parameters as specified in your # Oracle documentation. GMS_ENABLED NO GMS_CONNECT_TIMEOUT 30000000 GMS_LOCATION RAC 的启动与维护管理及安装成后的过程回忆 cmruncl to start the cluster: n4000a:# cmruncl Use vgchange to mark shared volume groups shared from one node: n4000a# vgchange -S y -c y rac Use vgchange to activate shared logical volumes from each node: n4000a# vgchange -a s rac n4000a# remsh n4000b /usr/sbin/vgchange -a s rac 下一步是：ORACLE启动： n4000a#su – oracle $ gsdctl start n4000b# su - oracle $ gsdctl start 然后在一台机器上运行： $ srvctl start database –d n4000 安装过程中的软件包： 安装过程回忆：’ 1. 安装cluster 软件 2. 创建RAW设备 /dev/rac/spfile ,,,,,,,,,, 3. vgimport 去另外一台。 4. 然后再配置cluster 软件 5. 配置好了，就启动cluster 6. 准备安装oracle软件。 7. 不需要运行preroot.sh 8. 选择cluster 安装，同时选择好两个节点。 9. 选择相关的安装软件，一直下去。直到安装完成。 10. 安装完成以后运行：root.sh文件 11. 修改/var/opt/oracle/srvConfig.loc文件中的内容。并修改成oracle：dba的属性。 然后再启动cluster时，运行： n4000a:# cmruncl Use vgchange to mark shared volume groups shared from one node: n4000a# vgchange -S y -c y rac Use vgchange to activate shared logical volumes from each node: n4000a# vgchange -a s rac n4000a# remsh n4000b /usr/sbin/vgchange -a s rac 下一步是：ORACLE启动gsd： n4000a#su – oracle $ gsdctl start n4000b# su - oracle $ gsdctl start 再在两台机器上运行：$lsnrctl start 启动listener.ora文件。 12. 在一台机器上运行dbca 进行建库。这样就可以成功。metalink网站的RAC for hp unix 的安装原文贴出来 Step-By-Step Installation of RAC on HP-UX Purpose This document provides the reader with step-by-step instructions on how to configure a cluster, install Oracle Real Application Clusters (RAC) and start a cluster database on HP-UX. 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 3.3, please contact HP Support. The information contained here is as accurate as possible at the time of writing. · 1. Configuring the Cluster Hardware o 1.1 Minimal Hardware list / System Requirements § 1.1.1 Hardware § 1.1.2 Software § 1.1.3 Patches o 1.2 Installing Disk Arrays o 1.3 Installing Cluster Interconnect and Public Network Hardware o 1.4 Unix User and Group Creation · 2. Creating a Cluster o 2.1 Modifying the /etc/lvmrc file o 2.2 Create a Shared Logical Volume o 2.3 Cluster Software Installation o 2.4 Form a One-Node Cluster o 2.5 Basic Cluster Administration o 2.6 Log Files for the Cluster · 3. Preparing for the Installation of RAC o 3.1 Configure the Shared Disks o 3.2 UNIX Pre-Installation Tasks o 3.3 Using the Oracle Universal Installer for Real Application Clusters o 3.4 Create a RAC Database using the Oracle Database Configuration Assistant · 4. Administering Real Application Clusters Instances · 5. References 1. Configuring the Clusters Hardware 1.1 Minimal Hardware list / System Requirements For a two node cluster the following would be a minimum recommended hardware list. Check the RAC/HP certification matrix for RAC updates on currently supported hardware/software. 1.1.1 Hardware All hardware is provided by HP. A bridge or hub is mandatory when using ethernet for the interconnect. HP does not support a straight through ethernet connection for a private ethernet interconnect. · For HP servers, third-party storage products, Cluster interconnects, Public networks, Switch options, Memory, Swap & CPU requirements consult the operating system or hardware vendor and see the RAC/HP certification matrix. · Private network connection can be any of the following (see the RAC/HP certification matrix): HyperFabric RS232 Serial Ethernet or FDDI · If the cluster is a 2 node configuration, any of the available disk subsystems provided by HP or their vendors are supported. Each of the disk arrays are dual-ported to each node, meaning that each array has a cable directly connecting it to each node. · Disk Subsystem Options (see the RAC/HP certification matrix): 2-4 nodes: A3311A Deskside fast/wide A3312A Rackmount fast/wide 2-8 nodes: Fibre Channel such as EMC Symmetrix · RAM Memory allocation: Minimum 256 MB. Use the following command to verify the amount of memory installed on your system $ /usr/sbin/dmesg | grep "Physical:" · Swap Space: Minimum 2 x RAM or 750 MB, whichever is greater. Use the following command to determine the amount of swap space installed on your system: $ /usr/sbin/swapinfo -a (requires root privileges) 1.1.2 Software · OS version >11.0 64bit · HP Serviceguard Extension for RAC (formerly called Serviceguard OPS Edition) >11.09 Confirm with HP what version of Serviceguard is certified with the specific OS version. · Oracle Version 9.x is a 64bit Application and is available for HP 64bit Operating systems only. Verify that the OS is running a 64bit Kernel: #/bin/getconf KERNEL_BITS · Use SAM and ensure that the following OS Kernel Parameter Settings are set to a minimum of these values: MAXDSIZ 536870912 bytes MAXDSIZ_64BIT 2147483648 bytes SEMMNS 2000 SEMVMX 32768 SHMMAX 1073741824 bytes or Available physical memory SHMMNI 512 SHMSEG 32 SHMMIN 1 SHMMNI 100 SHMSEG 10 SEMMNI 70 · When using HMP (Hyper Messaging Protocol) instead of UDP for the interconnet protocol, the file /opt/clic/lib/skgxp/skclic.conf contains HMP configuration parameters that are relevant to Oracle CLIC_ATTR_APPL_MAX_PROCS = Maximum number of Oracle processes. CLIC_ATTR_APPL_MAX_NQS = Being obsoleted. Set to the same as CLIC_ATTR_APPL_MAX_PROCS CLIC_ATTR_APPL_MAX_MEM_EPTS = 5000 Maximum number of Buffer descriptors. CLIC_ATTR_APPL_MAX_RECV_EPTS = Maximum number of Oracle Ports = CLIC_ATTR_APPL_MAX_PROCS CLIC_ATTR_APPL_DEFLT_PROC_SENDS = 1024 Maximum number of outstanding sends CLIC_ATTR_APPL_DEFLT_NQ_RECVS = 1024 Maximum number of outsdanding receives on a port · If the HMP cannot be used UDP may be sufficient over both HyperFabric cards or Ethernet cards where HMP can only be used over the HyperFabric interface. There are no addition settings when using UDP protocol. 1.1.3 Patches Ensure that you are running the lasted Patch release. Patches listed will be superceded by new patches. Oracle always recommends to have the most current patch set from the OS vendor. You can also reference Document id 43507.1 in Oracle Metalink which is a best effort to update customers on OS patches that are needed. HP provides patch bundles at http://www.software.hp.com/SUPPORT_PLUS Individual patches can be downloaded from http://itresourcecenter.hp.com To determine which operating system patches are installed, enter the following command: $ /usr/sbin/swlist -l patch To determine which operating system bundles are installed, enter the following command: $ /usr/sbin/swlist -l bundle 1.2 Installing Disk Arrays Prior to installing the operating environment and Cluster software, ensure that the shared disks are installed and available to each node (see the RAC/HP certification matrix). Typical cabinet or disk enclosures have disks preinstalled. Simply connect the cabinet to each server SCSI controller via standard SCSI connections. There are special consideration for A3311A and the A3312A disk subsystems. Both the A3311A and A3312A use simple SCSI connections, hence it is essential that all devices on a single SCSI chain have a unique target ID. This ID not only includes all the disks in the A3311A and A3312A but also the two hosts SCSI controllers to which the SCSI cables are connected from the A3311A. Change one of the nodes SCSI ID address from the default 6 to 7 on the SCSI controllers based on the hardware guide. This is only an issue when SCSI is being used. 1.3 Installing Cluster Interconnect and Public Network Hardware For the Network configuration, have at least 2 connections to send a heartbeat from one system to the other (Ethernet, FDDI, RS232, Fibre Channel). That means that the minimal recommended configuration would consist of the following: 1 x Ethernet for Data, cluster interconnect heartbeat of the Cluster 1 x RS232 connection for the cluster heartbeat Another configuration would be: 1 x Ethernet for Data, cluster interconnect heartbeat of the Cluster 1 x Ethernet as Standby network (that means no IP address!) - This would be configured as a second ip address subnet. NOTE: Both networks must be bridged (recommendation from HP) If you have configured a Standby network card, it will take over in the case of a problem with one of the primary network cards. This is only the case if the cards are the same card type (only Ethernet or FDDI). Once the cluster interconnect is connected modify the following: The /etc/cmcluster/cmclnodelist file is used by HP Serviceguard Extension for remote operations. If this file is not configured, HP Serviceguard Extension will use the /.rhosts file. Modify the /etc/cmcluster/cmclnodelist file: Format of the file is: [hostname] [rootuse] [#comment] Example of a "/etc/cmcluster/cmclnodelist" equivalence file: nodehp1 root #node1 nodehp2 root #node2 nodehp1 oracle # software owner on node1 hodehp2 oracle # software owneron node2 1.4 Unix User and Group Creation Create a user who will own the Oracle RAC software. This must be done on each node in the cluster using the same uid and gid for each user. 1. Log in as the root user. 2. Create a unix database administrator group and oracle user: Look at /etc/group, use any available gid this example uses 200 # groupadd -g 200 dba Look at /etc/passwd and ensure that the uid you select is not used. This example uses uid 300 and the newly created gid for the dba group. # useradd -u 300 -g 200 -d /home/oracle -s /usr/bin/csh -m oracle 2. Pre-Cluster Configuration 2.1 Modifying the /etc/lvmrc File as the root user · Turn off automatic volume group activation to keep shared volume groups from being activated at boot time. You want the shared volume groups enabled with the cluster startup: Copy the /etc/lvmrc to a backup file # cp /etc/lvmrc /etc/lvmrc_orig: Modify the /etc/lvmrc: From: AUTO_VG_ACTIVATE=1 To: AUTO_VG_ACTIVATE=0 · Add entries to the custom_vg_activation function in the /etc/lvmrc file for all volume groups that include logical volumes with non shared filesystems on them /etc/lvmrc example: custom_vg_activation() { # e.g. /sbin/vgchange -a y -s # parallel_vg_sync "/dev/vg00 /dev/vg01" # parallel_vg_sync "/dev/vg02 /dev/vg03" /sbin/vgchange -a y vg00 /sbin/vgchange -a y vg01 /sbin/vgchange -a y vg02 /sbin/vgchange -a y vg03 return 0 } 2.2 Creating Shared Logical Volumes · On the first node: pvcreate -f /dev/rdsk/c0t12d0 - Initialize direct access to a physical volume mkdir /dev/vg_ops - Create a directory in the /dev directory with the name of the volume group mknod /dev/vg_ops/group c 64 0x060000 - Major number will always be 64 but the minor number must be unique vgcreate /dev/vg_ops /dev/dsk/c0t12d0 - Create the volume group vgchange -a y vg_ops - Activate the volume group lvcreate -n P901_control_01.ctl -L 110 /dev/vg_ops - Create your logical volumes lvcreate -n P901_control_02.ctl -L 110 /dev/vg_ops lvcreate -n P901_control_03.ctl -L 110 /dev/vg_ops lvcreate -n P901_system_01.dbf -L 400 /dev/vg_ops lvcreate -n P901_log1_01.log -L 120 /dev/vg_ops lvcreate -n P901_log1_02.log -L 120 /dev/vg_ops lvcreate -n P901_log1_03.log -L 120 /dev/vg_ops lvcreate -n P901_log2_01.log -L 120 /dev/vg_ops lvcreate -n P901_log2_02.log -L 120 /dev/vg_ops lvcreate -n P901_log2_03.log -L 120 /dev/vg_ops lvcreate -n P901_spfile1.dbf -L 5 /dev/vg_ops lvcreate -n P901_users_01.dbf -L 120 /dev/vg_ops lvcreate -n P901_temp_01.dbf -L 100 /dev/vg_ops lvcreate -n P901_undotbs_01.dbf -L 312 /dev/vg_ops lvcreate -n P901_undotbs_02.dbf -L 312 /dev/vg_ops lvcreate -n P901_example_01.dbf -L 160 /dev/vg_ops lvcreate -n P901_cwmlite_01.dbf -L 100 /dev/vg_ops lvcreate -n P901_indx_01.dbf -L 70 /dev/vg_ops lvcreate -n P901_tools_01.dbf -L 20 /dev/vg_ops lvcreate -n P901_drsys_01.dbf -L 90 /dev/vg_ops vgchange -a n vg_ops - Deactivate the volume group vgexport -v -s -p -m /tmp/vg_ops.map /dev/vg_ops - Create a map of the logical volume rcp /tmp/vg_ops.map opcbhp2:/tmp/vg_ops.map - Copy the volume map to each node · On the other nodes: mkdir /dev/vg_ops mknod /dev/vg_ops/group c 64 0x060000 vgimport -v -s -m /tmp/vg_ops.map /dev/vg_ops - Create the volume group and logical volumes on the other nodes · Modify the ownership an permissions on both nodes, this example shows the commands if being done from the node where the logical volumes were originally created: # chown oracle:dba /dev/vg_ops/r* # remsh nodehp2 chown oracle:dba /dev/vg_ops/r* # chmod 777 /dev/vg_ops # remsh nodehp2 chmod 777 /dev/vg_ops # chmod 660 /dev/vg_ops/r* # remsh nodehp2 chmod 660 /dev/vg_ops/r* Note: When creating a new volume group the minor number must be unique when issuing the "mknod" command. You can use the following command to see which minor numbers are already in use: # find /dev -name group -exec ls -l {} \; crw------- 1 root sys 64 0x060000 May 6 07:52 /dev/vg_ops/group In this example the minor listed for "vg_ops" is "0x060000" so if creating a new volume group "0x060000" could not be used. Valid minor numbers range from "0x010000" to "0xFF0000". 2.3 Cluster Software Installation The HP Serviceguard Extension for RAC is installed from the Applications CD-ROM of HP-UX using "swinstall" 2.4 Form a Cluster 1. Steps to configure the cluster: Use cmquerycl to create a cluster configuration file The cmquerycl command is used to create a default cluster configuration ascii file. You must specify each node that belongs to the cluster with the -n option. This needs to be performed on one node only. # cmquerycl -v -C /etc/cmcluster/cmclconf.ascii -n nodehp1 -n nodehp2 2. Modify the cluster configuration file Parameters that needed modification on nodehp . Note that this cluster is running a minimal configuration. All other parameters in the ascii configuration file where set automatically such as heartbeat configuration.: CLUSTER_NAME #example nodehp FIRST_CLUSTER_LOCK # /dev/vg_ops FIRST_CLUSTER_PV # /dev/dsk/c0t12d0 OPS_VOLUME_GROUP # /dev/vg_ops DLM_ENABLED # NO GMS_ENABLED # NO Additonal Information: FIRST_CLUSTER_LOCK, FIRST_CLUSTER_PV = The cluster lock volume group and disk are used for the same purpose as a quorum device. This volume group and disk must be accessible by all nodes. A failure of a node to access the lock volume will result with the node leaving the cluster. OPS_VOLUME_GROUP = All cluster aware volume groups need to be identified DLM_ENABLED and GMS_ENABLED = set to NO when using >8.1.7 3. Use cmcheckconf to verify the cluster configuration file Verify the cluster configuration file # cmcheckconf -v -C /etc/cmcluster/cmclconf.ascii 4. Use vgchange to activate the lock volume group Activate the lock volume group which is vg_ops on the nodehp cluster: # vgchange -a y vg_ops 5. Use cmapplyconf to copy the cluster configuration to all nodes Use the cmapplyconf command to apply the configuration to all nodes: # cmapplyconf -v -C /etc/cmcluster/cmclconf.ascii 6. Use vgchange again to deactive the lock volume group Deactivate the lock volume group: # vgchange -a n vg_ops 2.5 Basic Cluster Administration Starting & Stopping Cluster Nodes Starting the cluster: cmruncl to start the cluster: # cmruncl Use vgchange to mark shared volume groups shared from one node: # vgchange -S y -c y vg_ops Use vgchange to activate shared logical volumes from each node: # vgchange -a s vg_ops # remsh nodehp2 /usr/sbin/vgchange -a s vg_ops Use cmhaltcl to stop the cluster or cmhaltnode to remove a single node from the cluster: # cmhaltnode Adding a Node Back Into a Running Cluster Use cmrunnode to add the node back into a running cluster # cmrunnode 2.6 Log Files for Cluster /var/adm/syslog/syslog.log contains the system log for HP Serviceguard Extension for RAC messages. /var/adm/clic_log is used for HyperFabric interface log if this is being used. 3.0 Preparing for the installation of RAC The Real Application Clusters installation process includes three major tasks. 1. Configure the shared disks and UNIX preinstallation tasks. 2. Run the Oracle Universal Installer to install the Oracle9i Enterprise Edition and the Oracle9i Real Application Clusters software. 3. Create and configure your database. 3.1 Configure the Shared Disks Real Application Clusters requires that all each instance be able to access a set of unformatted devices on a shared disk subsystem. These shared disks are also referred to as raw devices. If your platform supports an Oracle-certified cluster file system, however, you can store the files that Real Application Clusters requires directly on the cluster file system. The Oracle instances in Real Application Clusters write data onto the raw devices to update the control file, server parameter file, each datafile, and each redo log file. All instances in the cluster share these files. The Oracle instances in the RAC configuration write information to raw devices defined for: · The control file · The spfile.ora · Each datafile · Each ONLINE redo log file · Server Manager (SRVM) configuration information It is therefore necessary to define raw devices for each of these categories of file. The Oracle Database Configuration Assistant (DBCA) will create a seed database expecting the following configuration:- Raw Volume File Size Sample File Name SYSTEM tablespace 400 Mb db_name_raw_system_400m USERS tablespace 120 Mb db_name_raw_users_120m TEMP tablespace 100 Mb db_name_raw_temp_100m UNDOTBS tablespace per instance 312 Mb db_name_raw_undotbsx_312m CWMLITE tablespace 100 Mb db_name_raw_cwmlite_100m EXAMPLE 160 Mb db_name_raw_example_160m OEMREPO 20 Mb db_name_raw_oemrepo_20m INDX tablespace 70 Mb db_name_raw_indx_70m TOOLS tablespace 12 Mb db_name_raw_tools_12m DRYSYS tablespace 90 Mb db_name_raw_drsys_90m First control file 110 Mb db_name_raw_controlfile1_110m Second control file 110 Mb db_name_raw_controlfile2_110m Two ONLINE redo log files per instance 120 Mb x 2 db_name_thread_lognumber_120m spfile.ora 5 Mb db_name_raw_spfile_5m srvmconfig 100 Mb db_name_raw_srvmconf_100m Note: Automatic Undo Management requires an undo tablespace per instance therefore you would require a minimum of 2 tablespaces as described above. By following the naming convention described in the table above, raw partitions are identified with the database and the raw volume type (the data contained in the raw volume). Raw volume size is also identified using this method. Note: In the sample names listed in the table, the string db_name should be replaced with the actual database name, thread is the thread number of the instance, and lognumber is the log number within a thread. On the node from which you run the Oracle Universal Installer, create an ASCII file identifying the raw volume objects as shown above. The DBCA requires that these objects exist during installation and database creation. When creating the ASCII file content for the objects, name them using the format: database_object=raw_device_file_path When you create the ASCII file, separate the database objects from the paths with equals (=) signs as shown in the example below:- system1=/dev/vx/rdsk/oracle_dg/db_name_raw_system_400m spfile1=/dev/vx/rdsk/oracle_dg/db_name_raw_spfile_5m users1=/dev/vx/rdsk/oracle_dg/db_name_raw_users_120m temp1=/dev/vx/rdsk/oracle_dg/db_name_raw_temp_100m undotbs1=/dev/vx/rdsk/oracle_dg/db_name_raw_undotbs1_312m undotbs2=/dev/vx/rdsk/oracle_dg/db_name_raw_undotbs2_312m example1=/dev/vx/rdsk/oracle_dg/db_name_raw_example_160m cwmlite1=/dev/vx/rdsk/oracle_dg/db_name_raw_cwmlite_100m indx1=/dev/vx/rdsk/oracle_dg/db_name_raw_indx_70m tools1=/dev/vx/rdsk/oracle_dg/db_name_raw_tools_12m drsys1=/dev/vx/rdsk/oracle_dg/db_name_raw_drsys_90m control1=/dev/vx/rdsk/oracle_dg/db_name_raw_controlfile1_110m control2=/dev/vx/rdsk/oracle_dg/db_name_raw_controlfile2_110m redo1_1=/dev/vx/rdsk/oracle_dg/db_name_raw_log11_120m redo1_2=/dev/vx/rdsk/oracle_dg/db_name_raw_log12_120m redo2_1=/dev/vx/rdsk/oracle_dg/db_name_raw_log21_120m redo2_2=/dev/vx/rdsk/oracle_dg/db_name_raw_log22_120m You must specify that Oracle should use this file to determine the raw device volume names by setting the following environment variable where filename is the name of the ASCII file that contains the entries shown in the example above: csh: setenv DBCA_RAW_CONFIG filename sh or ksh: DBCA_RAW_CONFIG=filename; export DBCA_RAW_CONFIG 3.2 UNIX Preinstallation Tasks After configuring the raw volumes, perform the following steps prior to installation as root user: · Create a mount point directory on each node to serve as the top of your Oracle software directory structure so that: o The name of the mount point on each node is identical to that on the initial node o The oracle account has read, write, and execute privileges · On the node from which you will run the Oracle Universal Installer, set up user equivalence by adding entries for all nodes in the cluster, including the local node, to the .rhosts file of the oracle account, or the /etc/hosts.equiv file. · As oracle account user, check for user equivalence for the oracle account by performing a remote login (rlogin) to each node in the cluster. · As oracle account user, if you are prompted for a password, you have not given the oracle account the same attributes on all nodes. You must correct this because the Oracle Universal Installer cannot use the rcp command to copy Oracle products to the remote node's directories without user equivalence. Establish system environment variables · Set a local bin directory in the user's PATH, such as /usr/local/bin, or /opt/bin. It is necessary to have execute permissions on this directory. · Set the DISPLAY variable to point to the system's (from where you will run OUI) IP address, or name, X server, and screen. · Set a temporary directory path for TMPDIR with at least 20 Mb of free space to which the OUI has write permission. Establish Oracle environment variables: Set the following Oracle environment variables: Environment Variable Suggested value ORACLE_BASE eg /u01/app/oracle ORACLE_HOME eg /u01/app/oracle/product/901 ORACLE_TERM xterm NLS_LANG AMERICAN-AMERICA.UTF8 for example ORA_NLS33 $ORACLE_HOME/ocommon/nls/admin/data PATH Should contain $ORACLE_HOME/bin CLASSPATH $ORACLE_HOME/JRE:$ORACLE_HOME/jlib \$ORACLE_HOME/rdbms/jlib: \$ORACLE_HOME/network/jlib · Create the directory /var/opt/oracle and set ownership to the oracle user. 3.3 Using the Oracle Universal Installer for Real Application Clusters Follow these procedures to use the Oracle Universal Installer to install the Oracle Enterprise Edition and the Real Application Clusters software. Oracle9i is supplied on multiple CD-ROM disks. During the installation process it is necessary to switch between the CD-ROMS. OUI will manage the switching between CDs. For the latest RAC/HP certification matrix see here. To install the Oracle Software, perform the following:. · Login as the oracle user · $ ./<cdrom_mount_point>/runInstaller · At the OUI Welcome screen, click Next. · A prompt will appear for the Inventory Location (if this is the first time that OUI has been run on this system). This is the base directory into which OUI will install files. The Oracle Inventory definition can be found in the file /var/opt/oracle/oraInst.loc. Click OK. · Verify the UNIX group name of the user who controls the installation of the Oracle9i software. If an instruction to run /tmp/orainstRoot.sh appears, the pre-installation steps were not completed successfully. Typically, the /var/opt/oracle directory does not exist or is not writeable by oracle. Run /tmp/orainstRoot.sh to correct this, forcing Oracle Inventory files, and others, to be written to the ORACLE_HOME directory. Once again this screen only appears the first time Oracle9i products are installed on the system. Click Next. · The File Location window will appear. Do NOT change the Source field. The Destination field defaults to the ORACLE_HOME environment variable. Click Next. · Select the Products to install. In this example, select the Oracle9i Server then click Next. · Select the installation type. Choose the Enterprise Edition option. The selection on this screen refers to the installation operation, not the database configuration. The next screen allows for a customized database configuration to be chosen. Click Next. · Select the configuration type. In this example you choose the Advanced Configuration as this option provides a database that you can customize, and configures the selected server products. Select Customized and click Next. · Select the other nodes on to which the Oracle RDBMS software will be installed. It is not necessary to select the node on which the OUI is currently running. Click Next. · Identify the raw partition in to which the Oracle9i Real Application Clusters (RAC) configuration information will be written. It is recommended that this raw partition is a minimum of 100MB in size. · An option to Upgrade or Migrate an existing database is presented. Do NOT select the radio button. The Oracle Migration utility is not able to upgrade a RAC database, and will error if selected to do so. · The Summary screen will be presented. Confirm that the RAC database software will be installed and then click Install. The OUI will install the Oracle9i software on to the local node, and then copy this information to the other nodes selected. · Once Install is selected, the OUI will install the Oracle RAC software on to the local node, and then copy software to the other nodes selected earlier. This will take some time. During the installation process, the OUI does not display messages indicating that components are being installed on other nodes - I/O activity may be the only indication that the process is continuing. 3.4 Create a RAC Database using the Oracle Database Configuration Assistant The Oracle Database Configuration Assistant (DBCA) will create a database for you (for an example of manual database creation see Database Creation in Oracle9i RAC). The DBCA creates your database using the optimal flexible architecture (OFA). This means the DBCA creates your database files, including the default server parameter file, using standard file naming and file placement practices. The primary phases of DBCA processing are:- · Verify that you correctly configured the shared disks for each tablespace (for non-cluster file system platforms) · Create the database · Configure the Oracle network services · Start the database instances and listeners Oracle Corporation recommends that you use the DBCA to create your database. This is because the DBCA preconfigured databases optimize your environment to take advantage of Oracle9i features such as the server parameter file and automatic undo management. The DBCA also enables you to define arbitrary tablespaces as part of the database creation process. So even if you have datafile requirements that differ from those offered in one of the DBCA templates, use the DBCA. You can also execute user-specified scripts as part of the database creation process. Note: Prior to running the DBCA it may be necessary to run the NETCA tool or to manually set up your network files. To run the NETCA tool execute the command netca from the $ORACLE_HOME/bin directory. This will configure the necessary listener names and protocol addresses, client naming methods, Net service names and Directory server usage. Also, it is recommended that the Global Services Daemon (GSD) is started on all nodes prior to running DBCA. To run the GSD execute the command gsd from the $ORACLE_HOME/bin directory. The DBCA and the Oracle Net Configuration Assistant also accurately configure your Real Application Clusters environment for various Oracle high availability features and cluster administration tools. · DBCA will launch as part of the installation process, but can be run manually by executing the command dbca from the $ORACLE_HOME/bin directory on UNIX platforms. The RAC Welcome Page displays. Choose Oracle Cluster Database option and select Next. · The Operations page is displayed. Choose the option Create a Database and click Next. · The Node Selection page appears. Select the nodes that you want to configure as part of the RAC database and click Next. If nodes are missing from the Node Selection then perform clusterware diagnostics by executing the $ORACLE_HOME/bin/lsnodes -v command and analyzing its output. Refer to your vendor's clusterware documentation if the output indicates that your clusterware is not properly installed. Resolve the problem and then restart the DBCA. · The Database Templates page is displayed. The templates other than New Database include datafiles. Choose New Database and then click Next. · The Show Details button provides information on the database template selected. · DBCA now displays the Database Identification page. Enter the Global Database Name and Oracle System Identifier (SID). The Global Database Name is typically of the form name.domain, for example mydb.us.oracle.com while the SID is used to uniquely identify an instance (DBCA should insert a suggested SID, equivalent to name1 where name was entered in the Database Name field). In the RAC case the SID specified will be used as a prefix for the instance number. For example, MYDB, would become MYDB1, MYDB2 for instance 1 and 2 respectively. · The Database Options page is displayed. Select the options you wish to configure and then choose Next. Note: If you did not choose New Database from the Database Template page, you will not see this screen. · The Additional database Configurations button displays additional database features. Make sure both are checked and click OK. · Select the connection options desired from the Database Connection Options page. Note: If you did not choose New Database from the Database Template page, you will not see this screen. Click Next. · DBCA now displays the Initialization Parameters page. This page comprises a number of Tab fields. Modify the Memory settings if desired and then select the File Locations tab to update information on the Initialization Parameters filename and location. Then click Next. · The option Create persistent initialization parameter file is selected by default. If you have a cluster file system, then enter a file system name, otherwise a raw device name for the location of the server parameter file (spfile) must be entered. Then click Next. · The button File Location Variables… displays variable information. Click OK. · The button All Initialization Parameters… displays the Initialization Parameters dialog box. This box presents values for all initialization parameters and indicates whether they are to be included in the spfile to be created through the check box, included (Y/N). Instance specific parameters have an instance value in the instance column. Complete entries in the All Initialization Parameters page and select Close. Note: There are a few exceptions to what can be altered via this screen. Ensure all entries in the Initialization Parameters page are complete and select Next. · DBCA now displays the Database Storage Window. This page allows you to enter file names for each tablespace in your database. · The file names are displayed in the Datafiles folder, but are entered by selecting the Tablespaces icon, and then selecting the tablespace object from the expanded tree. Any names displayed here can be changed. A configuration file can be used, see section 3.1, (pointed to by the environment variable DBCA_RAW_CONFIG). Complete the database storage information and click Next. · The Database Creation Options page is displayed. Ensure that the option Create Database is checked and click Finish. · The DBCA Summary window is displayed. Review this information and then click OK. · Once the Summary screen is closed using the OK option, DBCA begins to create the database according to the values specified. A new database now exists. It can be accessed via Oracle SQL*PLUS or other applications designed to work with an Oracle RAC database. 4.0 Administering Real Application Clusters Instances Oracle Corporation recommends that you use SRVCTL to administer your Real Application Clusters database environment. SRVCTL manages configuration information that is used by several Oracle tools. For example, Oracle Enterprise Manager and the Intelligent Agent use the configuration information that SRVCTL generates to discover and monitor nodes in your cluster. Before using SRVCTL, ensure that your Global Services Daemon (GSD) is running after you configure your database. To use SRVCTL, you must have already created the configuration information for the database that you want to administer. You must have done this either by using the Oracle Database Configuration Assistant (DBCA), or by using the srvctl add command as described below. If this is the first Oracle9i database created on this cluster, then you must initialize the clusterwide SRVM configuration. Firstly, create or edit the file /var/opt/oracle/srvConfig.loc file and add the entry srvconfig_loc=path_name.where the path name is a small cluster-shared raw volume eg $ vi /var/opt/oracle/srvConfig.loc srvconfig_loc=/dev/vx/rdsk/datadg/rac_srvconfig_10m Then execute the following command to initialize this raw volume (Note: This cannot be run while the gsd is running. Before v9.2 you will need to kill the .../jre/1.1.8/bin/... process to stop the gsd from running):- $ srvconfig -init The first time you use the SRVCTL Utility to create the configuration, start the Global Services Daemon (GSD) on all nodes so that SRVCTL can access your cluster's configuration information. Then execute the srvctl add command so that Real Application Clusters knows what instances belong to your cluster using the following syntax:- For Oracle RAC v9.0.1:- $ gsd Successfully started the daemon on the local node. $ srvctl add db -p db_name -o oracle_home Then for each instance enter the command: $ srvctl add instance -p db_name -i sid -n node To display the configuration details for, example, databases racdb1/2, on nodes racnode1/2 with instances racinst1/2 run:- $ srvctl config racdb1 racdb2 $ srvctl config -p racdb1 racnode1 racinst1 racnode2 racinst2 $ srvctl config -p racdb1 -n racnode1 racnode1 racinst1 Examples of starting and stopping RAC follow:- $ srvctl start -p racdb1 Instance successfully started on node: racnode2 Listeners successfully started on node: racnode2 Instance successfully started on node: racnode1 Listeners successfully started on node: racnode1 $ srvctl stop -p racdb2 Instance successfully stopped on node: racnode2 Instance successfully stopped on node: racnode1 Listener successfully stopped on node: racnode2 Listener successfully stopped on node: racnode1 $ srvctl stop -p racdb1 -i racinst2 -s inst Instance successfully stopped on node: racnode2 $ srvctl stop -p racdb1 -s inst PRKO-2035 : Instance is already stopped on node: racnode2 Instance successfully stopped on node: racnode1 For Oracle RAC v9.2.0+:- $ gsdctl start Successfully started the daemon on the local node. $ srvctl add database -d db_name -o oracle_home [-m domain_name] [-s spfile] Then for each instance enter the command: $ srvctl add instance -d db_name -i sid -n node To display the configuration details for, example, databases racdb1/2, on nodes racnode1/2 with instances racinst1/2 run:- $ srvctl config racdb1 racdb2 $ srvctl config -p racdb1 -n racnode1 racnode1 racinst1 /u01/app/oracle/product/9.2.0.1 $ srvctl status database -d racdb1 Instance racinst1 is running on node racnode1 Instance racinst2 is running on node racnode2 Examples of starting and stopping RAC follow:- $ srvctl start database -d racdb2 $ srvctl stop database -d racdb2 $ srvctl stop instance -d racdb1 -i racinst2 $ srvctl start instance -d racdb1 -i racinst2 $ gsdctl stat GSD is running on local node $ gsdctl stop For further information on srvctl and gsdctl see the Oracle9i Real Application Clusters Administration manual. 5.0 References · Note 154360.1 - HP: Quick Start Guide - 9.0.x RDBMS Installation · Note:189256.1 - Script to Verify Installation Requirements for Oracle 9.x version of RDBMS · Note:137288.1 - Database Creation in Oracle9i RAC · RAC/HP certification matrix · Oracle9i Real Application Clusters on HP-UX · Oracle9i Real Application Clusters Installation and Configuration Release 1 (9.0.1) · Oracle9i Real Application Clusters Concepts · Oracle9i Real Application Clusters Administration · Oracle9i Real Application Clusters Deployment and Performance · Oracle9i Installation Guide for Compaq Tru64, Hewlett-Packard HPUX, IBM-AIX, Linux, and Sun Solaris-based systems. · Oracle9i Release Notes