This chapter explains how to install Sun Cluster Support for Oracle RAC on your Sun Cluster nodes.
The following table summarizes the installation tasks and provides cross-references to detailed instructions for performing the tasks.
Perform these tasks in the order in which they are listed in the table.
Table 1–1 Tasks for Installing Sun Cluster Support for Oracle RAC
Task |
Instructions |
---|---|
Plan your installation | |
Prepare the Sun Cluster nodes | |
Install data service packages | |
SPARC: Install the UNIX Distributed Lock Manager |
Oracle Real Application Clusters (RAC) is an application that can run on more than one machine concurrently. On SolarisTM 1O OS, Oracle RAC can run either in the global-cluster voting nodes of the global cluster or in a zone cluster. An Oracle RAC installation is entirely contained within one cluster, either a global cluster or a specific zone cluster. Keeping the Oracle RAC installation in one cluster ensures the support of multiple independent Oracle RAC installations concurrently, where each Oracle RAC installation can be of a different version or use different options, such as storage. Sun Cluster Support for Oracle RAC enables you to run Oracle RAC on Sun Cluster nodes and to manage Oracle RAC by using Sun Cluster commands.
In earlier versions of Oracle, this application is referred to as Oracle Parallel Server. In this book, references to Oracle RAC also apply to Oracle Parallel Server unless this book explicitly states otherwise.
Configuring this data service involves configuring resources for the following components of an Oracle RAC installation with Sun Cluster software:
The RAC framework. These resources enable Oracle RAC to run with Sun Cluster software. The resources also enable reconfiguration parameters to be set by using Sun Cluster commands. You must configure resources for the RAC framework. For more information, see Registering and Configuring the RAC Framework Resource Group.
Storage for Oracle files. These resources provide fault monitoring and automatic fault recovery for volume managers and file systems that store Oracle files. Configuring storage resources for Oracle files is optional. For more information, see Registering and Configuring Storage Resources for Oracle Files.
Oracle RAC database instances. The features that these resources provide depend on the version of Oracle that you are using:
Oracle 10g Release 2 and 11g. These resource types enable Oracle Cluster Ready Services (CRS) and Sun Cluster software to interoperate. These resource types do not provide fault monitoring and automatic fault recovery for Oracle 10g Release 2 or 11g RAC. The Oracle CRS software provides this functionality. This statement is not applicable to Oracle 10g Release 1.
Oracle 9i. These resource types provide fault monitoring and automatic fault recovery for Oracle RAC. The automatic fault recovery that these resource types provide supplements the automatic fault recovery that the Oracle RAC software provides.
Configuring resources, which enable Sun Cluster software to administer Oracle RAC database instances, is optional. For more information, see Configuring Resources for Oracle RAC Database Instances.
When you use Oracle RAC in a zone cluster, ensure that the zone cluster is not configured with the /opt directory as an inherited read-only directory. For an Oracle RAC configuration in a zone cluster, the /opt file system must be writable and unique to each zone. If the zone cluster that you intended to use for Oracle RAC is configured with an inherit-pkg-dir resource for the /opt directory, destroy and recreate the zone cluster or create a new zone cluster to meet this requirement.
The following sections contain additional preinstallation information:
SPARC: Processor Architecture Requirements for Oracle Components
Using Oracle Data Guard With Sun Cluster Support for Oracle RAC
Using the Oracle Real Application Clusters Guard Option With Sun Cluster 3.2 11/09 Software
Before you begin the installation, note the hardware and software requirements in the subsections that follow.
Sun Cluster Support for Oracle RAC requires a functioning cluster with the initial cluster framework already installed. See Sun Cluster Software Installation Guide for Solaris OS for details about initial installation of cluster software.
Verify that you have obtained and installed the appropriate licenses for your software. If you install your licenses incorrectly or incompletely, the nodes might fail to boot correctly.
For example, if you are using VxVM with the cluster feature, verify that you have installed a valid license for the Volume Manager cluster feature by running the vxlicrep command.
Check with a Sun Enterprise Services representative for the current supported topologies for Sun Cluster Support for Oracle RAC, cluster interconnect, storage management scheme, and hardware configurations.
Ensure that you have installed all the applicable software patches for the Solaris OS, Sun Cluster, Oracle, and volume manager software. If you need to install any Sun Cluster Support for Oracle RAC patches, you must apply these patches after you install the data service packages.
This section provides the following information about storage management for Oracle RAC:
Sun Cluster Support for Oracle RAC enables you to use the storage management schemes for Oracle files that are listed in the following table. The table summarizes the types of Oracle files that each storage management scheme can store. Ensure that you choose a combination of storage management schemes that can store all types of Oracle files.
The meaning of each symbol in the table is as follows:
Indicates that the storage management scheme can store the type of Oracle file.
Indicates that the storage management scheme cannot store the type of Oracle file.
Oracle File Type |
Storage Management Scheme |
|||||||
---|---|---|---|---|---|---|---|---|
- |
- |
- |
+ |
+ |
- |
+ |
+ |
|
- |
- |
- |
+ |
+ |
- |
+ |
+ |
|
- |
- |
- |
+ |
+ |
- |
+ |
+ |
|
- |
- |
- |
+ |
+ |
+ |
+ |
- |
|
- |
- |
- |
+ |
+ |
- |
+ |
+ |
|
- |
- |
- |
+ |
+ |
- |
+ |
+ |
|
+ |
+ |
+ |
+ |
+ |
+ |
- |
- |
|
+ |
+ |
+ |
+ |
+ |
+ |
- |
- |
|
+ |
+ |
+ |
+ |
+ |
+ |
- |
- |
|
- |
- |
- |
+ |
+ |
+ |
+ |
- |
|
- |
- |
- |
+ |
+ |
+ |
+ |
- |
|
- |
- |
- |
+ |
+ |
+ |
- |
- |
|
+ |
+ |
+ |
+ |
+ |
- |
+ |
- |
|
+ |
+ |
+ |
+ |
+ |
- |
+ |
- |
Some types of files are not included in all releases of Oracle RAC. For information about which types of file are included in the release that you are using, see your Oracle documentation.
Oracle Clusterware disks such as Oracle cluster registry (OCR) and voting disks are supported on the following storage management schemes:
Solaris Volume Manager for Sun Cluster
Solaris Volume Manager for Sun Cluster is supported only with Oracle RAC. Solaris Volume Manager for Sun Cluster with Oracle Parallel Server is not supported.
Veritas Volume Manager (VxVM)
VxVM is supported only on the SPARC platform.
Hardware redundant array of independent disks (RAID) support
Sun QFS shared file system with hardware RAID support or with Solaris Volume Manager for Sun Cluster
Qualified network-attached storage (NAS)
You can use the following storage management schemes for the Oracle RAC database:
Solaris Volume Manager for Sun Cluster
Solaris Volume Manager for Sun Cluster is supported only with Oracle RAC. Solaris Volume Manager for Sun Cluster with Oracle Parallel Server is not supported.
Veritas Volume Manager (VxVM) with the cluster feature
VxVM is supported only on the SPARC platform.
Hardware redundant array of independent disks (RAID) support
Sun QFS shared file system with hardware RAID support or with Solaris Volume Manager for Sun Cluster
Qualified network-attached storage (NAS) devices
Oracle Automatic Storage Management (ASM)
You can install the Oracle binary files and Oracle configuration files on one of the following locations.
The local disks of each cluster node. See Using Local Disks for Oracle Binary Files and Oracle Configuration Files for additional information.
A shared file system from the following list:
A Sun QFS shared file system
A cluster file system
A file system on a qualified NAS device
See Using a Shared File System for Oracle Binary Files and Oracle Configuration Files for additional information.
Placing the Oracle binary files and Oracle configuration files on the individual cluster nodes enables you to upgrade the Oracle application later without shutting down the data service.
Some versions of Oracle require you to shut down the data service during an upgrade. To determine whether you can upgrade the Oracle application without shutting down the data service, see your Oracle documentation.
The disadvantage is that you then have several copies of the Oracle application binary files and Oracle configuration files to maintain and administer.
To simplify the maintenance of your Oracle installation, you can install the Oracle binary files and Oracle configuration files on a shared file system. The following shared file systems are supported:
The Sun QFS shared file system
The cluster file system
If you use the cluster file system, decide which volume manager to use:
Solaris Volume Manager
VxVM without the cluster feature
VxVM is supported only on the SPARC platform.
A file system on a qualified NAS device
If you put the Oracle binary files and Oracle configuration files on a shared file system, you have only one copy to maintain and manage. However, you must shut down the data service in the entire cluster to upgrade the Oracle application. If a short period of downtime for upgrades is acceptable, place a single copy of the Oracle binary files and Oracle configuration files on a shared file system.
You can use the following storage management schemes for running Oracle RAC in a zone cluster, depending on the version of Oracle RAC you are running.
If you are using Oracle RAC 10g or Oracle RAC 11g, the following storage management schemes are supported:
Sun QFS shared file system with Solaris Volume Manager
Sun QFS shared file system with hardware RAID support
Solaris Volume Manager for Sun Cluster
If you are using Oracle RAC 9i, the following storage management schemes are supported:
Sun QFS shared file system with Solaris Volume Manager
Sun QFS shared file system with hardware RAID support
Solaris Volume Manager for Sun Cluster
Before you decide which architecture to use for the Oracle UDLM (SPARC) and the Oracle relational database management system (RDBMS), note the following points.
The architecture of both Oracle components must match. For example, if you have 64-bit architecture for your Oracle UDLM, you must have 64-bit architecture for your RDBMS.
If you have 32-bit architecture for your Oracle components, you can boot the node on which the components reside in either 32-bit mode or 64-bit mode. However, if you have 64-bit architecture for your Oracle components, you must boot the node on which the components reside in 64-bit mode.
You must use the same architecture when you boot all the nodes. For example, if you boot one node to use 32-bit architecture, you must boot all the nodes to use 32-bit architecture.
You can use Sun Cluster Support for Oracle RAC with Oracle Data Guard. To configure Sun Cluster Support for Oracle RAC with Oracle Data Guard, perform the tasks in this guide. The tasks for clusters that are to be used in an Oracle Data Guard configuration are identical to the tasks for a standalone cluster.
For information about the installation, administration, and operation of Oracle Data Guard, see your Oracle documentation.
For information about the installation, administration, and operation of the Oracle Real Application Clusters Guard option, see your Oracle documentation. If you plan to use this product option with Sun Cluster 3.2 11/09 software, note the points in the subsections that follow before you install Sun Cluster 3.2 11/09 software.
This section describes the following restrictions when you use Oracle Real Application Clusters Guard in a Sun Cluster configuration:
If you use the Oracle Real Application Clusters Guard option with Sun Cluster 3.2 11/09 software, the following restrictions apply to hostnames that you use in your cluster:
Hostnames cannot contain special characters.
You cannot change the hostnames after you install Sun Cluster 3.2 11/09 software.
For more information about these restrictions and any other requirements, see the Oracle documentation.
If you use the Oracle Real Application Clusters Guard option with Sun Cluster 3.2 11/09 software, do not use Sun Cluster commands to perform the following operations:
Manipulating the state of resources that Oracle Real Application Clusters Guard installs. Using Sun Cluster commands for this purpose might cause failures.
Querying the state of the resources that Oracle Real Application Clusters Guard installs. This state might not reflect the actual state. To check the state of the Oracle Real Application Clusters Guard, use the commands that Oracle supplies.
Preparing the Sun Cluster nodes modifies the configuration of the operating system to enable Oracle RAC to run on Sun Cluster nodes. Preparing the Sun Cluster nodes and disks involves the following tasks:
Bypassing the NIS name service
Creating the database administrator (DBA) group and the DBA user accounts
Configuring shared memory for the Oracle RAC software
Perform these tasks on all nodes where Sun Cluster Support for Oracle RAC can run. If you do not perform these tasks on all nodes, the Oracle installation is incomplete. An incomplete Oracle installation causes Sun Cluster Support for Oracle RAC to fail during startup.
To enable the Oracle RAC to run in a zone cluster, you need to perform the following additional tasks:
Configuring shared memory for Oracle RAC software in a zone cluster
Setting necessary privileges for Oracle RAC software in a zone cluster
Configuring logical hostname resources for Oracle RAC software in a zone cluster
This section contains the following information:
How to Configure Shared Memory for the Oracle RAC Software in the Global Cluster
How to Configure Shared Memory for the Oracle RAC Software in a Zone Cluster
How to Set the Necessary Privileges for Oracle RAC Software in a Zone Cluster
Before you prepare the Sun Cluster nodes, ensure that all preinstallation tasks for Oracle RAC are completed. For more information, see your Oracle RAC documentation.
Bypassing the NIS name service protects the Sun Cluster Support for Oracle RAC data service against a failure of a cluster node's public network. A failure of a cluster node's public network might cause the NIS name service to become unavailable. If Sun Cluster Support for Oracle RAC refers to the NIS name service, unavailability of the name service might cause the Sun Cluster Support for Oracle RAC data service to fail.
Bypassing the NIS name service ensures that the Sun Cluster Support for Oracle RAC data service does not refer to the NIS name service when the data service sets the user identifier (ID). The Sun Cluster Support for Oracle RAC data service sets the user ID when the data service starts or stops the database.
Become superuser on all nodes where Sun Cluster Support for Oracle RAC can run.
On each node, include the following entries in the /etc/nsswitch.conf file.
passwd: files [NOTFOUND=return] nis [TRYAGAIN=0] publickey: files [NOTFOUND=return] nis [TRYAGAIN=0] project: files [NOTFOUND=return] nis [TRYAGAIN=0] group: files [NOTFOUND=return] nis [TRYAGAIN=0]
For more information about the /etc/nsswitch.conf file, see the nsswitch.conf(4) man page.
Go to How to Create the DBA Group and the DBA User Accounts.
In installations of Oracle RAC with Sun Cluster software, the DBA group is normally named dba. This group normally contains the root user and the oracle user.
This configuration of users and groups differs from the configuration that is described in the Oracle documentation for a standalone installation of Oracle RAC. A standalone installation of Oracle RAC uses a primary DBA group that is named oinstall and a secondary group that is named dba. Some applications also require a secondary group that is named oper. For more information, see your Oracle documentation.
Perform this task on each cluster node.
On the cluster node where you are performing this task, become superuser.
Add an entry for the DBA group and potential users in the group to the /etc/group file.
# echo 'group-name:*:group-id:user-list' >> /etc/group |
Specifies the name of the group for which you are adding an entry. This group is normally named dba.
Specifies the group's unique numerical ID (GID) within the system.
Specifies a comma-separated list of the user names that are allowed in the group. Ensure that the list contains the names of all DBA users that are required. This group normally contains the root user and the oracle user.
Ensure that the entry is identical on each node that can run Sun Cluster Support for Oracle RAC.
You can create the name service entries in a network name service, such as the Network Information Service (NIS) or NIS+, so that the information is available to the data service clients. You can also create entries in the local /etc files to eliminate dependency on the network name service.
Create the home directory of each potential user in the DBA group that you defined in Step 2.
You are not required to create a home directory for the root user.
For each potential user whose home directory you are creating, type the following command:
# mkdir -p user-home |
Specifies the full path of the home directory that you are creating.
Add each potential user in the DBA group that you defined in Step 2 to the system.
You are not required to add the root user.
Use the useradd(1M) command to add each user. Adding a user to the system adds an entry for the user to the following files:
/etc/passwd
/etc/shadow
# useradd -u user-id -g group-name -d user-home \ [ -s user-shell] user-name |
Specifies the user's unique numerical ID (UID) within the system.
Specifies the name of the user group of which the user is a member. You must specify the DBA group that you defined in Step 2.
Specifies the full path of the user's home directory. You must specify the home directory that you created for the user in Step 3.
Optionally specifies the full path name of the program that is to be used as the user's shell when the user logs in. If you omit the -s option, the system uses the /bin/sh program by default. If you specify the -s option, user-shell must specify a valid executable file.
Specifies the user name of the user that you are adding. You must specify the name of a potential user in the DBA group that you defined in Step 2.
Ensure that each user is identical on each node that can run Sun Cluster Support for Oracle RAC.
Set the password of each user that you added in Step 4.
Use the passwd(1) command to set the password of each user.
Type the following command:
# password user-name |
Specifies the user name of the user whose password you are setting. You must specify the name of a user in the DBA group that you added in Step 4.
The passwd command prompts you for the password.
In response to the prompt, type the password and press Return.
The passwd command prompts you to retype the password.
In response to the prompt, retype the password and press Return.
Change the ownership of each home directory that you created in Step 3 as follows:
Owner: the user for which you created the home directory
Group: the DBA group that you defined in Step 2
For each home directory for which you are changing ownership, type the following command:
# chown user-name:group-name user-home |
Specifies the user name of the user for whose home directory you are changing ownership. You must specify the name of a user in the DBA group that you added in Step 4.
Specifies the name of the user group of which the user is a member. You must specify the DBA group that you defined in Step 2.
Specifies the full path of the user's home directory. You must specify the home directory that you created for the user in Step 3.
Create a subdirectory of the /var/opt directory for each user in the DBA group that you added in Step 4.
For each subdirectory that you are creating, type the following command:
# mkdir /var/opt/user-name |
Specifies the user name of the user whose subdirectory of the /var/opt directory you are creating. You must specify the name of a user in the DBA group that you added in Step 4.
Change the ownership of each directory that you created in Step 7 as follows:
Owner: the user for which you created the directory
Group: the DBA group that you defined in Step 2
For each directory for which you are changing ownership, type the following command:
# chown user-name:group-name /var/opt/user-name |
Specifies the user name of the user for whose home directory you are changing ownership. You must specify the name of a user in the DBA group that you added in Step 4.
Specifies the name of the user group of which the user is a member. You must specify the DBA group that you defined in Step 2.
This example shows the sequence of commands for creating the DBA group dba, which is to contain the users root and oracle.
The dba group and the oracle user are created as follows:
The GID of the dba group is 520.
The home directory of the oracle user is /Oracle-home.
The UID of the oracle user is 120.
The oracle user's login shell is the Korn shell.
# echo 'dba:*:520:root,oracle' >> /etc/group # mkdir /Oracle-home # useradd -u 120 -g dba -d /Oracle-home -s /bin/ksh oracle # passwd oracle New Password:oracle Re-enter new Password:oracle passwd: password successfully changed for oracle # chown oracle:dba /Oracle-home # mkdir /var/opt/oracle # chown oracle:dba /var/opt/oracle |
The following man pages:
Go to How to Configure Shared Memory for the Oracle RAC Software in the Global Cluster.
Perform this task only if you are using the Solaris 10 OS. If you are using the Solaris 9 OS, perform the task for configuring kernel parameters in your Oracle RAC documentation.
To enable the Oracle RAC software to run correctly, you must ensure that sufficient shared memory is available on all the cluster nodes. Perform this task on each cluster node.
Become superuser on a cluster node.
Update the /etc/system file with the shared memory configuration information.
You must configure these parameters on the basis of the resources that are available in the cluster. However, the value of each parameter must be sufficient to enable the Oracle RAC software to create a shared memory segment that conforms to its configuration requirements. For the minimum required value of each parameter, see your Oracle documentation.
The following example shows entries to configure in the /etc/system file.
*SHARED MEMORY/ORACLE set shmsys:shminfo_shmmax=4294967295 |
Shut down and reboot each node whose /etc/system file you updated in Step 2.
Before you reboot, you must ensure that any volume manager software that is already installed is completely installed. An incomplete installation of volume manager software causes a panic. If you use VxVM, also ensure that you have installed the software and that the license for the VxVM cluster feature is valid. Otherwise, a panic occurs when you reboot. For information about how to recover from a node panic during installation, see Node Panic During Initialization of Sun Cluster Support for Oracle RAC.
For detailed instructions, see Shutting Down and Booting a Single Node in a Cluster in Sun Cluster System Administration Guide for Solaris OS.
Go to Installing the Sun Cluster Support for Oracle RAC Packages.
To configure shared memory for the Oracle RAC software in a zone cluster, perform the following steps:
Perform the steps to configure the shared memory in a global cluster.
For detailed instructions on configuring the shared memory in a global cluster, see How to Configure Shared Memory for the Oracle RAC Software in the Global Cluster.
Perform the similar steps in each zone cluster.
These steps do not affect the actual shared memory control for the zone cluster. You perform these steps to help Oracle dbca utility enables you to set the database memory allocation. If the Oracle dbca utility is not used for RAC database creation, you can skip these steps in the zone cluster.
Perform the following steps, if you want to limit the memory used for the zone cluster.
Become superuser on the global cluster node that hosts the zone cluster.
Configure the capped-memory property attributes physical, swap, and locked by using the clzonecluster command.
#clzonecluster configure zoneclustername clzonecluster:zoneclustername> add capped-memory clzonecluster:cz1-2n:capped-memory> set physical=memsize clzonecluster:cz1-2n:capped-memory> set swap=memsize clzonecluster:cz1-2n:capped-memory> set locked=memsize clzonecluster:cz1-2n:capped-memory> end clzonecluster:cz1-2n>commit |
Specifies the physical memory size.
Specifies the swap memory size.
Specifies the limit of the shared memory segment size that the Oracle RAC database processes can request to lock in memory.
In addition to the locked attribute of the capped-memory property, you can use the max-shm-memory property to directly configure the limit of the shared memory segment in a zone cluster. See also the Solaris man page zonecfg(1M).
Reboot the zone cluster.
#clzonecluster reboot zoneclustername |
You can perform the step to configure the capped-memory property attributes as part of the zone cluster creation. If you configure the capped-memory property attributes as part of the zone cluster creation, the memory-related properties immediately take effect after the first zone cluster boot. See How to Create a Zone Cluster in Sun Cluster Software Installation Guide for Solaris OS.
You should set the necessary privileges to enable Oracle RAC to run in a zone cluster configuration. You can use the clzonecluster command to include the necessary privileges in a zone cluster configuration by setting the limitpriv property. Perform the following steps to set the necessary privileges in a zone cluster to run Oracle RAC.
Become superuser on the global cluster node that hosts the zone cluster.
Configure the limitpriv property by using the clzonecluster command.
# clzonecluster configure zcname clzonecluster:zcname>set limitpriv ="default,proc_priocntl,proc_clock_highres" clzonecluster:zcname>commit |
Reboot the zone cluster.
# clzonecluster reboot zcname |
You can perform the step to configure the limitpriv property as part of the zone cluster creation. For information on creating a zone cluster, see How to Create a Zone Cluster in Sun Cluster Software Installation Guide for Solaris OS.
To support logical hostname resources for Oracle RAC 9i configuration and Oracle clusterware virtual IP resources in Oracle RAC 10g and 11g configurations in zone clusters, you should configure the failover-capable hostnames or IP addresses used by those resources in a given zone cluster using the clzonecluster command.
Perform the following steps to configure the virtual IP addresses in a zone cluster configuration for Oracle RAC 10g or 11g.
Become superuser on the global cluster node that hosts the zone cluster.
Configure the virtual IP addresses using the clzonecluster command.
# clzonecluster configure zcname clzonecluster:zcname>add net clzonecluster:zcname:net>set address=racnode1-vip clzonecluster:zcname:net>end clzonecluster:zcname>add net clzonecluster:zcname:net>set address=racnode2-vip clzonecluster:zcname:net>end clzonecluster:zcname>commit |
Reboot the zone cluster.
# clzonecluster reboot zcname |
If you did not install the Sun Cluster Support for Oracle RAC packages during your initial Sun Cluster installation, perform this procedure to install the packages. To install the packages, use the Sun JavaTM Enterprise System Installation Wizard.
You need to install the Sun Cluster Support for Oracle RAC packages in the global cluster and not in the zone cluster.
Perform this procedure on each cluster node where you are installing the Sun Cluster Support for Oracle RAC packages.
You can run the Sun Java Enterprise System Installation Wizard with a command-line interface (CLI) or with a graphical user interface (GUI). The content and sequence of instructions in the CLI and the GUI are similar.
Ensure that you have the Sun Java Availability Suite DVD-ROM.
If you intend to run the Sun Java Enterprise System Installation Wizard with a GUI, ensure that your DISPLAY environment variable is set.
On the cluster node where you are installing the data service packages, become superuser.
Load the Sun Java Availability Suite DVD-ROM into the DVD-ROM drive.
If the Volume Management daemon vold(1M) is running and configured to manage DVD-ROM devices, the daemon automatically mounts the DVD-ROM on the /cdrom directory.
Change to the Sun Java Enterprise System Installation Wizard directory of the DVD-ROM.
Start the Sun Java Enterprise System Installation Wizard.
# ./installer |
When you are prompted, accept the license agreement.
If any Sun Java Enterprise System components are installed, you are prompted to select whether to upgrade the components or install new software.
From the list of Sun Cluster agents under Availability Services, select the data service for Oracle RAC.
If you require support for languages other than English, select the option to install multilingual packages.
English language support is always installed.
When prompted whether to configure the data service now or later, choose Configure Later.
Choose Configure Later to perform the configuration after the installation.
Follow the instructions on the screen to install the data service packages on the node.
The Sun Java Enterprise System Installation Wizard displays the status of the installation. When the installation is complete, the wizard displays an installation summary and the installation logs.
(GUI only) If you do not want to register the product and receive product updates, deselect the Product Registration option.
The Product Registration option is not available with the CLI. If you are running the Sun Java Enterprise System Installation Wizard with the CLI, omit this step.
Exit the Sun Java Enterprise System Installation Wizard.
Unload the Sun Java Availability Suite DVD-ROM from the DVD-ROM drive.
The next step depends on the platform that you are using, as shown in the following table.
Platform |
Next Step |
---|---|
SPARC | |
x86 |
For detailed instructions for installing the Oracle UDLM, see the Oracle RAC documentation.
Before you install the Oracle UDLM, ensure that you have created the DBA group and DBA user accounts. For more information, see How to Create the DBA Group and the DBA User Accounts.
If your Oracle RAC release requires Oracle UDLM, you must install the Oracle UDLM software on the local disk of each node. To support Oracle RAC on a zone cluster node, install Oracle UDLM software on each zone cluster node.
Become superuser on a cluster node.
Install the Oracle UDLM software.
See the appropriate Oracle RAC installation documentation for instructions.
Ensure that you did not receive any error messages when you installed the Oracle UDLM packages. If an error occurred during package installation, correct the problem before you install the Oracle UDLM software.