Oracle9i Real Application Clusters Setup and Configuration Release 2 (9.2) Part Number A96600-01 |
|
This chapter describes how to configure shared disk subsystems to deploy Real Application Clusters in environments that do not support (or for which you do not want to use) cluster file systems (CFS). If your system supports a cluster file system and you do not want to use raw devices as described in this chapter, then proceed to Chapter 3. The topics in this chapter include:
Real Application Clusters requires that each instance share a set of unformatted devices on a shared disk subsystem if you are not using a cluster file system for datafiles.
The Oracle instances in Real Application Clusters write data onto the shared files to update the control file, server parameter file, each datafile, and each redo log file. 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 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 Database Configuration Assistant (DBCA) interactively, then 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. This device is referred to as the Server Management (SRVM) configuration device which is a component of Real Application Clusters. Enterprise Manager (EM) uses SRVM to perform Real Application Clusters-specific operations.
The SRVM core includes the server configuration file or raw device, the Global Services Daemon (GSD) which manipulates the device, and the Server Control (SRVCTL) Utility and interfaces to the configuration. SRVM also includes facilities that are used by the DBCA, the Oracle Universal Installer (OUI), and the Network Configuration Assistant (NetCA), to enable them to operate on multiple nodes.
You must create a shared raw device for SRVM:
Oracle Enterprise Manager (EM), the Database Configuration Assistant (DBCA), the Server Control (SRVCTL) Utility, and other management tools use this raw device to store configuration information about:
The configuration procedures that you use for this raw device depends on your operating system:
srvcfg,
by creating an Object Link Manager (OLM) symbolic link with a fixed name.
Configure additional raw devices as described in the next section to use the DBCA to create your database. The procedures for using the DBCA appear in Chapter 4.
To use the 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 OUI to install the Oracle Enterprise Edition software. The DBCA cannot create a Real Application Clusters database unless you have properly configured the following raw devices:
See Also:
The Oracle9i Database Installation Guide for Windows for additional information about raw device requirements for Windows NT and Windows 2000 |
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 on your plans for using each partition, determine the placement of these spare partitions by combining different sizes on one disk, or by segmenting each disk into same-sized partitions.
Note: Ensuring that there are spare partitions enables you to perform emergency file relocations or additions if a tablespace datafile becomes full. |
The DBCA has four database templates, General Purpose, Transaction Processing, Data Warehouse, and New Database. Chapter 3 describes these configuration templates in more detail. The first three templates contain preconfigured database options. The New Database template does not contain preconfigured options and is fully customizable.
If you use the General Purpose, Transaction Processing, or Data Warehouse configuration, then you must create specific tablespaces using the 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 datafile file name and its size. To use the Customized configuration option, ensure that the raw volumes on UNIX, or raw partitions 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 and the same permissions 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 UNIX, Windows NT, and Windows 2000 platforms. If you use the New Database configuration type, then use these recommended sizes as guidelines.
Note: If you use manual undo management, then make the RBS tablespace raw device datafile at least 500MB in size. |
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, then 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:
The following step is recommended for all configuration types. If you select the New Database configuration type, then you can enter the raw device names on the DBCA screen.
database_object=raw_device_file_path
When you create the ASCII file, separate each database objects from its paths with an equal (=) sign as shown in Example 2-1:
system=/dev/vx/rdsk/oracle_dg/clustdb_raw_system_400m spfile=/dev/vx/rdsk/oracle_dg/clustdb_raw_spfile_5m users=/dev/vx/rdsk/oracle_dg/clustdb_raw_users_120m temp=/dev/vx/rdsk/oracle_dg/clustdb_raw_temp_100m undotbs1=/dev/vx/rdsk/oracle_dg/clustdb_raw_undotbs1_250m undotbs2=/dev/vx/rdsk/oracle_dg/clustdb_raw_undotbs2_250m example=/dev/vx/rdsk/oracle_dg/clustdb_raw_example_160m cwmlite=/dev/vx/rdsk/oracle_dg/clustdb_raw_cwmlite_100m xml=/dev/vx/rdsk/oracle_dg/clustdb_raw_xml_50m odm=/dev/vx/rdsk/oracle_dg/clustdb_raw_odm_20m indx=/dev/vx/rdsk/oracle_dg/clustdb_raw_indx_70m tools=/dev/vx/rdsk/oracle_dg/clustdb_raw_tools_12m drsys=/dev/vx/rdsk/oracle_dg/clustdb_raw_dr_250m 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
Note: If you are not using automatic undo management, then substitute the entries for rbs=/dev/vx/rdsk/oracle_dg/clustdb_raw_rbs_500m |
To enable Oracle to determine the raw device volume names, specify that Oracle use the ASCII file described in this section. Do this by setting the following environment variable where filename is the complete pathname 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
user account on each node so that the oracle
user:
.rhosts
file of the oracle
account, or the /etc/hosts.equiv
file.oracle
user, check for user equivalence for the oracle
user by performing a remote login (rlogin
) to each node in the cluster. If you are prompted for a password, then you have not given the oracle user the same attributes on all nodes. You must correct this because the OUI 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.
If you do not use a cluster file system for datafiles, then the 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 disks. To configure the logical drives, create multiple logical partitions using Windows NT Disk Administrator or Windows 2000 Disk Management.
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. Oracle uses these names to map the tablespaces as shown in the sample file in Example 2-1.
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 © 1998, 2002 Oracle Corporation. All Rights Reserved. |
|