4. Using the Plug-in

Searching Sun Cluster

Contents
Index

Using the Oracle 10g R2 RAC Plug-In

This page describes the following information:

Top

Oracle 10g R2 RAC Plug-In Process Overview

This section contains the following information:

Note

This release of the Oracle 10g R2 RAC plug-in only supports deployment of Oracle 10g R2 RAC release 10.2.0.1 components on Sun Cluster 3.1 or 3.2 clusters. Other clustering products or Oracle releases are not supported.

The plug-in does support operations on patched versions of Oracle, such as versions of 10.2.0, where the Oracle patchset upgrade has been performed manually.

Working with the Oracle database plug-in is a multi-step process.

  1. Procure all the software that will be needed by the installation. For information about the software that is required for the Oracle RAC plug-in, see Requirements for the Oracle 10g R2 RAC Plug-In.
  2. Install and configure the Oracle RAC plug-in. For more information about how to install the plug-in, see Installing and Configuring the Oracle 10g R2 RAC Plug-In.
  3. Obtain the root SSH cluster passphrase. For more information, see Customizing the Solution for Your Environment.
  4. Gather the information required to set the component and target host variables. For more information, see Worksheet for Component and Target Host Variable Settings.
  5. Install N1 SPS Remote Agent software on all Sun Cluster nodes on which you want to deploy Oracle RAC components. For more information about how to install N1 SPS Remote Agent software, see Chapter 4, Installing the Sun N1 Service Provisioning System 6.0 on Linux and UNIX Systems, in Sun N1 Service Provisioning System 6.0 Installation Guide.
  6. Create a physical host entry in N1 SPS for each Sun Cluster node that you plan to use. For more information, see Creating Sun Cluster Physical Hosts in N1 SPS.
  7. Create a virtual host entry in N1 SPS for each Sun Cluster node that you plan to use. For more information, see Creating Sun Cluster Virtual Hosts in N1 SPS.
  8. Create an Oracle CRS virtual host entry in N1 SPS for each Sun Cluster node that you plan to use. For more information, see Creating Oracle CRS Virtual Hosts in N1 SPS.
  9. Create the Oracle 10g R2 RAC component variable sets. For more information, see Creating Oracle 10g R2 RAC Component Variable Sets.
  10. 10. Deploy the Oracle RAC components to the nodes in your environment. For more information, see Deploying Oracle RAC Components.

Top

Worksheet for Component and Target Host Variable Settings

The amount of information that you need to collect will depend on the configuration that you plan to deploy. You will need to make the following decisions:

  • The version of Sun Cluster 3.1 or 3.2 software to use. If you choose Sun Cluster 3.2 software, decide whether to use the scalable device group, scalable mount point, and RAC proxy features
  • Whether to use a volume manager or none.
  • Whether to use shared QFS.
  • Where to install Oracle Clusterware and what storage it will use for its OCR and voting disks.
  • The locations for one or more installations of the Oracle RAC software.
  • Whether to use an Oracle ASM database.
  • How many Oracle databases to deploy and what storage they will use.
Information for Target Host Variable Settings
Description Value
The Oracle VIP hostname

Example: pgyruss1-vip		                                                                            
The Oracle VIP host IP address

Example: 129.159.54.123		  
The Oracle VIP host netmask

Example: 255.255.255.0		  
The Oracle VIP public NIC list

Example: ce0,ce1		  
The Oracle private NIC list

Example: clprivnet0		  

The following table gives an example of the information that you would have to gather if you were installing Oracle Clusterware and RAC on a four-node SPARC Sun Cluster 3.1 configuration. Here the Oracle Cluster OCR and voting disks are stored on the Solaris Volume Manager raw disk volumes d103 and d104 in metaset oraset. You must create this metaset manually from the command line.

