Oracle9i Real Application Clusters Installation and Configuration Release 1 (9.0.1) Part Number A89868-02 |
|
This chapter describes how to configure shared disk subsystems to deploy Real Application Clusters. This chapter explains how to configure your subsystem so that the nodes within a cluster can read from and write to the shared disks. The topics in this chapter include:
Perform the procedures in this chapter only after ensuring that your system complies with the hardware and software requirements described in Chapter 1, and before continuing with the procedures for installing the Oracle9i Enterprise Edition software in Chapter 3.
Note:
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 number and type of raw devices required depends on several factors as described in the following sections.
You must configure at least one device for the configuration information as described under the following heading, "The Configuration Raw Device". If you select one of the preconfigured database options on the Installer's Database Configuration screen, or if you use the DBCA interactively, you must also configure additional raw devices as described under the heading "Additional Raw Devices Required by the DBCA".
You must create at least one shared raw device as an information repository for the database server configuration. You must do this:
Oracle Enterprise Manager, the Oracle Database Configuration Assistant (DBCA), the SRVCTL Utility, and other management tools use this raw device to store configuration information about:
The configuration process for this raw device depends on your operating system:
srvcfg
by creating an Object Link Manager (OLM) symbolic link with a fixed name.
To use the DBCA to create your database, the procedures for which appear in Chapter 4, configure additional raw devices as described in the next section.
To use the Oracle Database Configuration Assistant, you must configure raw devices as described in this section. These devices are in addition to the configuration device mentioned in the previous section. Create these devices before running the Oracle Universal Installer to install the Oracle Enterprise Edition software. The DBCA cannot create a Real Application Clusters database unless you have properly configured these raw devices:
The Oracle9i Database installation guide for Windows for additional information about raw device requirements for Windows NT and Windows 2000
See Also:
Before installing the Oracle software, create enough partitions of specific sizes to support your database and leave a few spare partitions of the same size for future expansion. For example, if you have space on your shared disk array, select a limited set of standard partition sizes for your entire database. Partition sizes of 50MB, 100MB, 500MB, and 1GB are suitable for most databases. Also create a few very small and very large spare partitions that are, for example, 1MB and perhaps 5GB or greater in size.
Based your plans for using each partition, determine the placement of these spare partitions using a couple of methods. For example, you can mix different sizes on one disk, or segment each disk into same-sized partitions.
The DBCA supports several database templates for Real Application Clusters, General Purpose, Transaction Processing, Data Warehouse, and New Database. Chapter 3 describes these configuration types in more detail. The first three options are preconfigured database options and they include datafiles. As already mentioned, the New Database option does not include datafiles and is fully customizable.
If you use the General Purpose, Transaction Processing, or Data Warehouse configuration, you must create specific tablespaces using specific minimum sizes as described under the heading "Recommended Tablespace and File Capacities".
You can customize these tablespaces if you select the Customized database configuration type on the Universal Installer's Database Configuration screen. You can also specify the file and block sizes. To use the Customized configuration option, ensure that the raw volumes on UNIX, or logical drives on Windows NT and Windows 2000, have enough space to accommodate the customized sizes.
Use Veritas Volume Manager to create your volumes and then change the permissions and ownership on the volumes to the correct user, for example, oracle
user. Also make sure that all volumes on the disks have the same names on each node. More information about Veritas Volume Manager is available at:
http://www.veritas.com
Use the tablespace size requirements in Table 2-1 for the General Purpose, Transaction Processing, and Data Warehouse configuration types. These requirements apply to both UNIX and Windows NT and Windows 2000 platforms. The preconfigured database options automatically create tablespaces and files with the capacities shown in Table 2-1. If you use the Customized database configuration, use these recommended sizes as guidelines.
Some operating systems require additional overhead for the partition sizes in Table 2-1. Refer to your operating system-specific documentation for the exact raw partition size requirements.
If you do not use the DBCA and instead create your database manually, the number of raw devices you create depends on the number of instances and database options that you install.
See Also:
Chapter 5, "Manually Creating Real Application Clusters Databases" for more information about manual database creation |
The configuration of raw devices is operating system-specific as described in the following sections:
Refer to the section that corresponds to your operating system.
Use the following procedures to configure raw volumes on UNIX:
Table 2-2 Recommended Names for Oracle Database Files
If you select the General Purpose, Transaction Processing, or Data Warehouse database configuration type on the Universal Installer's Database Configuration screen, or if you select the Customized option on this screen and then use one of the DBCA templates that uses datafiles, then you must perform the following step:
database_object=raw_device_file_path
Use the following format for your undo tablespace files:
undotbs_number
Where number is the number of the instance.
Use the following format for your redo log files:
redothread_number
Where thread is the thread ID of the instance and number is the log number (1 or 2) of the instance.
When you create the ASCII file, separate the database objects from the paths with equals (=) signs as shown in Example 2-1:
system1=/dev/vx/rdsk/oracle_dg/clustdb_raw_system_400m spfile1=/dev/vx/rdsk/oracle_dg/clustdb_raw_spfile_5m users1=/dev/vx/rdsk/oracle_dg/clustdb_raw_users_120m temp1=/dev/vx/rdsk/oracle_dg/clustdb_raw_temp_100m undotbs1=/dev/vx/rdsk/oracle_dg/clustdb_raw_undotbs1_312m undotbs2=/dev/vx/rdsk/oracle_dg/clustdb_raw_undotbs2_312m example1=/dev/vx/rdsk/oracle_dg/clustdb_raw_example_160m cwmlite1=/dev/vx/rdsk/oracle_dg/clustdb_raw_cwmlite_100m indx1=/dev/vx/rdsk/oracle_dg/clustdb_raw_indx_70m tools1=/dev/vx/rdsk/oracle_dg/clustdb_raw_tools_12m drsys1=/dev/vx/rdsk/oracle_dg/clustdb_raw_dr_90m control1=/dev/vx/rdsk/oracle_dg/clustdb_raw_controlfile1_110m control2=/dev/vx/rdsk/oracle_dg/clustdb_raw_controlfile2_110m redo1_1=/dev/vx/rdsk/oracle_dg/clustdb_raw_log11_120m redo1_2=/dev/vx/rdsk/oracle_dg/clustdb_raw_log12_120m redo2_1=/dev/vx/rdsk/oracle_dg/clustdb_raw_log21_120m redo2_2=/dev/vx/rdsk/oracle_dg/clustdb_raw_log22_120m
Also make sure to use the following format for your redo log files:
redothread_number
Where thread is the thread ID of the instance and number is the log number (1 or 2) of the instance.
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 Example 2-1:
setenv DBCA_RAW_CONFIG filename
After configuring the raw volumes, perform the following steps prior to installation as root
user:
osdba
group defined in the /etc/group
file on all nodes of your cluster. To designate an osdba
group name and group number and osoper
group during installation, these group names must be identical on all nodes of your UNIX cluster that will be part of the Real Application Clusters database. The default UNIX group name for the osdba
and osoper
groups is dba
.
oracle
account on each node so that the account:
.rhosts
file of the oracle
account, or the /etc/hosts.equiv
file.
oracle
account user, check for user equivalence for the oracle
account by performing a remote login (rlogin
) to each node in the cluster.
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.
After configuring your raw volumes, proceed to Chapter 4 to install the Oracle9i Enterprise Edition software and to configure your Oracle9i Real Application Clusters database.
Datafiles, control files, and redo log files must reside on unformatted raw devices on Windows NT and Windows 2000 platforms. On Windows, these are more commonly referred to as logical drives that reside within extended partitions. The extended partitions point to raw space on the disk. To configure the logical drives, create multiple logical partitions using Windows NT Disk Administrator or Windows 2000 Computer Manager.
Before creating the logical partitions, first create extended partitions that point to the raw space on the disk. Then create multiple logical partitions within the extended partitions and assign symbolic link names to them using the Object Link Manager (OLM).
See Also:
Oracle9i Database installation guide for Windows for further information about configuring logical drives for Real Application Clusters on Windows NT and Windows 2000 |
The DBCA General Purpose, Transaction Processing, and Data Warehouse database configuration types require the symbolic link names shown in the left-hand column of Table 2-4 for a two-instance Real Application Clusters database:
To install the Oracle operating system-dependent clusterware, run the Oracle Cluster Setup Wizard. The Cluster Setup Wizard installs the Object Link Manager tool with which you create persistent symbolic links to the logical drives.
If you do not install the Oracle OSD clusterware, then copy the Object Link Manager software from the preinstall directory on the Oracle CD. Refer to the online document, the Oracle9i Database installation guide for Windows for further procedures for completing the configuration using OLM.
After configuring your logical drives, proceed to Chapter 3 to install the Oracle9i Enterprise Edition software and to configure your Real Application Clusters database.
|
Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|