Skip Headers
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
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

7 Pre-Installation Tasks for RAC on Solaris

This chapter describes the tasks that you must complete before you start the Oracle Universal Installer (OUI). It includes information about the following tasks:

Log In to the System as root

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.


Check the Hardware Requirements

Each system must meet the following minimum hardware requirements:

To ensure that each system meets these requirements, follow these steps:

  1. 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.

  2. 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.

  3. 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 the Network Requirements

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:

IP Address Requirements

Before starting the installation, you must identify or obtain the following IP addresses for each node:

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:

  1. If necessary, install the network adapters for the public and private networks and configure them with either public or private IP addresses.

  2. Register the host names and IP addresses for the public network interfaces in DNS.

  3. For each node, register one virtual host name and IP address in DNS.


    Note:

    If you are using Sun Cluster 3.1, go to step 6

  4. 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
    
    
  5. 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.

  6. 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.

Check the Software Requirements

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.

Checking the Software Requirements

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:

SUNWmfrun

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:
  • IBM WebSphere MQ V5.3, client and server (SPARC):

    mqm
    
  • IBM MQSeries V5.1, client and server (x86)

  • TIBCO Rendezvous 7.2 (SPARC only)


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:
  • Sun Java 2 SDK Standard Edition 1.3.1_10 (SPARC) or 1.3.1_11 (x86) and the JNDI extension

  • Sun Java 2 SDK Standard Edition 1.2.2_17 and the JNDI extension

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:
  • Sybase Adaptive Server Enterprise V12 or 12.5

  • Sybase Open Client V12 or 12.5

    Open Client is required if the Sybase server is not on the local node.

Oracle Transparent Gateway for Informix (SPARC only) One of the following:
  • Informix Dynamic Server v7.3, 7.4, or 9.*

  • Informix ESQL/C v7.3, 7.4, or 9.*

    ESQL/C is required if the Informix server is not on the local node.

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:

  1. 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.

  2. 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.

Check for Required Patches

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.

Installation Type or Product Requirement
All installations Patches for Solaris 8 (SPARC only):

All of the patches included in the J2SE Patch Cluster for Solaris 8:

  • 108528-23, SunOS 5.8: kernel update patch

  • 108652-66, X11 6.4.1: Xsun patch

  • 108773-18, SunOS 5.8: IIIM and X I/O Method patch

  • 108921-16, CDE 1.4: dtwm patch

  • 108940-53, Motif 1.2.7 and 2.1.1: Runtime lib. patch for Solaris 8

  • 108987-13, SunOS 5.8: Patch for patchadd and patchrm

  • 108989-02, /usr/kernel/sys/acctctl & /.../exacctsys patch

  • 108993-19, SunOS 5.8: LDAP2 client, libc, ... lib. patch

  • 109147-24, SunOS 5.8: linker patch

  • 110386-03, SunOS 5.8: RBAC Feature Patch

  • 111023-02, SunOS 5.8: /kernel/fs/mntfs and ... sparcv9/mntfs

  • 111111-03, SunOS 5.8: /usr/bin/nawk patch

  • 111308-03, SunOS 5.8: /usr/lib/libmtmalloc.so.1 patch

  • 111310-01, SunOS 5.8: /usr/lib/libdhcpagent.so.1 patch

  • 112396-02, SunOS 5.8: /usr/bin/fgrep patch

The following additional patches:

  • 111721-04, SunOS 5.8: Math Library (libm) patch

  • 112003-03, SunOS 5.8: Unable to load fontset ... iso-1 or iso-15

  • 112138-01, SunOS 5.8: usr/bin/domainname patch

All installations Patches for Solaris 9 (SPARC):
  • 112233-11, SunOS 5.9: Kernel Patch

  • 111722-04, SunOS 5.9: Math Library (libm) patch

