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.

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

Check the Hardware Requirements

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 and platform

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:

# grep "Physical:" /var/adm/syslog/syslog.log

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/swapinfo -a

If necessary, refer to your operating system documentation for information about how to configure additional swap space.

To determine the amount of disk space available in the /tmp directory, enter the following command:

# bdf /tmp

If there is less than 400 MB of disk space available in the /tmp directory, complete one of the following steps:

Delete unnecessary files from the /tmp directory to achieve the required disk space.

Set the TEMP and TMPDIR environment variables when setting the oracle user's environment (described later).

Extend the file system that contains the /tmp directory. If necessary, contact your system administrator for information about extending file systems.

To determine the amount of free disk space on the system, enter the following command:

# bdf

To determine whether the system architecture can run the software, enter the following command:

# /bin/getconf KERNEL_BITS

The expected output from this command is the value 64.

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:

UDP is the default interconnect protocol for RAC and TCP is the interconnect protocol for Oracle CRS.

To use HMP as the interconnect protocol for RAC, you must relink the oracle executable. Refer to the Oracle Database Administrator's Reference for UNIX Systems for more information about enabling HMP for RAC on HP-UX systems.

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

Oracle recommends that you use non-routable IP addresses for the private interfaces, for example: 10.*.*.* or 192.168.*.*. 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/bin/netstat -in

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.

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 version:

PA-RISC (64-bit) systems:

HP-UX 11i (11.11) PA-RISC

Itanium systems:

HP-UX 11i v2 (11.23)

Oracle Spatial

HP-UX Developer's Toolkit - X11, Motif, and Imake:

X11MotifDevKit

Note: This software is required only to build the sample programs.

Real Application Clusters

Note: HP Serviceguard is required only if you want to use shared logical volumes for CRS or database files.

HP-UX 11i (11.11):

HP Serviceguard A11.15.00 or higher

HP Serviceguard Extension for RAC A11.15.00 or higher

HyperFabric software - Required if you want to use Hyper Messaging protocol as the cluster interconnect

HP-UX 11i v2 (11.23):

HP Serviceguard A11.15.01 or higher

HP Serviceguard Extension for RAC A11.15.01 or higher

Oracle Messaging Gateway (PA-RISC only)

Oracle Messaging Gateway supports the integration of Oracle Streams Advanced Queuing (AQ) with the following software:

To determine whether a bundle, product, or fileset is installed, enter a command similar to the following, where level is bundle, product, or fileset:

# /usr/sbin/swlist -l level | more

If a required bundle, product, or fileset is not installed, you must install it. Refer to your operating system or software documentation for information about installing products.

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:

There may be more recent versions of the patches listed installed on the system. If a listed patch is not installed, determine whether a more recent version is installed before installing the version listed.

Installation Type or Product

Requirement

All installations

Quality Pack bundle:

HP-UX 11i (11.11):

HP-UX 11i Quality Pack (GOLDQPK11i), June 2003 or later:

GOLDAPPS11i
GOLDBASE11i

HP-UX 11i v2 (11.23):

None currently required

All installations

Patches for HP-UX 11i (11.11):

PHCO_28123: cumulative SAM patch

PHKL_29198: Psets Enablement Patch; top(1)

PHNE_28476: Cumulative STREAMS Patch

PHNE_28923: LAN product cumulative patch

PHSS_28871: ld(1) and linker tools cumulative patch

PHSS_28880: HP aC++ -AA runtime libraries (aCC A.03.50)

Patches for HP-UX 11i v2 (11.23):

PHSS_29658: Aries cumulative patch

PHSS_29660: linker + fdp cumulative patch

All installations

Patches for JDK on HP-UX 11i (11.11):

PHCO_26331: mountall cumulative patch, Dev IDs enabler

PHCO_29109: Pthread enhancement and fixes

PHKL_25468: eventport (/dev/poll) pseudo driver

PHKL_25842: Thread Abort

PHKL_25993: thread nostop for NFS, rlimit, Ufalloc fix

PHKL_25994: Thread NOSTOP, Psets Enablement, Ufalloc

PHKL_25995: ufalloc;VxFS3.5;SPP fragmentation

PHKL_26468: Shared synchronization performance support

PHKL_28489: copyin EFAULT, LDCD access type

Note: Refer to the following Web site for information about additional patches that might be required by JDK 1.4.2:

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 OSDBA group (dba)

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.

The OSOPER group (oper)

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.

An unprivileged user

On HP-UX systems, you must create a new unprivileged user. The user that you create 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.

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

Creating the Oracle Software Owner User

You must create an Oracle software owner user in the following circumstances:

If an Oracle software owner user does not exist, for example, if this is the first installation of Oracle software on the system

If an Oracle software owner user exists, but you want to use a different UNIX user, with different group membership, to give database administrative privileges to those groups in a new Oracle Database installation

Determine Whether an Existing Oracle Software Owner User Exists

To determine whether an Oracle software owner user named oracle exists, enter the following command:

# id oracle

If the oracle user exists, the output from this command is similar to the following:

uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)

If the user exists, determine whether you want to use the existing user or create a new user. If you want to use the existing user, ensure that the user's primary group is the Oracle Inventory group and that it is a member of the appropriate OSDBA and OSOPER groups. Refer to one of the following sections for more information:

Note:

If necessary, contact your system administrator before using or modifying an existing user.

If you want to use the existing Oracle software owner user, and the user's primary group is the Oracle Inventory group, refer to the "Creating an Unprivileged User" section.

If the oracle user exists, but its primary group is not oinstall or it is not a member of the appropriate OSDBA or OSOPER groups, enter a command similar to the following to modify it. Specify the primary group using the -g option and any required secondary groups using the -G option:

# /usr/sbin/usermod -g oinstall -G dba[,oper] oracle

Creating an Unprivileged User

You must create a new unprivileged local user to own the extjob executable. You can use any user name for this user, but this document uses the name extjob. To create the extjob user, enter the following command on all cluster nodes:

# /usr/sbin/useradd extjob

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:

Enter following command:

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

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.

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.

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:

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:

Each command should return only the date setting on the specified node. If a node prompts for a password or displays any other text, then user equivalence is not set up correctly on that node. In this case, verify that the /etc/hosts.equiv (or ~oracle/.rhosts) file has the correct entries.

Grant Privileges to the OSDBA Group

To enhance the performance of the software on HP-UX systems, you must grant several system privileges to the OSDBA group. Complete the following steps if you are installing the software on HP-UX:

Using any text editor, open the /etc/privgroup file, or create it if necessary.

Add or edit the following line, which begins with the name of the OSDBA group, specifying the privileges MLOCK, RTPRIO, and RTSCHED, that you want to grant to this group every time the system restarts:

dba MLOCK RTPRIO RTSCHED

Save the file and exit from the text editor.

Enter the following command to grant the privileges to the OSDBA group:

# /usr/sbin/setprivgrp -f /etc/privgroup

Enter the following command to verify that the privileges are set correctly:

# /usr/bin/getprivgrp dba

Repeat this procedure on all of the other cluster nodes.

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

On all cluster nodes, verify that the kernel parameters shown in the following table are set either to the formula shown, or 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 Formula or Value

ksi_alloc_max

(nproc*8)

max_thread_proc

1024

maxdsiz

1073741824 (1 GB)

maxdsiz_64bit

2147483648 (2 GB)

maxssiz

134217728 (128 MB)

maxssiz_64bit

1073741824 (1 GB)

maxswapchunks (PA-RISC only)

16384

maxuprc

((nproc*9)/10)

msgmap

(msgtql+2)

msgmni

(nproc)

msgseg

32767

msgtql

(nproc)

ncsize (PA-RISC)

(ninode+vx_ncsize)

ncsize (Itanium)

(ninode+1024)

nfile

(15*nproc+2048)

nflocks

(nproc)

ninode

(8*nproc+2048)

nkthread

(((nproc*7)/4)+16)

nproc

4096

semmap (PA-RISC only)

(semmni+2)

semmni

(nproc)

semmns

(semmni*2)

semmnu

(nproc-4)

semvmx

32767

shmmax

The size of physical memory or 1073741824 (0X40000000), whichever is greater.

Note: To avoid performance degradation, the value should be greater than or equal to the size of the SGA.

If you are using Hyper Messaging protocol as the cluster interconnect on PA-RISC systems, the value of this parameter must be less than 4 GB.

shmmni

512

shmseg

120

vps_ceiling

64

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 or formula specified for these kernel parameters, and to change them if necessary, follow these steps:

Follow these steps, depending on your platform:

PA-RISC:

Optionally, set the DISPLAY environment variable to specify the display of the local system:

Check the value or formula specified for each of these parameters and, if necessary, modify that value or formula.

If necessary, refer to the SAM online help for more information about completing this step.

Note:

If you modify the value of a parameter that is not dynamic, you must restart the system.

Itanium:

Enter the following command to start the kcweb application:

# /usr/sbin/kcweb -F

Check the value or formula specified for each of these parameters and, if necessary, modify that value or formula.

If necessary, refer to the kcweb online help for more information about completing this step.

Note:

If you modify the value of a parameter that is not dynamic, you must restart the system.

If necessary, when the system restarts, log in and switch user to root.

Complete this procedure on all other cluster nodes.

Identify Required Software Directories

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.

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:

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 must be on a local file system.

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

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:

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 /etc/oratab

If the oratab file exists, it contains lines similar to the following:

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 up to 3 GB of free disk space.

To determine the free disk space on the file system where the Oracle base directory is located, enter the following command:

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.

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:

Use the bdf 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 must be a local file system.

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:

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

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:

To use raw devices (disks or logical volumes) for Oracle CRS or database file storage, refer to the "Configure Raw Devices" 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:

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:

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 raw devices for database files and ASM for recovery files if you choose.

For RAC installations, if you choose to enable automated backups, 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.

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:

View the contents of the oratab file to determine whether an ASM instance is configured on the system:

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

Configuring Disks for ASM

To configure disks for use with ASM on HP-UX, follow these steps:

If necessary, install the shared disks that you intend to use for the ASM disk group.

To make sure that the disks are available, enter the following command on every node:

Configure Raw Devices

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 Disk Devices or Raw Logical Volumes

The following subsections describe how to configure raw disk devices or raw logical volumes on HP-UX:

Follow the procedures described in this section if you are installing RAC on a cluster without HP Serviceguard Extension for RAC and you intend to use raw disk devices for CRS or database file storage.

If you are installing RAC on an HP-UX cluster without HP Serviceguard Extension for RAC, you must use shared raw disk devices for the Cluster Ready Services (CRS) files. You can also use shared raw disk devices for database file storage, however, Oracle recommends that you use ASM to store database files in this situation. This section describes how to configure the shared raw disk devices for CRS files (Oracle Cluster Registry and CRS voting disk) and database files.

Table 3-1 lists the number and size of the raw disk devices that you must configure for database files. Table 3-2 lists the number and size of the raw disk devices that you must configure for CRS files.

Note:

Because each file requires exclusive use of a complete disk device, Oracle recommends that, if possible, you use disk devices with sizes that closely match the size requirements of the files that they will store. You cannot use the disks that you choose for these files for any other purpose.

Table 3-1 Raw Disk Devices Required for Database Files on HP-UX

Number

Size (MB)

Purpose and Sample Alternative Device File 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 3-2 Raw Disk Devices Required for CRS Files on HP-UX

Number

Size (MB)

Purpose and Sample Alternative Device File 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.

This command displays information about each disk attached to the system, including the block device name (/dev/dsk/cxtydz) and the character raw device name (/dev/rdsk/cxtydz).

If the ioscan command does not display device name information for a device that you want to use, enter the following command to install the special device files for any new devices:

# /usr/sbin/insf -e

For each disk that you want to use, enter the following command on any node to verify that it is not already part of an LVM volume group:

# /sbin/pvdisplay /dev/dsk/cxtydz

If this command displays volume group information, the disk is already part of a volume group. The disks that you choose must not be part of an LVM volume group.

Note:

If you are using different volume management software, for example VERITAS Volume Manager, refer to the appropriate documentation for information about verifying that a disk is not in use.

If the ioscan command shows different device names for the same device on any node, follow these steps on every node:

Change directory to the /dev/rdsk directory.

Enter the following command to list the raw disk device names and their associated major and minor numbers:

# ls -la

The output from this command is similar to the following for each disk device:

crw-r--r-- 1 bin sys 188 0x032000 Nov 4 2003 c3t2d0

In this example, 188 is the device major number and 0x32000 is the device minor number.

Enter the following command to create a new device file for the disk that you want to use, specifying the same major and minor number as the existing device file:

Note:

Oracle recommends that you use the alternative device file names shown in the previous table.

# mknod ora_ocr_raw_100m c 188 0x032000

Repeat these steps on each node, specifying the correct major and minor numbers for the new device files on each node.

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 device that you want to use:

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 you created an alternative device file for the device, set the permissions on that device file.

OCR:

# chown root:oinstall /dev/rdsk/cxtydz
# chmod 640 /dev/rdsk/cxtydz

CRS voting disk or database files:

# chown oracle:dba /dev/rdsk/cxtydz
# chmod 660 /dev/rdsk/cxtydz

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:

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 disk 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 devices use alternative disk device file names. Make sure that the device file name that you specify identifies the same disk device on all nodes.

The alternative device file names suggested in the previous table include the database object identifier that you must use in this mapping file. For example, in the following alternative disk device file 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.

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:

The following subsections describe how to create logical volumes using the command line. If you prefer, you can use SAM to complete the same tasks. Refer to the HP-UX documentation for more information about using SAM.

This section describes how to configure shared raw logical volumes for Oracle CRS and database file storage. The procedures in this section describe how to create a new shared volume group that contains the logical volumes required for both types of files.

To use shared raw logical volumes, HP Serviceguard Extension for RAC must be installed on all cluster nodes. If HP Serviceguard Extension for RAC is not installed, you can use shared raw disk devices to store the Oracle CRS or database files. However, Oracle recommends that you use this method only for the CRS files and use an alternative method such as ASM for database file storage.

Before you continue, review the following guidelines which contain important information about using shared logical volumes with this release of Oracle Real Application Clusters:

You must use shared volume groups for Oracle CRS and database files.

If you specify raw logical volumes for the Oracle Cluster Registry and Oracle CRS voting disk during the Oracle CRS installation, the installation process configures the Oracle CRS startup scripts to activate the volume group that contains these logical volumes when Oracle CRS starts.

Note:

You do not need to create a Serviceguard package to activate the volume group that contains the Oracle CRS files.

The Oracle CRS files require less than 200 MB of disk space. To make efficient use of the disk space in a volume group, Oracle recommends that you use the same shared volume group for the logical volumes for both the CRS files and the database files.

If you are upgrading an existing Oracle9i release 2 RAC installation that uses raw logical volumes, you can use the existing SRVM configuration repository logical volume for the OCR and create a new logical volume in the same volume group for the Oracle CRS voting disk. However, before you install Oracle CRS, you must remove this volume group from any Serviceguard package that currently activates it.

See Also:

For information about removing a volume group from a Serviceguard package, refer to the HP Serviceguard or HP Serviceguard Extension for RAC documentation.

Note:

If you are upgrading a database, you must also create a new logical volume for the SYSAUX tablespace. Refer to the "Create Raw Logical Volumes in the New Volume Group" section for more information about the requirements for the Oracle CRS voting disk and SYSAUX logical volumes.

You must use either your own startup script or a Serviceguard package to activate new or existing volume groups that contain only database files (not Oracle CRS files).

See Also:

For information about creating a Serviceguard package to activate a shared volume group for RAC, refer to the HP Serviceguard documentation.

All shared volume groups that you intend to use for Oracle CRS or database files must be activated in shared mode before you start the installation.

All shared volume groups that you are using for RAC, including the volume group that contains the Oracle CRS files, must be specified in the cluster configuration file using the parameter OPS_VOLUME_GROUP.

Note:

If you create a new shared volume group for RAC on an existing HP Serviceguard cluster, you must reconfigure and restart the cluster before installing Oracle CRS. Refer to the HP Serviceguard documentation for information about configuring the cluster and specifying shared volume groups.

The procedures in this section describe how to create basic volumes groups and volumes. If you want to configure more complex volumes, using mirroring for example, use this section in conjunction with the HP Serviceguard documentation.

Disable Operating System Activation of Shared Volume Groups

To prevent the operating system from activating shared volume groups when it boots, you must edit the /etc/lvmrc file on every node, as follows:

Create a backup copy of the /etc/lvmrc file:

# cp /etc/lvmrc /etc/lvmrc_orig

Open the /etc/lvmrc file in any text editor and search for the AUTO_VG_ACTIVATE flag.

If necessary, change the value of the AUTO_VG_ACTIVATE flag to 0, to disable automatic volume group activation, as follows:

AUTO_VG_ACTIVATE=0

Search for the custom_vg_activation function in the /etc/lvmrc file.

Add vgchange commands to the function, as shown in the following example, to automatically activate existing local volume groups:

In this example, 64 is the major number used by all volume group devices and 0x000000 and 0x010000 are the minor numbers used by volume groups vg00 and vg01 respectively. Minor numbers have the format 0xnn0000, where nn is a number in the range 00 to the value of the maxvgs kernel parameter minus 1. The default value for the maxvgs parameter is 10, so the default range is 00 to 09.

Identify an appropriate minor number that is unused on all nodes in the cluster.

To create the volume group and activate it, enter commands similar to the following:

/dev/dsk/cxtydz... is a list of one or more block device names for the disks that you want to add to the volume group

Create Raw Logical Volumes in the New Volume Group

To create the required raw logical volumes in the new volume 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 3-3 lists the number and size of the logical volumes that you must create for database files. Table 3-4 lists the number and size of the logical volumes that you must create for CRS files.

Table 3-3 Raw Logical Volumes Required for Database Files on HP-UX

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 3-4 Raw Logical Volumes Required for CRS Files on HP-UX

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.

To create each required logical volume, enter a command similar to the following:

# /sbin/lvcreate -n LVname -L size /dev/vg_name

In this example:

LVname 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 that you chose for the database in step 1.

vg_name is the name of the volume group where you want to create the logical volume

size is the size of the logical volume in megabytes

The following example shows a sample command used to create an 800 MB logical volume in the oracle_vg volume group for the SYSAUX tablespace of a database named test:

# /sbin/lvcreate -n test_sysaux_raw_800m -L 800 /dev/oracle_vg

Change the owner, group, and permissions on the character device files associated with the logical volumes that you created, as follows:

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

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.

Verify the Cluster Software Configuration

Note:

HP Serviceguard is not required. However, if it is installed, Oracle CRS can integrate with it.

To verify that the HP Serviceguard software is running:

If necessary, configure (or reconfigure) the cluster.

Verify that HP Serviceguard is configured to start automatically at runlevel 3.

To verify that HP Serviceguard is running correctly, enter the following command:

# /usr/sbin/cmviewcl -v

Verify that the cluster status is up, and that all nodes are up and running.

If the cluster is not running, enter the following command to start it:

# /usr/sbin/cmruncl

If any nodes are not running, enter a command similar to the following to start the cluster daemon on those nodes:

# /usr/sbin/cmrunnode nodename1 nodename2...

If you intend to use Hyper Messaging protocol as the cluster interconnect, enter the following command to verify that the HyperFabric software is configured properly:

# /opt/clic/bin/clic_stat -d NET

In the output from this command, verify that all of the cluster nodes are listed in the Node Table Entries section. If a node is missing, refer to the HyperFabric documentation for more information about configuring the software.

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:

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.

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.

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:

Set the default file mode creation mask (umask) to 022 in the shell startup file.

Set the DISPLAY and ORACLE_BASE environment variables.

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 bdf 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:

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.