Oracle® Real Application Clusters Installation and Configuration Guide
10g Release 1 (10.1) for AIX-Based Systems, Apple Mac OS X, hp HP-UX, hp Tru64 UNIX, Linux, Solaris Operating System, and Windows Platforms Part No. B10766-08 |
|
Previous |
Next |
This chapter describes the tasks that you must complete before you start the Oracle Universal Installer (OUI). It includes information about the following tasks:
Choose a Storage Option for Oracle CRS, Database, and Recovery Files
Create Directories for Oracle CRS, Database, or Recovery Files
Before you install the Oracle software, you must complete several tasks as the root
user. To log in as the root
user, complete one of the following procedures:
Note: Unless you intend to complete a silent-mode installation, you must install the software from an X Window System workstation, an X terminal, or a PC or other system with X server software installed.For more information about silent-mode installations, refer to Appendix B. |
If you are installing the software from an X Window System workstation or X terminal:
Start a local terminal session, for example, an X terminal (xterm
).
If you are not installing the software on the local system, enter the following command to enable remote hosts to display X applications on the local X server:
$ xhost +
If you are not installing the software on the local system, use the ssh
, rlogin
, or telnet
commands to connect to the system where you want to install the software:
$ telnet remote_host
If you are not logged in as the root
user, enter the following command to switch user to root
:
$ su - root password: #
If you are installing the software from a PC or other system with X server software installed:
Note: If necessary, refer to your X server documentation for more information about completing this procedure. Depending on the X server software that you are using, you may need to complete the tasks in a different order. |
Start the X server software.
Configure the security settings of the X server software to permit remote hosts to display X applications on the local system.
Connect to the remote system where you want to install the software and start a terminal session on that system, for example, an X terminal (xterm
).
If you are not logged in as the root
user on the remote system, enter the following command to switch user to root
:
$ su - root password: #
Each system must meet the following minimum hardware requirements:
512 MB of physical RAM
1 GB of swap space (or twice the size of RAM)
On systems with 2 GB or more of RAM, the swap space can be between one and two times the size of RAM.
400 MB of disk space in the /tmp
directory
Up to 4 GB of disk space for the Oracle software, depending on the installation type
1.2 GB of disk space for a preconfigured database that uses file system storage (optional)
Note: The disk space requirement for databases that use Automatic Storage Management (ASM) or raw device storage is described later in this chapter. |
Additional disk space, either on a file system or in an ASM disk group, is required for the flash recovery area if you choose to configure automated backups.
To ensure that each system meets these requirements, follow these steps:
To determine the physical RAM size, enter the following command:
# /usr/sbin/prtconf | grep "Memory size"
If the size of the physical RAM installed in the system is less than the required size, you must install more memory before continuing.
To determine the size of the configured swap space, enter the following command:
# /usr/sbin/swap -s
If necessary, refer to your operating system documentation for information about how to configure additional swap space.
To determine whether the system architecture can run the software, enter the following command:
# /bin/isainfo -kv
Verify that this command displays the correct output:
SPARC systems:
64-bit sparcv9 kernel modules
x86 systems:
32-bit i386 kernel modules
Note: If you do not see the expected output, you cannot install the software on this system. |
Check that you have the networking hardware and internet protocol (IP) addresses required for an Oracle Real Application Clusters installation.
Note: For the most up-to-date information about supported network protocols and hardware for RAC installations, refer to the Certify pages on the OracleMetaLink Web site:http://metalink.oracle.com |
Network Hardware Requirements
Each node in the cluster must meet the following requirements:
Each node must have at least two network adapters; one for the public network interface and one for the private network interface (the interconnect).
The interface names associated with the network adapters for each network must be the same on all nodes.
For increased reliability, you can configure redundant public and private network adapters for each node.
For the public network, each network adapter must support TCP/IP.
For the private network, Oracle supports the following interconnect protocols and hardware:
User datagram protocol (UDP) using high-speed network adapters and switches that support TCP/IP (Gigabit Ethernet or better recommended)
(SPARC systems only) Remote shared memory (RSM) using peripheral component interconnect-scalable coherent interface (PCI-SCI) adapters and SCI switches
Note: UDP is the default interconnect protocol for RAC and TCP is the interconnect protocol for Oracle CRS. |
IP Address Requirements
Before starting the installation, you must identify or obtain the following IP addresses for each node:
An IP address and an associated host name registered in the domain name service (DNS) for each public network interface
One unused virtual IP address and an associated virtual host name registered in DNS that you will configure for the primary public network interface
The virtual IP address must be in the same subnet as the associated public interface. After installation, you can configure clients to use the virtual host name or IP address. If a node fails, its virtual IP address fails over to another node.
A private IP address and optional host name for each private interface
Note: If you are using Sun Cluster 3.1 (SPARC systems only), you must use the private host name and IP address configured for each node during the Sun Cluster installation. The default private host name for each Sun Cluster node isclusternode nodeid -priv . Do not specify this host name or IP address in the /etc/hosts or /etc/inet/hosts file.
If you are not using Sun Cluster 3.1, you must configure private host names and IP addresses for each node. |
Oracle recommends that you use non-routable IP addresses for the private interfaces, for example: 10.*.*.* or 192.168.*.*. If you are not using Sun Cluster 3.1, you can use the /etc/hosts
file on each node to associate private host names with private IP addresses.
For example, if each node has two public and two private interfaces, you might have the following host names and IP addresses on one of the nodes (rac1
) and similar host names and IP addresses on the other nodes:
Host Name | Type | IP Address | Registered In |
---|---|---|---|
rac1.mydomain.com
|
Public | 143.47.43.100 | DNS |
rac1-2.mydomain.com
|
Public | 143.46.51.101 | DNS |
rac1-vip.mydomain.com
|
Virtual | 143.47.43.104 | DNS |
rac1-priv1
|
Private | 10.0.0.1 | /etc/hosts
|
rac1-priv2
|
Private | 10.0.0.2 | /etc/hosts
|
Checking the Network Requirements
To verify that each node meets the requirements, follow these steps:
If necessary, install the network adapters for the public and private networks and configure them with either public or private IP addresses.
Register the host names and IP addresses for the public network interfaces in DNS.
For each node, register one virtual host name and IP address in DNS.
For each private interface on every node, add a line similar to the following to the /etc/hosts
file on all nodes, specifying the private IP address and associated private host name:
10.0.0.1 rac1-priv1
To identify the interface name and associated IP address for every network adapter, enter the following command:
# /usr/sbin/ifconfig -a
From the output, identify the interface name and IP address for all network adapters that you want to specify as public or private network interfaces.
If you are using Sun Cluster 3.1, enter the following command to display private host names:
# /usr/cluster/bin/scconf -p
Note: When you install Oracle CRS and RAC, you will require this information. |
Refer to the following section for information about checking the software requirements.
Note: The Oracle Universal Installer performs checks on your system to verify that it meets the requirements listed for your platform. To ensure that these checks pass, verify the requirements before you start the Installer. |
Check that the required software and patches are installed on the system.
Check for Required Software
Depending on the products that you intend to install, verify that the following software is installed on the system. The procedure following the table describes how to check these requirements.
Installation Type or Product | Requirement |
---|---|
All installations | Operating system versions:
SPARC systems: Solaris 8 or Solaris 9, 64-bit x86 systems: Solaris 9 |
Operating system packages:
SPARC and x86 systems: SUNWarc SUNWbtool SUNWhea SUNWlibC SUNWlibm SUNWlibms SUNWsprot SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt SPARC systems only: SUNWsprox Note: You might also require additional font packages for Java, depending on your locale. Refer to the following Web site for more information: http://java.sun.com/j2se/1.4.2/font-requirements.html |
|
Oracle Spatial | Motif RunTime Kit:
Note: This software is required only to build the sample programs. |
Real Application Clusters | Sun Cluster 3.1 (SPARC systems only)
Note: Sun Cluster is supported for use with RAC on SPARC systems but it is not required. |
Oracle Messaging Gateway | Oracle Messaging Gateway supports the integration of Oracle Streams Advanced Queuing (AQ) with the following software: |
PL/SQL native compilation, Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, Oracle XML Developer's Kit (XDK) |
Sun ONE Studio 8 (C and C++ 5.5) |
Oracle JDBC/OCI Drivers | You can use the following optional JDK versions with the Oracle JDBC/OCI drivers, however they are not required for the installation:
Note: JDK 1.4.2_01 (SPARC) or 1.4.2_04 (x86) is installed with this release. |
Oracle Transparent Gateway for Sybase (SPARC only) | Either of the following:
|
Oracle Transparent Gateway for Informix (SPARC only) | One of the following:
Note: This version of the gateway does not support Informix SE. |
Oracle Transparent Gateway for Ingres (SPARC only) | Ingres II version 2.0, 2.5, or 2.6 |
Oracle Transparent Gateway for Teradata (SPARC only) | NCR Teradata ODBC Driver v02.04.00.00 |
To ensure that the system meets these requirements, follow these steps:
To determine which version of Solaris is installed, enter the following command:
# uname -r 5.9
In this example, the version shown is Solaris 9 (5.9). If necessary, refer to your operating system documentation for information about upgrading the operating system.
To determine whether the required packages are installed, enter a command similar to the following:
# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibC SUNWlibm SUNWlibms SUNWsprot \ SUNWsprox SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt
If a package is not installed, then install it. Refer to your operating system or software documentation for information about installing packages.
Depending on the products that you intend to install, verify that the following patches are installed on the system. The procedure following the table describes how to check these requirements.
Note: The patch versions shown in the following table are minimum versions. Higher versions of the same patches are also supported. |
To ensure that the system meets these requirements, follow these steps:
To determine whether an operating system patch is installed, enter a command similar to the following:
# /usr/sbin/patchadd -p | grep patch_number
If an operating system patch is not installed, download it from the following Web site and install it:
http://sunsolve.sun.com
If you require a CSD or a SupportPac for WebSphere MQ or MQSeries, refer to the following Web site for download and installation information:
http://www.ibm.com/software/integration/mqfamily/support/summary/sun.html
Depending on whether this is the first time Oracle software is being installed on this system and on the products that you are installing, you may need to create several UNIX groups and a UNIX user.
The following UNIX groups and user are required if you are installing Oracle Database:
You must create this group the first time you install Oracle Database software on the system. It identifies UNIX users that have database administrative privileges (the SYSDBA privilege). The default name for this group is dba
.
If you want to specify a group name other than the default dba
group, you must choose the Custom installation type to install the software or start the Installer as a user that is not a member of this group. In this case, the Installer prompts you to specify the name of this group.
This is an optional group. Create this group if you want a separate group of UNIX users to have a limited set of database administrative privileges (the SYSOPER privilege). By default, members of the OSDBA group also have the SYSOPER privilege.
If you want to specify a separate OSOPER group, other than the default dba
group, you must choose the Custom installation type to install the software or start the Installer as a user that is not a member of the dba
group. In this case, the Installer prompts you to specify the name of this group. The usual name chosen for this group is oper
.
You must verify that the unprivileged user nobody
exists on the system. The nobody
user must own the external jobs (extjob
) executable after the installation.
The following UNIX group and user are required for all installations:
The Oracle Inventory group (oinstall
)
You must create this group the first time you install Oracle software on the system. The usual name chosen for this group is oinstall
. This group owns the Oracle inventory, which is a catalog of all Oracle software installed on the system.
Note: If Oracle software is already installed on the system, the existing Oracle Inventory group must be the primary group of the UNIX user that you use to install new Oracle software. The following sections describe how to identify an existing Oracle Inventory group. |
The Oracle software owner user (oracle
)
You must create this user the first time you install Oracle software on the system. This user owns all of the software installed during the installation. The usual name chosen for this user is oracle
. This user must have the Oracle Inventory group as its primary group. It must also have the OSDBA and OSOPER groups as a secondary groups.
A single Oracle Inventory group is required for all installations of Oracle software on the system. After the first installation of Oracle software, you must use the same Oracle Inventory group for all subsequent Oracle software installations on that system. However, you can choose to create different Oracle software owner users, OSDBA groups, and OSOPER groups (other than oracle
, dba
, and oper
) for separate installations. By using different groups for different installations, members of these different groups have DBA privileges only on the associated databases rather than on all databases on the system.
See Also: The Oracle Database Administrator's Reference for UNIX Systems and the Oracle Database Administrator's Guide contain more information about the OSDBA and OSOPER groups and the SYSDBA and SYSOPER privileges. |
The following sections describe how to create the required UNIX user and groups.
Note: The following sections describe how to create local users and groups. As an alternative to creating local users and groups, you could create the appropriate users and groups in a directory service, for example, Network Information Services (NIS). For information about using directory services, contact your system administrator or refer to your operating system documentation. |
You must create the Oracle Inventory group if it does not already exist. The following subsections describe how to determine the Oracle Inventory group name, if it exists, and how to create it if necessary.
Determine Whether the Oracle Inventory Group Exists
When you install Oracle software on the system for the first time, the Installer creates the oraInst.loc
file. This file identifies the name of the Oracle Inventory group and the path of the Oracle Inventory directory. To determine whether the Oracle Inventory group exists, enter the following command:
# more /var/opt/oracle/oraInst.loc
If the oraInst.loc
file exists, the output from this command is similar to the following:
inventory_loc=/u01/app/oracle/oraInventory inst_group=oinstall
The inst_group
parameter shows the name of the Oracle Inventory group (oinstall
).
Create the Oracle Inventory Group
If the oraInst.loc
file does not exist, enter the following command to create the oinstall
group:
# /usr/sbin/groupadd oinstall
You must create an OSDBA group in the following circumstances:
An OSDBA group does not exist, for example, if this is the first installation of Oracle Database software on the system
An OSDBA group exists, but you want to give a different group of UNIX users database administrative privileges in a new Oracle installation
If the OSDBA group does not exist or if you require a new OSDBA group, enter the following command to create the dba
group. Use the group name dba
unless a group with that name already exists.
# /usr/sbin/groupadd dba
Create an OSOPER group only if you want to identify a group of UNIX users with a limited set of database administrative privileges (SYSOPER operator privileges). For most installations, it is sufficient to create only the OSDBA group. If you want to use an OSOPER group, you must create it in the following circumstances:
If an OSOPER group does not exist, for example, if this is the first installation of Oracle Database software on the system
If an OSOPER group exists, but you want to give a different group of UNIX users database operator privileges in a new Oracle installation
If you require an new OSOPER group, enter the following command to create the oper
group. Use the group name oper
unless a group with that name already exists.
# /usr/sbin/groupadd oper
Before installing the software, verify that the UNIX user nobody
exists on the system:
To determine whether the user exists, enter the following command:
# id nobody
If this command displays information about the nobody
user, you do not have to create that user.
If the nobody
user does not exist, enter the following command to create it:
# /usr/sbin/useradd nobody
Repeat this procedure on all of the other cluster nodes.
Note: You must complete the following procedures only if you are using local users and groups. If you are using users and groups defined in a directory service such as NIS, they are already identical on each cluster node. |
The Oracle software owner user and the Oracle Inventory, OSDBA, and OSOPER groups must exist and be identical on all cluster nodes. To create these identical users and groups, you must identify the user ID and group IDs assigned them on the node where you created them, then create the user and groups with the same name and ID on the other cluster nodes.
Identifying the User and Group IDs
To determine the user ID (UID) of the Oracle software owner user and the group IDs (GID) of the Oracle Inventory, OSDBA, and OSOPER groups, follow these steps:
Enter following command:
# id -a oracle
The output from this command is similar to the following:
uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)
From the output, identify the UID for the oracle
user and the GIDs for the groups to which it belongs.
Create the User and Groups on the Other Cluster Nodes
To create the user and groups on the other cluster nodes, repeat the following procedure on each node:
Log in to the next cluster node as root
.
Enter commands similar to the following to create the oinstall
and dba
groups, and if required, the oper
group. Use the -g
option to specify the correct GID for each group.
# /usr/sbin/groupadd -g 200 oinstall # /usr/sbin/groupadd -g 201 dba # /usr/sbin/groupadd -g 202 oper
Note: If the group already exists, use thegroupmod command to modify it if necessary. If you cannot use the same group ID for a particular group on this node, view the /etc/group file on all nodes to identify a group ID that is available on every node. You must then specify that ID for the group on all of the nodes.
|
To create the oracle
user, enter a command similar to the following:
# /usr/sbin/useradd -u 200 -g oinstall -G dba[,oper] oracle
In this command:
The -u
option specifies the user ID, which must be the user ID that you identified in the previous subsection
The -g
option specifies the primary group, which must be the Oracle Inventory group, for example oinstall
The -G
option specifies the secondary groups, which must include the OSDBA group and if required, the OSOPER group, for example dba
or dba,oper
Note: If the user already exists, use theusermod command to modify it if necessary. If you cannot use the same user ID for the oracle user on this node, view the /etc/passwd file on all nodes to identify a user ID that is available on every node. You must then specify that ID for the user on all of the nodes.
|
Set the password of the oracle
user:
# passwd oracle
Note: This section describes how to set up user equivalence forrcp , which the Installer uses when copying Oracle software to the other cluster nodes. If you prefer, you can configure the Secure Shell (SSH) tool suite, so that the Installer uses scp instead of rcp . Refer to the SSH documentation for information about setting up user equivalence for scp .
|
Before you install and use Oracle Real Application clusters, you must set up user equivalence on all cluster nodes, as follows:
On all cluster nodes, edit the /etc/hosts.equiv
file in any text editor and add entries similar to the following for all nodes in the cluster:
node1-public oracle node1-public.domain oracle node2-public oracle node2-public.domain oracle . . .
In this example:
noden_public
is the host name associated with the primary public network interface
domain
is the domain name of the system, for example mydomain.com
Note: Alternatively, you can create a.rhosts file using the same format in the oracle user's home directory on all nodes in the cluster.
|
Refer to the following section for information about configuring the system kernel parameters and shell limits.
Note: The kernel parameter values shown in this section are recommended values only. For production database systems, Oracle recommends that you tune these values to optimize the performance of the system. Refer to your operating system documentation for more information about tuning kernel parameters. |
On all cluster nodes, verify that the kernel parameters shown in the following table are set to values greater than or equal to the recommended value shown. The procedure following the table describes how to verify and set the values.
Parameter | Recommended Value |
---|---|
noexec_user_stack (SPARC only) | 1 |
semsys:seminfo_semmni | 100 |
semsys:seminfo_semmns | 1024 |
semsys:seminfo_semmsl | 256 |
semsys:seminfo_semvmx | 32767 |
shmsys:shminfo_shmmax | 4294967295 |
shmsys:shminfo_shmminFoot 1 | 1 |
shmsys:shminfo_shmmni | 100 |
shmsys:shminfo_shmsegFootref 1 | 10 |
Note: If the current value for any parameter is higher than the value listed in this table, do not change the value of that parameter. |
To view the current value specified for these kernel parameters, and to change them if necessary, follow these steps:
To view the current values of these parameters, enter the following commands:
# grep noexec_user_stack /etc/system # /usr/sbin/sysdef | grep SEM # /usr/sbin/sysdef | grep SHM
If you must change any of the current values, follow these steps:
Create a backup copy of the /etc/system
file, for example:
# cp /etc/system /etc/system.orig
Open the /etc/system
file in any text editor and, if necessary, add lines similar to the following (edit the lines if the file already contains them):
set noexec_user_stack=1 set semsys:seminfo_semmni=100 set semsys:seminfo_semmns=1024 set semsys:seminfo_semmsl=256 set semsys:seminfo_semvmx=32767 set shmsys:shminfo_shmmax=4294967295 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=10
Enter the following command to restart the system:
# /usr/sbin/reboot
When the system restarts, log in and switch user to root
.
Repeat this procedure on all other cluster nodes.
You must identify or create four directories for the Oracle software, as follows:
Oracle base directory
Oracle Inventory directory
CRS home directory
Oracle home directory
The following subsections describe the requirements for these directories.
The Oracle base directory acts as a top-level directory for Oracle software installations. It is analogous to the C:\Oracle
directory used for Oracle software installations on Windows systems. On UNIX systems, the Optimal Flexible Architecture (OFA) guidelines recommend that you use a path similar to the following for the Oracle base directory:
/mount_point/app/oracle_sw_owner
mount_point
is the mount point directory for the file system that will contain the Oracle software.
The examples in this guide use /u01
for the mount point directory. However, you could choose another mount point directory, /oracle
or /opt/oracle
for example.
oracle_sw_owner
is the UNIX user name of the Oracle software owner, for example oracle
.
You can use the same Oracle base directory for more than one installation or you can create separate Oracle base directories for different installations. If different UNIX users install Oracle software on the same system, each user must create a separate Oracle base directory. The following example Oracle base directories could all exist on the same system:
/u01/app/oracle /u01/app/orauser /opt/oracle/app/oracle
The following sections describe how to identify existing Oracle base directories that might be suitable for your installation and how to create a new Oracle base directory if necessary.
Regardless of whether you create a new Oracle base directory or decide to use an existing one, you must set the ORACLE_BASE environment variable to specify the full path to this directory.
Note: The Oracle base directory can be on a local file system, a supported cluster file system, or on an NFS file system on a certified NAS device. |
The Oracle Inventory directory (oraInventory
) stores an inventory of all software installed on the system. It is required by, and shared by, all Oracle software installations on a single system. The first time you install Oracle software on a system, the Installer prompts you to specify the path to this directory. If you are installing the software on a local file system, Oracle recommends that you choose the following path:
oracle_base/oraInventory
If the Oracle base directory is on a cluster file system or an NFS file system on a NAS device, you must specify a path for the Oracle Inventory directory on a local file system. The Oracle base directory must be on a local file system to enable all of the nodes to have separate inventories.
The Installer creates the directory that you specify and sets the correct owner, group, and permissions on it. You do not need to create it.
Note: All Oracle software installations rely on this directory. Make sure that you back it up regularly.Do not delete this directory unless you have completely removed all Oracle software from the system. |
CRS Home Directory
The CRS home directory is the directory where you choose to install the software for Oracle Cluster Ready Services. You must install CRS in a separate home directory. When you run the Installer, it prompts you to specify the path to this directory, as well as a name that identifies it. Oracle recommends that you specify a path similar to the following for the CRS home directory:
/u01/crs/oracle/product/10.1.0/crs
Note: Because you must change the permissions of all of the parent directories of the CRS home directory after installing the software to grant write access only to theroot user, the CRS home directory must not be a subdirectory of the Oracle base directory.
|
The Oracle home directory is the directory where you choose to install the software for a particular Oracle product. You must install different Oracle products, or different releases of the same Oracle product, in separate Oracle home directories. When you run the Installer, it prompts you to specify the path to this directory, as well as a name that identifies it. The directory that you specify must be a subdirectory of the Oracle base directory. Oracle recommends that you specify a path similar to the following for the Oracle home directory:
oracle_base/product/10.1.0/db_1
The Installer creates the directory path that you specify under the Oracle base directory. It also sets the correct owner, group, and permissions on it. You do not need to create this directory.
Before starting the installation, you must either identify an existing Oracle base directory or if required, create a new one. This section contains information about the following:
Note: You can choose to create a new Oracle base directory, even if other Oracle base directories exist on the system. |
Identifying an Existing Oracle Base Directory
Existing Oracle base directories might not have paths that comply with OFA guidelines. However, if you identify an existing Oracle Inventory directory or existing Oracle home directories, you can usually identify the Oracle base directories, as follows:
Identify an existing Oracle Inventory directory
Enter the following command on all cluster nodes to view the contents of the oraInst.loc
file:
# more /var/opt/oracle/oraInst.loc
If the oraInst.loc
file exists, the output from this command is similar to the following:
inventory_loc=/u01/app/oracle/oraInventory inst_group=oinstall
The inventory_loc
parameter identifies the Oracle Inventory directory (oraInventory
) on that system. The parent directory of the oraInventory
directory is typically an Oracle base directory. In the previous example, /u01/app/oracle
is an Oracle base directory.
Identify existing Oracle home directories
Enter the following command on all cluster nodes to view the contents of the oratab
file:
# more /var/opt/oracle/oratab
If the oratab
file exists, it contains lines similar to the following:
*:/u03/app/oracle/product/10.1.0/db_1:N *:/opt/orauser/infra_904:N *:/oracle/9.2.0:N
The directory paths specified on each line identify Oracle home directories. Directory paths that end with the user name of the Oracle software owner that you want to use are valid choices for an Oracle base directory. If you intend to use the oracle
user to install the software, you could choose one of the following directories from the previous example:
/u03/app/oracle /oracle
Note: If possible, choose a directory path similar to the first (/u03/app/oracle ). This path complies with the OFA guidelines.
|
Before deciding to use an existing Oracle base directory for this installation, make sure that it satisfies the following conditions:
It should not be on the same file system as the operating system.
It must have an identical path on all cluster nodes or it must be on a supported cluster file system.
If you are not using a cluster file system, create identical Oracle base directories on the other nodes.
It must have sufficient free disk space on all cluster nodes, as follows:
To determine the free disk space on the file system where the Oracle base directory is located, enter the following command:
# df -k oracle_base_path
To continue:
If an Oracle base directory exists and you want to use it, refer to the "Create the CRS Home Directory" section.
When you are configuring the oracle
user's environment later in this chapter, set the ORACLE_BASE environment variable to specify the directory you chose.
If an Oracle base directory does not exist on the system or if you want to create a new Oracle base directory, refer to the following section.
Creating a New Oracle Base Directory
Before you create a new Oracle base directory, you must identify an appropriate file system with sufficient free disk space, as follows:
To identify an appropriate file system, follow these steps:
Use the df -k
command to determine the free disk space on each mounted file system.
From the display, identify a file system that has appropriate free space.
Note: The file system can be a local file system, a supported cluster file system, or an NFS file system on a certified NAS device. |
The path to the Oracle base directory must be the same on all nodes.
Note the name of the mount point directory for the file system that you identified.
To create the Oracle base directory and specify the correct owner, group, and permissions for it, follow these steps:
Enter commands similar to the following to create the recommended subdirectories in the mount point directory that you identified and set the appropriate owner, group, and permissions on them:
# mkdir -p /mount_point/app/oracle_sw_owner # chown -R oracle:oinstall /mount_point/app/oracle_sw_owner # chmod -R 775 /mount_point/app/oracle_sw_owner
If the mount point you identified is /u01
and oracle
is the user name of the Oracle software owner, the recommended Oracle base directory path is as follows:
/u01/app/oracle
If necessary, repeat the commands listed in the previous step to create the same directory on the other cluster nodes.
When you are configuring the oracle
user's environment later in this chapter, set the ORACLE_BASE environment variable to specify this directory.
You must create a CRS home directory before installing Oracle CRS. You can create the CRS home directory on the same file system as the Oracle base directory, or you can choose a different file system for this directory. If you choose the same file system as the Oracle base directory, you must not use a subdirectory of the Oracle base directory as the CRS home directory.
To identify an appropriate file system, follow these steps:
Use the df -k
command to determine the free disk space on each mounted file system.
From the display, identify a file system that has at least 1 MB of free disk space.
If you are using the same file system for the Oracle base directory, this 1 MB of disk space is additional to the free disk space requirement that you identified previously.
Note: The file system can be a local file system, a supported cluster file system, or an NFS file system on a certified NAS device. |
The path to the CRS home directory must be the same on all nodes.
Note the name of the mount point directory for the file system that you identified.
To create the CRS home directory and specify the correct owner, group, and permissions for it, follow these steps:
Enter commands similar to the following to create the recommended subdirectories in the mount point directory that you identified and set the appropriate owner, group, and permissions on them:
# mkdir -p /mount_point/crs/oracle_sw_owner/product/10.1.0/crs # chown -R oracle:oinstall /mount_point/crs/oracle_sw_owner # chmod -R 775 /mount_point/crs/oracle_sw_owner
If the mount point you identified is /u01
and oracle
is the user name of the Oracle software owner, the recommended CRS home directory path is as follows:
/u01/crs/oracle/product/10.1.0/crs
If necessary, repeat the commands listed in the previous step to create the same directory on the other cluster nodes.
When you are installing Oracle CRS, set the ORACLE_HOME environment variable to specify this directory.
Note: During the installation, before you run theroot.sh script, you must change the permissions on the parent directories of the CRS home directory to permit only the root user to write to those directories.
|
The following table shows the storage options supported for storing Oracle Cluster Ready Services (CRS) files, Oracle database files, and Oracle database recovery files. Oracle database files include datafiles, control files, redo log files, the server parameter file, and the password file. Oracle CRS files include the Oracle Cluster Registry (OCR) and the CRS voting disk.
For all installations, you must choose the storage option that you want to use for Oracle CRS files and Oracle database files. If you want to enable automated backups during the installation, you must also choose the storage option that you want to use for recovery files (the flash recovery area). You do not have to use the same storage option for each file type.
Note: For the most up-to-date information about supported storage options for RAC installations, refer to the Certify pages on the OracleMetaLink Web site:http://metalink.oracle.com |
Storage Option | File Types Supported | ||
---|---|---|---|
CRS | Database | Recovery | |
Automatic Storage Management | No | Yes | Yes |
Cluster file system
Note: Requires a supported cluster file system |
Yes | Yes | Yes |
NFS file system
Note: Currently supported only with Fujitsu PRIMECLUSTER and a certified NAS device (SPARC only) |
Yes | Yes | Yes |
Shared raw logical volumes (SPARC only) | Yes | Yes | No |
Shared raw partitions | Yes | Yes | No |
Use the following guidelines when choosing the storage options that you want to use for each file type:
You can choose any combination of the supported storage options for each file type as long as you satisfy any requirements listed for the chosen storage options.
Oracle recommends that you choose ASM as the storage option for database and recovery files.
For Standard Edition installations, ASM is the only supported storage option for database or recovery files.
You cannot use Automatic Storage Management to store Oracle CRS files, because these files must be accessible before any Oracle instance starts.
For information about how to configure disk storage before you start the installation, refer to one of the following sections depending on your choice:
To use a file system for Oracle CRS, database, or recovery file storage, refer to the "Create Directories for Oracle CRS, Database, or Recovery Files" section.
To use ASM for database or recovery file storage, refer to the "Configure Disks for Automatic Storage Management" section.
To use raw devices (partitions or logical volumes) for Oracle CRS or database file storage, refer to the "Configure Raw Partitions or Raw Logical Volumes" section.
If you decide to place the Oracle CRS, database, or recovery files on a file system, use the following guidelines when deciding where to place them.
Guidelines for Placing Oracle CRS Files on a File System
The Installer does not suggest a default location for the Oracle Cluster Registry (OCR) or the Oracle CRS voting disk. If you choose to create these files on a file system, use the following guidelines when deciding where to place them:
You must choose a shared file system on shared disks, for example:
A supported cluster file system
An NFS file system on a certified NAS device
Note: NAS storage is currently supported only if you are using Fujitsu PRIMECLUSTER and a certified NAS device. |
It must have at least 100 MB of free disk space for the OCR and 20 MB of free disk space for the CRS voting disk.
For improved reliability, you should choose a file system on a highly available storage device, for example, a RAID device that implements mirroring.
If you are placing the Oracle Cluster Ready Services software on a shared file system, you can use the same file system for these files.
The oracle
user must have write permissions to create the files in the path that you specify.
Note: If you are upgrading from Oracle9i Release 2, you can continue to use the raw device or shared file that you used for the SRVM configuration repository instead of creating a new file for the OCR. |
Guidelines for Placing Oracle Database Files on a File System
If you choose to place the Oracle database files on a file system, use the following guidelines when deciding where to place them:
You must choose a shared file system on shared disks, for example:
A supported cluster file system
An NFS file system on a certified NAS device
Note: NAS storage is currently supported only if you are using Fujitsu PRIMECLUSTER and a certified NAS device. |
The default path suggested by the Installer for the database file directory is a subdirectory of the Oracle base directory. You can choose this path only if you are using an Oracle base directory that is on a shared file system.
This default location is not recommended for production databases.
You can choose either a single file system or more than one file system to store the database files:
If you want to use a single file system, choose a file system on a physical device that is dedicated to the database.
For best performance and reliability, choose a RAID device or a logical volume on more than one physical device and implement the stripe-and-mirror-everything (SAME) methodology.
If you want to use more than one file system, choose file systems on separate physical devices that are dedicated to the database.
This method enables you to distribute physical I/O and create separate control files on different devices for increased reliability. It also enables you to fully implement the OFA guidelines. You must choose either the Advanced database creation option or the Custom installation type during the installation to implement this method.
If you intend to create a preconfigured database during the installation, the file system (or file systems) that you choose must have at least 1.2 GB of free disk space.
For production databases, you must estimate the disk space requirement depending on the use that you want to make of the database.
For optimum performance, the file systems that you choose should be on physical devices that are used only by the database.
The oracle
user must have write permissions to create the files in the path that you specify.
Guidelines for Placing Oracle Recovery Files on a File System
Note: You must choose a location for recovery files only if you intend to enable automated backups during the installation. |
If you choose to place the Oracle recovery files on a file system, use the following guidelines when deciding where to place them:
To prevent disk failure from making both the database files and the recovery files unavailable, place the recovery files in a file system on a different physical disk from the database files.
Note: Alternatively use an ASM disk group with a normal or high redundancy level for either or both file types. |
You must choose a shared file system on shared disks, for example:
A supported cluster file system
An NFS file system on a certified NAS device
Note: NAS storage is currently supported only if you are using Fujitsu PRIMECLUSTER and a certified NAS device. |
The file system that you choose should have at least 2 GB of free disk space.
The disk space requirement is the default disk quota configured for the flash recovery area (specified by the DB_RECOVERY_FILE_DEST_SIZE initialization parameter).
If you choose the Custom installation type or the Advanced database configuration option, you can specify a different disk quota value. After you create the database, you can also use Oracle Enterprise Manager Grid Control or Database Control to specify a different value.
For more information about sizing the flash recovery area, refer to the Oracle Backup and Recovery Basics manual.
The default path suggested by the Installer for the flash recovery area is a subdirectory of the Oracle base directory. You can choose this path only if you are using an Oracle base directory that is on a shared file system.
This default location is not recommended for production databases.
The oracle
user must have write permissions to create the files in the path that you specify.
Note: You must complete this procedure only if you want to place the Oracle CRS, database, or recovery files on a separate file system to the Oracle base directory. |
To create directories for the Oracle CRS, database, or recovery files on separate file systems to the Oracle base directory, follow these steps:
If necessary, configure the shared file systems that you want to use and mount them on each node.
Note: The mount point that you use for the file system must be identical on each node. Make sure that the file systems are configured to mount automatically when a node restarts. |
Use the df -k
command to determine the free disk space on each mounted file system.
From the display, identify the file systems that you want to use:
File Type | File System Requirements |
---|---|
CRS files | Choose a file system with at least 120 MB of free disk space |
Database files | Choose either:
|
Recovery files | Choose a file system with at least 2 GB of free disk space. |
If you are using the same file system for more than one type of file, add the disk space requirements for each type to determine the total disk space requirement.
Note the names of the mount point directories for the file systems that you identified.
Enter commands similar to the following to create the recommended subdirectories in each of the mount point directories and set the appropriate owner, group, and permissions on them:
CRS file directory:
# mkdir /mount_point/oracrs # chown oracle:oinstall /mount_point/oracrs # chmod 775 /mount_point/oracrs
Database file directory:
# mkdir /mount_point/oradata # chown oracle:oinstall /mount_point/oradata # chmod 775 /mount_point/oradata
Recovery file directory (flash recovery area):
# mkdir /mount_point/flash_recovery_area # chown oracle:oinstall /mount_point/flash_recovery_area # chmod 775 /mount_point/flash_recovery_area
If you also want to use ASM or raw devices for storage, refer to one of the following sections:
Otherwise, refer to the "Verify that the Cluster Software is Configured and Running" section.
This section describes how to configure disks for use with ASM. Before you configure the disks, you must determine the number of disks and the amount of free disk space that you require. The following sections describe how to identify the requirements and configure the disks on each platform:
Note: Although this section refers to disks, you can also use zero-padded files on a certified NAS storage device in an ASM disk group. Refer to the Oracle Database Installation Guide for UNIX Systems for information about creating and configuring NAS-based files for use in an ASM disk group. |
To identify the storage requirements for using ASM, you must determine how many devices and the amount of free disk space that you require. To complete this task, follow these steps:
Determine whether you want to use ASM for Oracle database files, recovery files, or both.
Note: You do not have to use the same storage mechanism for database files and recovery files. You can use the file system for one file type and ASM for the other.For RAC installations, if you choose to enable automated backups and you do not have a shared file system available, you must choose ASM for recovery file storage. |
If you enable automated backups during the installation, you can choose ASM as the storage mechanism for recovery files by specifying an ASM disk group for the flash recovery area. Depending on how you choose to create a database during the installation, you have the following options:
If you select an installation method that runs DBCA in interactive mode, by choosing the Advanced database configuration option for example, you can decide whether you want to use the same ASM disk group for database files and recovery files, or you can choose to use different disk groups for each file type.
The same choice is available to you if you use DBCA after the installation to create a database.
If you select an installation method that runs DBCA in non-interactive mode, you must use the same ASM disk group for database files and recovery files.
Choose the ASM redundancy level that you want to use for the ASM disk group.
The redundancy level that you choose for the ASM disk group determines how ASM mirrors files in the disk group and determines the number of disks and amount of disk space that you require, as follows:
External redundancy
An external redundancy disk group requires a minimum of one disk device. The effective disk space in an external redundancy disk group is the sum of the disk space in all of its devices.
Because ASM does not mirror data in an external redundancy disk group, Oracle recommends that you use only RAID or similar devices that provide their own data protection mechanisms as disk devices in this type of disk group.
Normal redundancy
In a normal redundancy disk group, ASM uses two-way mirroring by default, to increase performance and reliability. A normal redundancy disk group requires a minimum of two disk devices (or two failure groups). The effective disk space in a normal redundancy disk group is half the sum of the disk space in all of its devices.
For most installations, Oracle recommends that you use normal redundancy disk groups.
High redundancy
In a high redundancy disk group, ASM uses three-way mirroring to increase performance and provide the highest level of reliability. A high redundancy disk group requires a minimum of three disk devices (or three failure groups). The effective disk space in a high redundancy disk group is one-third the sum of the disk space in all of its devices.
While high redundancy disk groups do provide a high level of data protection, you must consider the higher cost of additional storage devices before deciding to use this redundancy level.
Determine the total amount of disk space that you require for the database files and recovery files.
Use the following table to determine the minimum number of disks and the minimum disk space requirements for the installation:
Redundancy Level | Minimum Number of Disks | Database Files | Recovery Files | Both File Types |
---|---|---|---|---|
External | 1 | 1.15 GB | 2.3 GB | 3.45 GB |
Normal | 2 | 2.3 GB | 4.6 GB | 6.9 GB |
High | 3 | 3.45 GB | 6.9 GB | 10.35 GB |
For RAC installations, you must also add additional disk space for the ASM metadata. You can use the following formula to calculate the additional disk space requirements (in MB):
15 + (2 * number_of_disks) + (126 * number_of_ASM_instances)
For example, for a four-node RAC installation, using three disks in a high redundancy disk group, you require an additional 525 MB of disk space:
15 + (2 * 3) + (126 * 4) = 525
If an ASM instance is already running on the system, you can use an existing disk group to meet these storage requirements. If necessary, you can add disks to an existing disk group during the installation.
The following section describes how to identify existing disk groups and determine the free disk space that they contain.
Optionally identify failure groups for the ASM disk group devices.
Note: You need to complete this step only if you intend to use an installation method that runs DBCA in interactive mode, for example, if you intend to choose the Custom installation type or the Advanced database configuration option. Other installation types do not enable you to specify failure groups. |
If you intend to use a normal or high redundancy disk group, you can further protect your database against hardware failure by associating a set of disk devices in a custom failure group. By default, each device comprises its own failure group. However, if two disk devices in a normal redundancy disk group are attached to the same SCSI controller, the disk group becomes unavailable if the controller fails. The controller in this example is a single point of failure.
To protect against failures of this type, you could use two SCSI controllers, each with two disks, and define a failure group for the disks attached to each controller. This configuration would enable the disk group to tolerate the failure of one SCSI controller.
Note: If you define custom failure groups, you must specify a minimum of two failure groups for normal redundancy disk groups and three failure groups for high redundancy disk groups. |
If you are sure that a suitable disk group does not exist on the system, install or identify appropriate disk devices to add to a new disk group. Use the following guidelines when identifying appropriate disk devices:
All of the devices in an ASM disk group should be the same size and have the same performance characteristics.
Do not specify more than one partition on a single physical disk as a disk group device. ASM expects each disk group device to be on a separate physical disk.
Although you can specify a logical volume as a device in an ASM disk group, Oracle does not recommend their use. Logical volume managers can hide the physical disk architecture, preventing ASM from optimizing I/O across the physical devices.
For information about completing this task, refer to the "Configuring Disks for ASM" section.
If you want to store either database or recovery files in an existing ASM disk group, you have the following choices, depending on the installation method that you select:
If you select an installation method that runs DBCA in interactive mode, by choosing the Advanced database configuration option for example, you can decide whether you want to create a new disk group or use an existing one.
The same choice is available to you if you use DBCA after the installation to create a database.
If you select an installation method that runs DBCA in non-interactive mode, you must choose an existing disk group for the new database; you cannot create a new disk group. However, you can add disk devices to an existing disk group if it has insufficient free space for your requirements.
Note: The ASM instance that manages the existing disk group can be running in a different Oracle home directory. |
To determine whether an existing ASM disk group exists, or to determine whether there is sufficient disk space in a disk group, you can use Oracle Enterprise Manager Grid Control or Database Control. Alternatively, you can use the following procedure:
View the contents of the oratab
file to determine whether an ASM instance is configured on the system:
# more /var/opt/oracle/oratab
If an ASM instance is configured on the system, the oratab
file should contain a line similar to the following:
+ASM:oracle_home_path:N
In this example, +ASM
is the system identifier (SID) of the ASM instance and oracle_home_path
is the Oracle home directory where it is installed. By convention, the SID for an ASM instance begins with a plus sign.
Set the ORACLE_SID and ORACLE_HOME environment variables to specify the appropriate values for the ASM instance that you want to use.
Connect to the ASM instance as the SYS user with SYSDBA privilege and start the instance if necessary:
# $ORACLE_HOME/bin/sqlplus "SYS/SYS_password as SYSDBA"
SQL> STARTUP
Enter the following command to view the existing disk groups, their redundancy level, and the amount of free disk space in each one:
SQL> SELECT NAME,TYPE,TOTAL_MB,FREE_MB FROM V$ASM_DISKGROUP;
From the output, identify a disk group with the appropriate redundancy level and note the free space that it contains.
If necessary, install or identify the additional disk devices required to meet the storage requirements listed in the previous section.
Note: If you are adding devices to an existing disk group, Oracle recommends that you use devices that have the same size and performance characteristics as the existing devices in that disk group. |
To configure disks for use with ASM on Solaris, follow these steps:
If necessary, install the shared disks that you intend to use for the disk group and restart the system.
On SPARC systems only, enter the following commands to identify devices that are part of a logical volume manager (LVM) disk group:
# vxdiskconfig # /usr/sbin/vxdisk list
If this command displays disk group information associated with a disk device, the disk is already part of an LVM disk group. Do not use disks that are part of an LVM disk group.
To create or identify the disk slices (partitions) that you want to include in the ASM disk group, follow these steps:
To list the disks attached to the system, enter the following command:
# /usr/sbin/format
The output from this command is similar to the following:
AVAILABLE DISK SELECTIONS: 0. c0t0d0 <ST34321A cyl 8892 alt 2 hd 15 sec 63> /pci@1f,0/pci@1,1/ide@3/dad@0,0 1. c1t5d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133> /pci@1f,0/pci@1/scsi@1/sd@5,0
This command displays information about each disk attached to the system, including the device name (c
x
t
y
d
z
).
Enter the number corresponding to the disk that you want to use.
On x86 systems only, use the fdisk
command to create a Solaris partition on the disk if one does not already exist.
Solaris fdisk
partitions must start at cylinder 1, not cylinder 0. If you create a new fdisk
partition, you must label the disk before continuing.
Enter the partition
command, followed by the print
command to display the partition table for the disk that you want to use.
If necessary, create a single whole-disk slice, starting at cylinder 1.
Note: To prevent ASM from overwriting the partition table, you cannot use slices that start at cylinder 0 (for example, slice 2). |
Make a note of the number of the slice that you want to use.
If you modified a partition table or created a new one, enter the label
command to write the partition table and label to the disk.
Enter q
to return to the format
menu.
If you have finished creating slices, enter q
to quit from the format
utility. Otherwise, enter the disk
command to select a new disk and repeat steps b to g to create or identify the slices on that disks.
On the other cluster nodes, use the format
utility to determine whether the device names for the slices that you created are the same on every node.
If you plan to use existing slices, enter the following command on every node to verify that they are not mounted as file systems:
# df -k
This command displays information about the slices on disk devices that are mounted as file systems. The device name for a slice includes the disk device name followed by the slice number, for example c
x
t
y
d
z
s
n
, where s
n
is the slice number.
Enter commands similar to the following on every node to change the owner, group, and permissions on the character raw device file for each disk slice that you want to add to a disk group:
# chown oracle:dba /dev/rdsk/cxtydzs6 # chmod 660 /dev/rdsk/cxtydzs6
In this example, the device name specifies slice 6.
Note: If you are using a multi-pathing disk driver with ASM, make sure that you set the permissions only on the correct logical device name for the disk.If the nodes are configured differently, the disk device names for the disks might be different on some nodes. Make sure that you specify the correct disk device name in these commands on each node. |
If you also want to use raw devices for storage, refer to the "Configure Raw Partitions or Raw Logical Volumes" section.
Otherwise, refer to the "Verify that the Cluster Software is Configured and Running" section.
Refer to the following section for information about configuring raw devices.
Note: If you are using ASM for database file storage, you need only create raw devices for the Oracle CRS files. However, if a cluster file system is available on your platform, Oracle recommends that you use that file system to store the Oracle CRS files instead of using raw devices for them. |
The following subsections describe how to configure raw partitions or raw logical volumes on Solaris:
Configure Raw Partitions or Raw Logical Volumes
Follow the procedures described in this section if you are installing RAC on a cluster without a supported cluster volume manager or a supported cluster file system.
SPARC Only: Configuring Raw Logical Volumes for Oracle CRS or Database File Storage
Follow the procedures described in this section only if you are using VERITAS Cluster Volume Manager (CVM) with Sun Cluster on SPARC systems.
Configuring Raw Partitions for Oracle CRS or Database File Storage
This section describes how to configure shared raw partitions for Oracle CRS files (Oracle Cluster Registry and CRS voting disk) and Oracle database files.
A partition is a slice defined on a shared disk or on a shared disk array volume.
Note: For RAC installations, Solaris Volume Manager volumes or partitions are not currently supported for Oracle CRS or database file storage. |
Table 7-1 lists the number and size of the raw disk devices that you must configure for database files. Table 7-2 lists the number and size of the raw disk devices that you must configure for CRS files.
Note: Solaris imposes limits on the number of slices that you can create on a single disk device. If you want to use slices, you might need to create them on more than one disk or volume. |
Table 7-1 Raw Partitions Required for Database Files on Solaris
Table 7-2 Raw Partitions Required for CRS Files on Solaris
To configure shared raw partitions for CRS files, database files, or both, follow these steps:
If you intend to use raw partitions for database file storage, choose a name for the database that you want to create.
The name that you choose must start with a letter and have no more than four characters, for example, orcl
.
If necessary, install or configure the shared disks that you intend to use and restart the system.
If you want to use disk slices, follow these steps to create or identify the required disk slices:
To list the disks attached to the system, enter the following command:
# /usr/sbin/format
The output from this command is similar to the following:
AVAILABLE DISK SELECTIONS: 0. c0t0d0 <ST34321A cyl 8892 alt 2 hd 15 sec 63> /pci@1f,0/pci@1,1/ide@3/dad@0,0 1. c1t5d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133> /pci@1f,0/pci@1/scsi@1/sd@5,0
This command displays information about each disk attached to the system, including the device name (c
x
t
y
d
z
).
Enter the number corresponding to the disk that you want to use.
Note: Make sure that the disk you choose is not being used for another purpose. For example, make sure that it is not being used as a component for a logical volume manager volume. |
On x86 systems only, use the fdisk
command to create a Solaris partition on the disk if one does not already exist.
Solaris fdisk
partitions must start at cylinder 1, not cylinder 0. If you create a new fdisk
partition, you must label the disk before continuing.
Enter the partition
command, followed by the print
command to display the partition table for the disk that you want to use.
Identify or create slices for each of the partitions that you require.
The previous table shows the number and size of the partitions that you require for both CRS files and database files.
Note: To prevent the CRS or database files from overwriting the partition table, do not use slices that start at cylinder 0 (for example, slice 2). |
Make a note of the number of the slices that you want to use.
If you modified a partition table or created a new one, enter the label
command to write the partition table and label to the disk.
Enter q
to return to the format
menu.
After you have finished creating slices, enter q
to quit from the format
utility.
If you plan to use existing partitions, enter the following command on every node to verify that they are not mounted as file systems:
# df -k
This command displays information about the devices that are mounted as file systems. The device name for a slice includes the disk device name followed by the slice number, for example c
x
t
y
d
z
s
n
, where s
n
is the slice number.
On the other cluster nodes, use the format
utility to determine whether the device names for the slices that you created are the same on every node.
If the device name for a slice that you want to use is different on any node, enter a command similar to the following on all nodes to create symbolic links to the appropriate device using a common name:
Note: If you are using a multi-pathing disk driver, make sure that you create the links to the correct logical device name for the slice.The previous table provides suggested symbolic link names for each partition. |
# ln -s /dev/rdsk/cxtydzsn /dev/rdsk/ora_ocr_raw_100m
Enter commands similar to the following on every node to change the owner, group, and permissions on the character raw device file for each partition:
OCR:
# chown root:oinstall /dev/rdsk/cxtydzsn # chmod 640 /dev/rdsk/cxtydzsn
CRS voting disk and database files:
# chown oracle:dba /dev/rdsk/cxtydzsn # chmod 660 /dev/rdsk/cxtydzsn
Note: If you are using a multi-pathing disk driver, make sure that you set the permissions only on the correct logical device name for the partition.If you created symbolic links, specify the symbolic link paths in these commands. |
If you are using raw disk devices for database files, follow these steps to create the DBCA raw device mapping file:
Note: You must complete this procedure only if you are using raw devices for database files. The DBCA raw device mapping file enables the DBCA to identify the appropriate raw disk device for each database file. You do not specify the raw devices for the Oracle CRS files in the DBCA raw device mapping file. |
Set the ORACLE_BASE environment variable to specify the Oracle base directory that you identified or created previously:
Bourne, Bash, or Korn shell:
$ ORACLE_BASE=/u01/app/oracle ; export ORACLE_BASE
C shell:
% setenv ORACLE_BASE /u01/app/oracle
Create a database file subdirectory under the Oracle base directory and set the appropriate owner, group, and permissions on it:
# mkdir -p $ORACLE_BASE/oradata/dbname
# chown -R oracle:oinstall $ORACLE_BASE/oradata
# chmod -R 775 $ORACLE_BASE/oradata
In this example, dbname
is the name of the database that you chose previously.
Change directory to the $ORACLE_BASE/oradata/
dbname
directory.
Using any text editor, create a text file similar to the following that identifies the device file name associated with each database file.
Oracle recommends that you use a file name similar to dbname
_raw.conf
for this file.
Note: The following example shows a sample mapping file for a two-instance RAC cluster. Some of the partitions use alternative symbolic link names. Make sure that the partition device file name that you specify identifies the same partition on all nodes. |
system=/dev/rdsk/c2t1d1s3 sysaux=/dev/rdsk/c2t1d1s4 example=/dev/rdsk/c2t1d1s5 users=/dev/rdsk/c2t1d1s6 temp=/dev/rdsk/c2t1d2s3 undotbs1=/dev/rdsk/c2t1d2s4 undotbs2=/dev/rdsk/c2t1d2s5 redo1_1=/dev/rdsk/c2t1d2s6 redo1_2=/dev/rdsk/c2t1d3s3 redo2_1=/dev/rdsk/c2t1d3s4 redo2_2=/dev/rdsk/c2t1d3s5 control1=/dev/rdsk/c2t1d4s3 control2=/dev/rdsk/c2t1d4s3 spfile=/dev/rdsk/dbname_spfile_raw_5m pwdfile=/dev/rdsk/dbname_pwdfile_raw_5m
In this example, dbname
is the name of the database.
Use the following guidelines when creating or editing this file:
Each line in the file must have the following format:
database_object_identifier=device_file_name
The symbolic link names suggested in the previous table include the database object identifier that you must use in this mapping file. For example, in the following symbolic link name, redo1_1
is the database object identifier:
rac_redo1_1_raw_120m
For a RAC database, the file must specify one automatic undo tablespace datafile (undotbs
n
) and two redo log files (redo
n
_1
, redo
n
_2
) for each instance.
Specify at least two control files (control1
, control2
).
To use manual instead of automatic undo management, specify a single RBS tablespace datafile (rbs
) instead of the automatic undo management tablespace datafiles.
Save the file and note the file name that you specified.
When you are configuring the oracle
user's environment later in this chapter, set the DBCA_RAW_CONFIG environment variable to specify the full path to this file.
When you are installing Oracle Cluster Ready Services, you must enter the paths to the appropriate device files when prompted for the path of the OCR and CRS voting disk, for example:
/dev/rdsk/cxtydzsn
To continue, refer to the "Verify that the Cluster Software is Configured and Running" section.
SPARC Only: Configuring Raw Logical Volumes for Oracle CRS or Database File Storage
This section describes how to configure raw logical volumes using VERITAS Cluster Volume Manager (CVM) with Sun Cluster 3.1 on SPARC systems.
Note: For information about other supported options for creating logical volumes for Oracle CRS and database files, refer to the Certify page on the OracleMetalink Web site:http://metalink.oracle.com/ |
To create a shared disk group, follow these steps:
If necessary, install the shared disks that you intend to use for the disk group and restart the system.
To make sure that the disks are available, enter the following command:
# /usr/sbin/format
The output from this command is similar to the following:
AVAILABLE DISK SELECTIONS: 0. c0t0d0 <ST34321A cyl 8892 alt 2 hd 15 sec 63> /pci@1f,0/pci@1,1/ide@3/dad@0,0 1. c1t5d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133> /pci@1f,0/pci@1/scsi@1/sd@5,0
This command displays information about each disk attached to the system, including the device name (c
x
t
y
d
z
).
From the list, identify the device names for the disk devices that you want to add to a disk group, then press Ctrl/D to exit from the format
utility.
Enter the following command on every node to verify that the devices you identified are not mounted as file systems:
# df -k
This command displays information about the partitions (slices) on disk devices that are mounted as file systems. The device name for a slice includes the disk device name followed by the slice number, for example c
x
t
y
d
z
s
n
, where s
n
is the slice number. Slice 2 (s2
) represents the entire disk. The disk devices that you choose must not be shown as mounted partitions.
Enter the following commands to verify that the devices you identified are not already part of a disk group:
# /usr/sbin/vxdiskconfig # /usr/sbin/vxdisk list
The vxdisk list
command identifies the disk devices that are already configured in a disk group. The word online in the STATUS column also identifies disks that have been initialized and placed under VxVM control. The word error in the STATUS column identifies disks that are not initialized.
The disk devices that you choose must not be in an existing disk group.
If the disk devices that you want to use are not initialized, enter a command similar to the following to initialize each disk:
# /usr/sbin/vxdiskadd cxtydz
To create a shared disk group, enter a command similar to the following, specifying all of the disks that you want to add to the group:
# /usr/sbin/vxdg -s init diskgroup diskname=devicename ...
In this example:
-s
indicates that you want to create a shared disk group
diskgroup
is the name of the disk group that you want to create, for example, oradg
diskname
is an administrative name that you assign to a disk, for example orad01
devicename
is the device name, for example, c1t0d0
Create Raw Logical Volumes in the New Disk Group
To create the required raw logical volumes in the new disk group, follow these steps:
Choose a name for the database that you want to create.
The name that you choose must start with a letter and have no more than four characters, for example, orcl
.
Identify the logical volumes that you must create.
Table 7-3 lists the number and size of the logical volumes that you must create for database files. Table 7-4 lists the number and size of the logical volumes that you must create for CRS files.
Table 7-3 Raw Logical Volumes Required for Database Files on Solaris
Table 7-4 Raw Logical Volumes Required for CRS Files on Solaris
To create the logical volume for the Oracle Cluster Registry, enter a command similar to the following:
# /usr/sbin/vxassist -g diskgroup make ora_ocr_raw_100m 100m user=root \
group=oinstall mode=640
In this example, diskgroup
is the name of the disk group you created previously, for example, oradg
.
To create the other required logical volumes, enter commands similar to the following:
# /usr/sbin/vxassist -g diskgroup make volume size user=oracle \ group=dba mode=660
In this example:
diskgroup
is the name of the disk group that you created previously, for example oradg
volume
is the name of the logical volume that you want to create
Oracle recommends that you use the sample names shown in the previous table for the logical volumes. Substitute the dbname
variable in the sample logical volume name with the name you chose for the database in step 1.
size
is the size of the logical volume, for example, 500m
represents 500 MB
user=oracle group=dba mode=660
specifies the owner, group, and permissions on the volume
Specify the Oracle software owner user and the OSDBA group for the user
and group
values (typically oracle
and dba
).
The following example shows a sample command used to create an 800 MB logical volume in the oradg
disk group for the SYSAUX tablespace of a database named test
:
# /usr/sbin/vxassist -g oradb make test_sysaux_raw_800m 800m \ user=oracle group=dba mode=660
Deport the Disk Group and Import It on the Other Cluster Nodes
To deport the disk group and import it on the other cluster nodes, follow these steps:
Deport the disk group:
# /usr/sbin/vxdg deport diskgroup
Log into each cluster node and complete the following steps:
Enter the following command to cause VxVM to examine the disk configuration:
# /usr/sbin/vxdctl enable
Import the shared disk group:
# /usr/sbin/vxdg -s import diskgroup
Start all logical volumes:
# /usr/sbin/vxvol startall
Create the DBCA Raw Device Mapping File
Note: You must complete this procedure only if you are using raw devices for database files. You do not specify the raw devices for the Oracle CRS files in the DBCA raw device mapping file. |
To enable Database Configuration Assistant (DBCA) to identify the appropriate raw device for each database file, you must create a raw device mapping file, as follows:
Set the ORACLE_BASE environment variable to specify the Oracle base directory that you identified or created previously:
Bourne, Bash, or Korn shell:
$ ORACLE_BASE=/u01/app/oracle ; export ORACLE_BASE
C shell:
% setenv ORACLE_BASE /u01/app/oracle
Create a database file subdirectory under the Oracle base directory and set the appropriate owner, group, and permissions on it:
# mkdir -p $ORACLE_BASE/oradata/dbname
# chown -R oracle:oinstall $ORACLE_BASE/oradata
# chmod -R 775 $ORACLE_BASE/oradata
In this example, dbname
is the name of the database that you chose previously.
Change directory to the $ORACLE_BASE/oradata/
dbname
directory.
Enter the following command to create a text file that you can use to create the raw device mapping file:
# find /dev/vx/rdsk/diskgroup -user oracle -name dbname* \ -print > dbname_raw.conf
Edit the dbname
_raw.conf
file in any text editor to create a file similar to the following:
Note: The following example shows a sample mapping file for a two-instance RAC cluster. |
system=/dev/vx/rdsk/diskgroup/dbname_system_raw_500m sysaux=/dev/vx/rdsk/diskgroup/dbname_sysaux_raw_800m example=/dev/vx/rdsk/diskgroup/dbname_example_raw_160m users=/dev/vx/rdsk/diskgroup/dbname_users_raw_120m temp=/dev/vx/rdsk/diskgroup/dbname_temp_raw_250m undotbs1=/dev/vx/rdsk/diskgroup/dbname_undotbs1_raw_500m undotbs2=/dev/vx/rdsk/diskgroup/dbname_undotbs2_raw_500m redo1_1=/dev/vx/rdsk/diskgroup/dbname_redo1_1_raw_120m redo1_2=/dev/vx/rdsk/diskgroup/dbname_redo1_2_raw_120m redo2_1=/dev/vx/rdsk/diskgroup/dbname_redo2_1_raw_120m redo2_2=/dev/vx/rdsk/diskgroup/dbname_redo2_2_raw_120m control1=/dev/vx/rdsk/diskgroup/dbname_control1_raw_110m control2=/dev/vx/rdsk/diskgroup/dbname_control2_raw_110m spfile=/dev/vx/rdsk/diskgroup/dbname_spfile_raw_5m pwdfile=/dev/vx/rdsk/diskgroup/dbname_pwdfile_raw_5m
In this example:
diskgroup
is the name of the disk group
dbname
is the name of the database
Use the following guidelines when creating or editing this file:
Each line in the file must have the following format:
database_object_identifier=logical_volume
The logical volume names suggested in this manual include the database object identifier that you must use in this mapping file. For example, in the following logical volume name, redo1_1
is the database object identifier:
/dev/vx/rdsk/oradg/rac_redo1_1_raw_120m
For a RAC database, the file must specify one automatic undo tablespace datafile (undotbs
n
) and two redo log files (redo
n
_1
, redo
n
_2
) for each instance.
Specify at least two control files (control1
, control2
).
To use manual instead of automatic undo management, specify a single RBS tablespace datafile (rbs
) instead of the automatic undo management tablespace datafiles.
Save the file and note the file name that you specified.
When you are configuring the oracle
user's environment later in this chapter, set the DBCA_RAW_CONFIG environment variable to specify the full path to this file.
Note: This section applies to SPARC systems only.Sun Cluster is not required. However, if it is installed, Oracle CRS can integrate with it. |
To verify that the Sun Cluster software is configured and running on Solaris SPARC systems:
Verify that the oracle.dba.gid
parameter in the /etc/opt/SUNWcluster/conf/
clustername
.ora_cdb
file specifies the group ID of the OSDBA group (typically dba
) that you created earlier.
Note: The name of the cluster (clustername ) is defined in the /etc/opt/SUNWcluster/conf/default_clustername file.
|
To verify that the Sun Cluster software is running, enter the following command on one of the cluster nodes:
# /usr/cluster/bin/scstat -n
If the output from this command does not list all of the nodes in the cluster, make sure that all of the cluster nodes are booted.
If necessary, refer to the Sun Cluster documentation for information about troubleshooting the cluster.
Caution: If you are installing additional Oracle Database 10g products in an existing Oracle home, stop all processes running in the Oracle home. You must complete this task to enable the Installer to relink certain executables and libraries. |
If you choose to create a database during the installation, most installation types configure and start a default Oracle Net listener using TCP/IP port 1521 and the IPC key value EXTPROC. However, if an existing Oracle Net listener process is using the same port or key value, the Installer can only configure the new listener; it cannot start it. To ensure that the new listener process starts during the installation, you must shut down any existing listeners before starting the Installer.
To determine whether an existing listener process is running and to shut it down if necessary, follow these steps:
Switch user to oracle
:
# su - oracle
Enter the following command to determine whether a listener process is running and to identify its name and the Oracle home directory in which it is installed:
$ ps -ef | grep tnslsnr
This command displays information about the Oracle Net listeners running on the system:
... oracle_home1/bin/tnslsnr LISTENER -inherit
In this example, oracle_home1
is the Oracle home directory where the listener is installed and LISTENER
is the listener name.
Note: If no Oracle Net listeners are running, refer to the "Configure the oracle User's Environment" section to continue. |
Set the ORACLE_HOME environment variable to specify the appropriate Oracle home directory for the listener:
Bourne, Bash, or Korn shell:
$ ORACLE_HOME=oracle_home1
$ export ORACLE_HOME
C or tcsh shell:
% setenv ORACLE_HOME oracle_home1
Enter the following command to identify the TCP/IP port number and IPC key value that the listener is using:
$ $ORACLE_HOME/bin/lsnrctl status listenername
Note: If the listener uses the default name LISTENER, you do not have to specify the listener name in this command. |
Enter a command similar to the following to stop the listener process:
$ $ORACLE_HOME/bin/lsnrctl stop listenername
Repeat this procedure to stop all listeners running on this system and on all other cluster nodes.
You run the Installer from the oracle
account. However, before you start the Installer you must configure the environment of the oracle
user. To configure the environment, you must:
To set the oracle
user's environment, follow these steps:
Start a new terminal session, for example, an X terminal (xterm
).
Enter the following command to ensure that X Window applications can display on this system:
$ xhost +
If you are not already logged in to the system where you want to install the software, log in to that system as the oracle
user.
If you are not logged in as the oracle
user, switch user to oracle
:
$ su - oracle
To determine the default shell for the oracle
user, enter the following command:
$ echo $SHELL
Open the oracle
user's shell startup file in any text editor:
Bourne shell (sh
), Bash shell (bash
), or Korn shell (ksh
):
$ vi .profile
C shell (csh
or tcsh
):
% vi .login
Enter or edit the following line, specifying a value of 022 for the default file mode creation mask:
umask 022
If the ORACLE_SID, ORACLE_HOME, or ORACLE_BASE environment variables are set in the file, remove the appropriate lines from the file.
Save the file and exit from the editor.
To run the shell startup script, enter one of the following commands:
Bourne, Bash, or Korn shell:
$ . ./.profile
C shell:
% source ./.login
If you are not installing the software on the local system, enter a command similar to the following to direct X applications to display on the local system:
Bourne, Bash, or Korn shell:
$ DISPLAY=local_host:0.0 ; export DISPLAY
C shell:
% setenv DISPLAY local_host:0.0
In this example, local_host
is the host name or IP address of the system that you want to use to display the Installer (your workstation or PC).
If you determined that the /tmp
directory has less than 400 MB of free disk space, identify a file system with at least 400 MB of free space and set the TEMP and TMPDIR environment variables to specify a temporary directory on this file system:
Use the df -k
command to identify a suitable file system with sufficient free space.
If necessary, enter commands similar to the following to create a temporary directory on the file system that you identified, and set the appropriate permissions on the directory:
$ su - root # mkdir /mount_point/tmp # chmod a+wr /mount_point/tmp # exit
Enter commands similar to the following to set the TEMP and TMPDIR environment variables:
Bourne, Bash, or Korn shell:
$ TEMP=/mount_point/tmp $ TMPDIR=/mount_point/tmp $ export TEMP TMPDIR
C shell:
% setenv TEMP /mount_point/tmp % setenv TMPDIR /mount_point/tmp
Enter commands similar to the following to set the ORACLE_BASE environment variable:
Bourne, Bash, or Korn shell:
$ ORACLE_BASE=/u01/app/oracle $ export ORACLE_BASE
C shell:
% setenv ORACLE_BASE /u01/app/oracle
In these examples, /u01/app/oracle
is the Oracle base directory that you created or identified earlier.
If you are using raw devices for database file storage, set the DBCA_RAW_CONFIG environment variable to specify the full path to the raw device mapping file:
Bourne, Bash, or Korn shell:
$ DBCA_RAW_CONFIG=$ORACLE_BASE/oradata/dbname/dbname_raw.conf $ export DBCA_RAW_CONFIG
C shell:
% setenv DBCA_RAW_CONFIG=$ORACLE_BASE/oradata/dbname/dbname_raw.conf
Enter the following command to ensure that the ORACLE_HOME and TNS_ADMIN environment variables are not set:
Bourne, Bash, or Korn shell:
$ unset ORACLE_HOME $ unset TNS_ADMIN
C shell:
% unsetenv ORACLE_HOME % unsetenv TNS_ADMIN
Note: If the ORACLE_HOME environment variable is set, the Installer uses the value that it specifies as the default path for the Oracle home directory. However, if you set the ORACLE_BASE environment variable, Oracle recommends that you unset the ORACLE_HOME environment variable and choose the default path suggested by the Installer. |
To verify that the environment has been set correctly, enter the following commands:
$ umask $ env | more
Verify that the umask
command displays a value of 22
, 022
, or 0022
and that the environment variables you set in this section have the correct values.