Patches for Solaris 9 (x86):

  • 111713-06, SunOS 5.9_x86: Shared library patch for C++

  • 111728-03, SunOS 5.9_x86: Math Library (libm) patch

  • 112234-12, SunOS 5.9_x86: Kernel Patch

  • 113986-08, SunOS 5.9_x86: linker Patch

  • 115114-02, SunOS 5.9_x86: Patch for assembler

  • 116013-02, SunOS 5.9_x86: ps utility patch (Available only from your local Sun solution center)


PL/SQL native compilation,
Pro*C/C++,
Oracle Call Interface,
Oracle C++ Call Interface,
Oracle XML Developer's Kit (XDK)
Patches for Solaris 8 and Solaris 9 (SPARC):
  • 112758-02, dbx 7.1: Patch for S1S8CC Debugger

  • 112760-05, C 5.5: Patch for S1S8CC C compiler

  • 112763-06, Compiler Common S1S8CC: Patch for S1S8CC C C++ F77 F95

  • 113817-03, C++ 5.5: Patch for S1S8CC C++ compiler

  • 113820-02, Compiler Common 7.1: Patch for S1S8CC Math Libraries

  • 113823-03, ILD 4.1: Patch for S1S8CC Incremental Linker

Patches for Solaris 9 (x86):

  • 112756-10, Patch for S1S8CC Sun Compiler Common 7.1 compiler backend_x86

  • 112759-03, dbx 7.1_x86: Patch for S1S8CC Debugger

  • 112761-07, C 5.5_x86: Patch for S1S8CC C compiler

  • 113819-07, C++ 5.5_x86: Patch for S1S8CC C++ compiler

  • 113821-01, Compiler Common 7.1_x86: Patch for S1S8CC Math Libraries

  • 113825-02, ILD 4.1_x86: Patch for S1S8CC Incremental Linker

Real Application Clusters Sun Cluster patches for Solaris 8 (SPARC):
  • 111488-08, Sun Cluster 3.0/3.1: mediator patch

  • 113800-06, Sun Cluster 3.1: Core/Sys Admin Patch

To obtain the following patches, contact your local Sun solution center:

114492-02, 115058-03, 115062-02, 115064-01, 115066-01, 115070-01, 115072-01, 115076-01, 115078-01, 115080-01, 115082-01, 115084-01, 115086-01, 115089-01

Sun Cluster patches for Solaris 9 (SPARC):

113801: Sun Cluster 3.1: Core/Sys Admin Patch

Oracle Messaging Gateway Corrective service diskettes (CSDs) for WebSphere MQ:

SPARC systems:

CSD06 or later for WebSphere MQ V5.3

x86 systems:

  • CSD09 or later for MQSeries Server V5.1

  • MQSeries Client for Sun Solaris, Intel Platform Edition- V5.1 SupportPac MACE


To ensure that the system meets these requirements, follow these steps:

  1. 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
    
    
  2. 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
    
    

Create Required UNIX Groups and User

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:

The following UNIX group and user are required for all installations:

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.

Creating the Oracle Inventory Group

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

Creating the OSDBA Group

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

Creating an OSOPER Group (Optional)

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

Verifying that the UNIX User nobody Exists

Before installing the software, verify that the UNIX user nobody exists on the system:

  1. 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.

  2. If the nobody user does not exist, enter the following command to create it:

    # /usr/sbin/useradd nobody
    
    
  3. Repeat this procedure on all of the other cluster nodes.

Create Identical Users and Groups on 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:

  1. 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)
    
    
  2. 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:

  1. Log in to the next cluster node as root.

  2. 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 the groupmod 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.

  3. 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 the usermod 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.

  4. Set the password of the oracle user:

    # passwd oracle
    
    

Set Up User Equivalence for rsh and rcp on All Cluster Nodes


Note:

This section describes how to set up user equivalence for rcp, 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:

  1. 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.

Configure Kernel Parameters and Shell Limits

Refer to the following section for information about configuring the system kernel parameters and shell limits.

Configuring Kernel Parameters


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