Example Component Worksheet
Description Value
Oracle User Component (installName, softOwnerId, softGroup, softGroupId, installPath, shell, dbaGroup, dbaGroupId, operGroup, operGroupId) Example: oracle, 1000, oinstall, 1000, /export/home/oracle, /bin/ksh, dba, 1001, dba, 1001                                                                
Location of Sun Java Enterprise System (Java ES) installer on the Sun Cluster media (for the SUNWscucm package) Example: /net/mediasvr/export/software/sc31_dvd/Solaris_sparc/Product  
Location of Java ES installer on the Sun Cluster media (for the SUNWudlm and SUNWudlmr packages - SPARC only) Example: /net/mediasvr/export/software/sc31_dvd/Solaris_sparc/Product  
Location of the Oracle ORCLudlm package Example: /net/mediasvr/export/software/Oracle/UDLM  
Location of Java ES installer on the Sun Cluster media (for the SUNWscmd package) Example: /net/mediasvr/export/software/sc31_dvd/Solaris_sparc/Product  
RAC framework resource group (installName, nodeList) Example: rac-framework-rg pgyruss1,pgyruss2,pgyruss3,pgyruss4  
RAC framework resource (installName, rg_name)Example: rac-framework, rac-framework-rg  
RAC udlm resource (installName, rg_name) Example: rac-udlm, rac-framework-rg  
RAC svm resource (installName, rg_name) Example: rac-svm, rac-framework-rg  
Oracle CRS component (installPath, ORACLE_BASE, ORACLE_HOME_NAME, nodeList, COMPONENT_LANGUAGES, ORACLE_CLUSTER_NAME, ocrDevList, vdskDevList, mediaLocation) Example: /oracle/oracle/product/10.2.0/crs_1, /local/oracle, OraCrs10g_home1, pgyruss1,pgyruss2,pgyruss3,pgyruss4 en, gyruss, /dev/md/oraset/rdsk/d103, /dev/md/oraset/rdsk/d104, /net/mediasvr/export/software/Oracle/CRS  
Oracle RAC component (installPath, ORACLE_HOME_NAME, COMPONENT_LANGUAGES, install_type, nodeList, mediaLocation) Example: /oracle/oracle/product/10.2.0/db_1, OraDb10g_home1, en, EE pgyruss1,pgyruss2,pgyruss3,pgyruss4 /net/mediasvr/export/software/Oracle/DB  

Top

Creating Sun Cluster Physical Hosts in N1 SPS

Create one system#crhost host for each physical Sun Cluster node that you will use, either by using the N1 SPS browser GUI or by using the cr_cli command line. You must ensure that the host is prepared successfully. The example below shows a host being added that uses a raw TCP-IP connection as opposed to ssh.

% cr_cli -cmd hdb.h.add                     host add
    -name pgyruss1                          host name
    -tID "NM:system#crhost"                 host type
    -u spsadmin                             user name
    -p x1y2z3                               password
% cr_cli -cmd hdb.a.add                     host add
    -hID NM:pgyruss1                        host id
    -port 1131                              remote agent port
    -conn raw -type RA                      connection type
    -pID NM:masterserver:MS                 parent hostname
    -ip 192.168.1.23                        IP of target
    -u spsadmin                             user name
    -p x1y2z3                               password
% cr_cli -cmd pe.h.prep                     host prepare
    -tar NM:pgyruss1                        target name
    -u spsadmin                             user name
    -p x1y2z3                               password

Top

Creating Sun Cluster Virtual Hosts in N1 SPS

Create one virtual host of type com.sun.oracle10g_RAC#ClusterNodeHT for each physical Sun Cluster node that is used.

Note

The virtual host must be parented on the physical system#crhost host that you created in the previous step.

You can do this by using the N1 SPS browser or by using the cr_cli command line. The following example shows the creation of a virtual host, pgyruss1-sc, that is parented on the physical pgyruss1 host.

% cr_cli -cmd hdb.h.add                             host add
    -name pgyruss1-sc                               virtual host name
    -tID "NM:com.sun.oracle10g_RAC#ClusterNodeHT"   host type
    -pID "NM:pgyruss1"                              parent host
    -attr "cluster_name=gyruss"                     host attributes
    -u spsadmin                                     user name
    -p x1y2z3                                       password

Top

Creating Oracle CRS Virtual Hosts in N1 SPS

Create one virtual host of type com.sun.oracle10g_RAC#OracleCRS_HT for each physical Sun Cluster node that is used.

Note

The virtual host must be parented on the virtual com.sun.oracle10g_RAC#ClusterNodeHT host that you created in the previous step.

You can do this by using the N1 SPS browser or by using the cr_cli command line. The following example shows the creation of a virtual host, pgyruss1-crs, that is parented on the virtual pgyruss1-sc host.

% cr_cli -cmd hdb.h.add                            host add
    -name pgyruss1-crs                             virtual host name
    -tID "NM:com.sun.oracle10g_RAC#OracleCRS_HT"   host type
    -pID "NM:pgyruss1-sc"                          parent host
    -attr "vip_hostname=$pgyruss1-crs;             host attributes
           vip_host_ip=192.168.1.24;                  Attributes are shown on separate lines
           vip_host_netmask=255.255.255.0;            for clarity. The actual entry must
           vip_public_nic_list=ce0,ce1;               be a continuous line with no
           private_nic_list=clprivnet0"           spaces between attributes.
    -u spsadmin                                    user name
    -p x1y2z3                                      password