Footnote 1 This parameter is obsolete in Solaris 9

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:

  1. 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
    
    
  2. If you must change any of the current values, follow these steps:

    1. Create a backup copy of the /etc/system file, for example:

      # cp /etc/system /etc/system.orig
      
      
    2. 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
      
      
    3. Enter the following command to restart the system:

      # /usr/sbin/reboot
      
      
    4. When the system restarts, log in and switch user to root.

  3. Repeat this procedure on all other cluster nodes.

Identify Required Software Directories

You must identify or create four directories for the Oracle software, as follows:

The following subsections describe the requirements for these directories.

Oracle Base Directory

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

In this example:

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.

Oracle Inventory Directory

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 the root user, the CRS home directory must not be a subdirectory of the Oracle base directory.

Oracle Home 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.

Identify or Create an Oracle Base 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:

Before deciding to use an existing Oracle base directory for this installation, make sure that it satisfies the following conditions:

To continue:

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:

Requirement Free Disk Space
The Oracle base directory will contain only software files. Up to 3 GB
The Oracle base directory will contain both software and database files (not recommended for production databases). Up to 4 GB

To identify an appropriate file system, follow these steps:

  1. Use the df -k command to determine the free disk space on each mounted file system.

  2. 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.

  3. 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:

  1. 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
    
    
  2. If necessary, repeat the commands listed in the previous step to create the same directory on the other cluster nodes.

  3. When you are configuring the oracle user's environment later in this chapter, set the ORACLE_BASE environment variable to specify this directory.

Create the CRS Home 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:

  1. Use the df -k command to determine the free disk space on each mounted file system.

  2. 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.

  3. 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:

  1. 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
    
    
  2. If necessary, repeat the commands listed in the previous step to create the same directory on the other cluster nodes.

  3. When you are installing Oracle CRS, set the ORACLE_HOME environment variable to specify this directory.


    Note:

    During the installation, before you run the root.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.

Choose a Storage Option for Oracle CRS, Database, and Recovery Files

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:

For information about how to configure disk storage before you start the installation, refer to one of the following sections depending on your choice:

Create Directories for Oracle CRS, Database, or Recovery Files

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:


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:

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:

Creating Required Directories


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:

  1. 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.

  2. Use the df -k command to determine the free disk space on each mounted file system.

  3. 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:
    • A single file system with at least 1.2 GB of free disk space

    • Two or more file systems with at least 1.2 GB of free disk space in total

    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.

  4. Note the names of the mount point directories for the file systems that you identified.

  5. 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
      
      
  6. 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.

Configure Disks for Automatic Storage Management

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.

Identifying Storage Requirements for ASM

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:

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Using an Existing ASM Disk Group

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:

  1. 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.

  2. Set the ORACLE_SID and ORACLE_HOME environment variables to specify the appropriate values for the ASM instance that you want to use.

  3. 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
    
    
  4. 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;
    
    
  5. From the output, identify a disk group with the appropriate redundancy level and note the free space that it contains.

  6. 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.

Configuring Disks for ASM

To configure disks for use with ASM on Solaris, follow these steps:

  1. If necessary, install the shared disks that you intend to use for the disk group and restart the system.

  2. On SPARC systems only, enter the following commands to identify devices that are part of a logical volume manager (LVM) disk group:


    Note:

    The following command displays information about VERITAS Volume Manager disks. If you use a different LVM, refer to the appropriate documentation for information about determining which disk devices it is managing.

    # 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.

  3. To create or identify the disk slices (partitions) that you want to include in the ASM disk group, follow these steps:

    1. 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 (cxtydz).

    2. Enter the number corresponding to the disk that you want to use.

    3. 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.

    4. Enter the partition command, followed by the print command to display the partition table for the disk that you want to use.

    5. 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).

    6. Make a note of the number of the slice that you want to use.

    7. 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.

    8. Enter q to return to the format menu.

    9. 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.

  4. 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.

  5. 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 cxtydzsn, where sn is the slice number.

  6. 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.


  7. 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.

Configure Raw Partitions or Raw Logical Volumes

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.

Configuring Raw Partitions or Raw Logical Volumes

The following subsections describe how to configure raw partitions or raw logical volumes on Solaris:

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

Number Size (MB) Purpose and Sample Symbolic Link Name
1 500 SYSTEM tablespace:
dbname_system_raw_500m
1 300 + (Number of instances * 250) SYSAUX tablespace:
dbname_sysaux_raw_800m
Number of instances 500 UNDOTBSn tablespace (One tablespace for each instance, where n is the number of the instance):
dbname_undotbsn_raw_500m
1 250 TEMP tablespace:
dbname_temp_raw_250m
1 160 EXAMPLE tablespace:
dbname_example_raw_160m
1 120 USERS tablespace:
dbname_users_raw_120m
2 * number of instances 120 Two online redo log files for each instance (n is the number of the instance and m is the log number, 1 or 2):
dbname_redon_m_raw_120m
2 110 First and second control files:
dbname_control{1|2}_raw_110m
1 5 Server parameter file (SPFILE):
dbname_spfile_raw_5m
1 5 Password file:
dbname_pwdfile_raw_5m

Table 7-2 Raw Partitions Required for CRS Files on Solaris

Number Size (MB) Purpose and Sample Symbolic Link Name
1 100 Oracle Cluster Registry:
ora_ocr_raw_100m

Note: You need to create this raw device only once on the cluster. If you create more than one database on the cluster, they all share the same Oracle Cluster Registry (OCR).

1 20 Oracle CRS voting disk:
ora_vote_raw_20m

Note: You need to create this raw device only once on the cluster. If you create more than one database on the cluster, they all share the same Oracle CRS voting disk.


To configure shared raw partitions for CRS files, database files, or both, follow these steps:

  1. 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.

  2. If necessary, install or configure the shared disks that you intend to use and restart the system.

  3. If you want to use disk slices, follow these steps to create or identify the required disk slices:

    1. 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 (cxtydz).

    2. 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.

    3. 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.

    4. Enter the partition command, followed by the print command to display the partition table for the disk that you want to use.

    5. 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).

    6. Make a note of the number of the slices that you want to use.

    7. 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.

    8. Enter q to return to the format menu.

    9. After you have finished creating slices, enter q to quit from the format utility.

  4. 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 cxtydzsn, where sn is the slice number.

  5. 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.

  6. 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
    
    
  7. 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.


  8. 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.

    1. 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
        
        
    2. 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.

    3. Change directory to the $ORACLE_BASE/oradata/dbname directory.

    4. 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 (undotbsn) and two redo log files (redon_1, redon_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.

    5. Save the file and note the file name that you specified.

    6. 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.

  9. 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
    
    
  10. 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/

Create a Shared Disk Group

To create a shared disk group, follow these steps:

  1. If necessary, install the shared disks that you intend to use for the disk group and restart the system.

  2. 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 (cxtydz).

  3. 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.

  4. 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 cxtydzsn, where sn is the slice number. Slice 2 (s2) represents the entire disk. The disk devices that you choose must not be shown as mounted partitions.

  5. Enter the following commands to verify that the devices you identified are not already part of a disk group:


    Note:

    The following command displays information about VERITAS Volume Manager (VxVM) disks. If you use a different LVM, refer to the appropriate documentation for information about determining which disk devices it is managing.

    # /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.

  6. 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
    
    
  7. 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:

  1. 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.

  2. 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

    Number Size (MB) Purpose and Sample Logical Volume Name
    1 500 SYSTEM tablespace:
    dbname_system_raw_500m
    
    1 300 + (Number of instances * 250) SYSAUX tablespace:
    dbname_sysaux_raw_800m
    
    Number of instances 500 UNDOTBSn tablespace (One tablespace for each instance, where n is the number of the instance):
    dbname_undotbsn_raw_500m
    
    1 250 TEMP tablespace:
    dbname_temp_raw_250m
    
    1 160 EXAMPLE tablespace:
    dbname_example_raw_160m
    
    1 120 USERS tablespace:
    dbname_users_raw_120m
    
    2 * number of instances 120 Two online redo log files for each instance (where n is the number of the instance and m is the log number, 1 or 2):
    dbname_redon_m_raw_120m
    
    2 110 First and second control files:
    dbname_control{1|2}_raw_110m
    
    1 5 Server parameter file (SPFILE):
    dbname_spfile_raw_5m
    
    1 5 Password file:
    dbname_pwdfile_raw_5m
    

    Table 7-4 Raw Logical Volumes Required for CRS Files on Solaris

    Number Size (MB) Purpose and Sample Logical Volume Name
    1 100 Oracle Cluster Registry:
    ora_ocr_raw_100m
    

    Note: You need to create this raw logical volume only once on the cluster. If you create more than one database on the cluster, they all share the same Oracle Cluster Registry (OCR).

    If you are upgrading from Oracle9i Release 2, you can continue to use the raw device that you used for the SRVM configuration repository instead of creating this new logical volume.

    1 20 Oracle CRS voting disk:
    ora_vote_raw_20m
    

    Note: You need to create this raw logical volume only once on the cluster. If you create more than one database on the cluster, they all share the same Oracle CRS voting disk.


  3. 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.

  4. 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:

  1. Deport the disk group:

    # /usr/sbin/vxdg deport diskgroup
    
    
  2. Log into each cluster node and complete the following steps:

    1. Enter the following command to cause VxVM to examine the disk configuration:

      # /usr/sbin/vxdctl enable
      
      
    2. Import the shared disk group:

      # /usr/sbin/vxdg -s import diskgroup
      
      
    3. 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:

  1. 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
      
      
  2. 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.

  3. Change directory to the $ORACLE_BASE/oradata/dbname directory.

  4. 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
    
    
  5. 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 (undotbsn) and two redo log files (redon_1, redon_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.

  6. Save the file and note the file name that you specified.

  7. 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.

Verify that the Cluster Software is Configured and Running


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:

  1. 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.

  2. To verify that the Sun Cluster software is running, enter the following command on one of the cluster nodes:

    # /usr/cluster/bin/scstat -n
    
    
  3. 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.

Stop Existing Oracle Processes


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:

  1. Switch user to oracle:

    # su - oracle
    
    
  2. 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.

  3. 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
      
      
  4. 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.

  5. Enter a command similar to the following to stop the listener process:

    $ $ORACLE_HOME/bin/lsnrctl stop listenername
    
    
  6. Repeat this procedure to stop all listeners running on this system and on all other cluster nodes.

Configure the oracle User's Environment

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:

  1. Start a new terminal session, for example, an X terminal (xterm).

  2. Enter the following command to ensure that X Window applications can display on this system:

    $ xhost +
    
    
  3. 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.

  4. If you are not logged in as the oracle user, switch user to oracle:

    $ su - oracle
    
    
  5. To determine the default shell for the oracle user, enter the following command:

    $ echo $SHELL
    
    
  6. 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
      
      
  7. Enter or edit the following line, specifying a value of 022 for the default file mode creation mask:

    umask 022
    
    
  8. If the ORACLE_SID, ORACLE_HOME, or ORACLE_BASE environment variables are set in the file, remove the appropriate lines from the file.

  9. Save the file and exit from the editor.

  10. To run the shell startup script, enter one of the following commands:

    • Bourne, Bash, or Korn shell:

      $ . ./.profile
      
      
    • C shell:

      % source ./.login
      
      
  11. 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).

  12. 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:

    1. Use the df -k command to identify a suitable file system with sufficient free space.

    2. 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
      
      
    3. 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
        
        
  13. 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.

  14. 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
      
      
  15. 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.

  16. 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.