Top

Creating Oracle 10g R2 RAC Component Variable Sets

Create the Oracle 10g R2 RAC component variable sets for the components that are required for the deployment by using the data collected above. You can do this by using the browser or by using the cr_cli command line interface. The following example shows how to create a variable set for the CRS component.

% cr_cli -cmd cdb.vs.add                                        component variable set add
     -name crs-two-node                                         variable set name
     -comp /com/sun/oracle10g_RAC/CRS                           component name
     -vars "nodeList=pgyruss1,pgyruss2;                         variable settings
        installPath=/oracle/oracle/product/10.2.0/crs_1;          Variables are shown on separate 
        ORACLE_BASE=/local/oracle;                                lines for clarity. The actual entry
        ocrDevList=/oradata/OCR.dbf;                              must be in a continuous line with
        vdskDevList=/oradata/VDSK1.dbf;                           no spaces between variables.
        mediaLocation=/net/software/oracle_media/10.2.0.1/crs"
     -u spsadmin                                                user name
     -p x1y2z3                                                  password

Top

Deploying Oracle RAC Components

Deploy the components either from the N1 SPS browser GUI or from the command line interface. In general, the procedure will require you to deploy components starting at the top of the Oracle plug-in in the browser, such as the Oracle user component and work downwards. You can deploy the components from the N1 SPS browser or by using the cr_cli command line interface. The following example shows how to deploy the CRS component to the target nodes pgyruss1-crs and pgyruss2-crs.

% echo “mysshpwd” | cr_cli -cmd pe.p.run             plan execution
     -PID NM:/com/sun/oracle10g_RAC/CRS.install      plan name
     -tar “H:HM:pgyruss1-crs,H:HM:pgyruss2-crs;      targets for the 3 plan stages
        H:HM:pgyruss1-crs,H:HM:pgyruss2-crs;           Targets are shown on separate lines 
        H:HM:pgyruss1-crs,H:HM:pgyruss2-crs”          _ for clarity. The actual entry must be 
                                                       on a continuous line with no spaces 
                                                       between targets._
     -nto 120 -pto 120                               timeouts
     -comp ";;"                                     component versions
     -vs ";;crs-two-node"                            variable set name
     -u spsadmin                                     user name
     -p x1y2z3                                       password

Top

Virtual Host Structure That is Used by the Plug-in

The Oracle 10g R2 RAC plug-in uses three host types:

  • Physical system#crhost host types
  • Virtual com.sun.oracle10g_RAC#ClusterNodeHT Sun Cluster host types
  • Virtual com.sun.oracle10g_RAC#OracleCRS_HT Oracle CRS host types

These host types are described in the following sections:

Top

The crhost Type

You use the physical hosts of the system#crhost type as the target for deploying physical components, such as the Oracle users, additional Sun Cluster packages, and shared QFS file systems.

Top

The Sun Cluster Host Type

You use virtual hosts of the Sun Cluster (com.sun.oracle10g_RAC#ClusterNodeHT) host type as the targets for deploying any Sun Cluster components, such as resource groups and resources.

Note

You must parent these virtual hosts on the physical system#crhost that are used to specific the Solaris hosts that make up the Sun Cluster.

The Sun Cluster host type has one host variable:

Name Description Notes
cluster_name The Sun Cluster cluster name of which this host is a part Optional

The cluster_name host variable is provided simply to reminder you which Sun Cluster the node is part of. It is not actually used anywhere in the component execution plans.

Top

The CRS Node Host Type

You use the virtual CRS (com.sun.oracle10g_RAC#OracleCRS_HT) host type as the target for deploying any Oracle components, such as the Clusterware or RAC software, an ASM database or databases on one of the storage mechanisms (ASM, QFS, or raw disk).

Note

You must parent these virtual hosts on the Sun Cluster virtual hosts described in the previous section.

The OracleCRS_HT host type has the following host variables:

Name Description Notes
vip_hostname The Oracle CRS VIP host name Mandatory
vip_host_ip The Oracle CRS VIP host IP address Mandatory
vip_host_netmask The Oracle CRS VIP address netmask Mandatory
vip_public_nic_list The Oracle CRS public VIP NIC list Mandatory
private_nic_list The Oracle CRS private NIC list Mandatory - must be set to clprivnet0

You will need to define the values for these host variables before you can provision the Oracle Clusterware software. Oracle Clusterware relies on these values for its installation.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact