Release Notice:

PRIMECLUSTER

Oracle 10g installation on PRIMECLUSTER

 

PRIMEPOWER 100 200 250 400 450 600 650 850
800 900 1000 1500 2000 2500

 

 

SOLARIS 8 / SOLARIS 9 /SOLARIS 10

 

Date of the last modification:

March

2006

Release level:

March

2006

 


 Table of Contents

 

 

1

General

1.1

Ordering

1.2

Delivery

1.3

Documentation

 

 

2

Software extensions/new functions

 

 

3

Technical information

3.1

Resource requirements

3.2

Hardware requirements/support

3.3

Software requirements

3.4

Product installation/configuration

 

 

3.4.1

Installing Oracle 10g RAC on PRIMECLUSTER prior to version 10.1.0.4

3.4.2

Moving from an Oracle installation without SMAWrac to one with SMAWrac

3.4.3

Installing Oracle RAC 10g R2 (Release 10.2.0.x) with SMAWrac

 

 

3.6

Obsolete functions

3.7

Incompatibilities

 

 

3.8

Restrictions


1 General

This Release Notice contains a Readme that describes the necessary steps to install 10g RAC on PRIMECLUSTER.

The navigation in this document is done by hyperlinks. The links in the table of contents will guide you to the corresponding item. Click on the section header to return to the table of contents.

The use of names or product designations, etc. in this information does not constitute a general authorization to use such names or designations. In many cases they are legally or contractually protected names or designations even if they are not marked as such. 

1.1 Ordering

-/-.

Printed Manuals may be ordered separately.

1.2 Delivery

-/-

1.3 Documentation

An overview of the documentation on the PRIMECLUSTER 4.1 distribution CD contains the order numbers and also the possibility to view the manuals via the Acrobat Reader.

Check for an updated version of this document at:

http://uc.fujitsu.com/Oracle/downloads/SMAWrac10g.readme.html

 

2 Software extensions/new functions

-/-

3 Technical information

3.1 Resource requirements

-/-

3.2 Hardware requirements/support

Please see the PRIMECLUSTER Installation Guide for details on the supported models and general configuration information.
An ORACLE 10g RAC installation is supported on PRIMECLUSTER CF 4.1A20 or higher. See CF 4.1A20 release notes and CF 4.1A30 release notes for details on the supported models and configuration.

3.3 Software requirements

The following software products or software components are required for the use of SMAWrac_10g:

  • Cluster foundation 4.1A20 or higher must be installed.
    For any prerequisites about the operating system, please read carefully the Readme of the corresponding CF 4.1.
    Patch matrix:

 

Solaris 8

Solaris 9

PCL 4.1A20

SMAWpas: 901156-02 

SMAWpas: 901155-02 

SMAWcf:  901146-14 

SMAWcf:  901147-14 

PCL 4.1A30

SMAWpas: 901175-01 

SMAWpas: 901176-01 

SMAWcf:  901157-05 

SMAWcf:  901158-05 

          
             Note: The table documents the minimum patch levels for SMAWcf and SMAWpas.

             Note: To date there are  no minimum patch level requirement for Solaris 10

 

  • RMS 4.1A20 or higher and packages, which are needed by RMS
  • If you are using PRIMECLUSTER with SMAWrac_10g_64 Oracle RAC 10g 10.1.0.4 or higher is required. In addition the Oracle P4334900_10104_SOLARIS64 and p4450598_10104_SOLARIS64 must be applied.

 

3.4 Installation/configuration

This section is divided into two parts:

3.4.1 Describes the way Oracle 10g had to be installed prior to Oracle version 10.1.0.4 (without SMAWrac). It is also the first step for the recommended way to install Oracle 10g RAC on PRIMECLUSTER.

3.4.2 Lists the necessary steps to move from an Oracle 10g RAC installation as described in 3.4.1 to an installation with SMAWrac. If  you had a prior Oracle 10g/PRIMECLUSTER installation follow these steps to integrate Oracle RAC 10g with SMAWrac for 10g.

3.4.3 Gives a brief overview of necessary steps to install Oracle 10g R2 (Oracle Release 10.2.0.1 or higher) on PRIMECLUSTER.

3.4.1 Installing Oracle 10g RAC on PRIMECLUSTER prior to Oracle Version 10.1.0.4

This description assumes that you have PRIMECLUSTER already installed and configured on all the systems that should be part of the Oracle 10g DB cluster.

Before you install the CRS (Cluster Ready Services), please make sure that the library libskgxn2.so does not exist in the /opt/ORCLcluster/lib directories. This can be the case, if an older Oracle RAC version has been installed before. If it exists please simply move this library to libskgxn9.so.

After you started the Oracle Universal Installer as described in the Oracle Real Application Clusters Installation and Configuration Guide, you need to complete some generic information on the Cluster Configuration page. At this point of the CRS installation you will be asked to enter public and private node names of the systems that are part of this 10g RAC cluster. Use the host names that were assigned to CIP (FSC Cluster IP) as private host names.

For example if you configured a cluster with the nodes sys1 and sys2 you probably used sys1RMS and sys2RMS as private nodenames. The /etc/hosts then shows the following entries:

192.168.1.1     sys1RMS       sys1rms
192.168.1.2     sys2RMS       sys2rms

Also, use the cluster name you choose for PRIMECLUSTER as Oracle clustername.

On the Specify Network Interface Usage page the OUI asks to assign the public and private networks. In this step you choose the CIP (Cluster IP) network for your private network addresses.

In our example the OUI will list a network 192.168.1.0.  Choose this network as the private network.

Now follow the steps described in the Oracle RAC Installation and Configuration Guide to configure the Cluster Registry device and the Voting Disk. It is recommended to use mirrored devices for both whenever possible.

Also check the additional notes in the next chapter.

Note: An earlier version of this document described, how the CLSCFG_MISCNT parameter should be altered when installing Oracle 10g RAC on PRIMECLUSTER. These steps are now with availability of the SMAWrac for 10g obsolete.

3.4.2 Moving from an Oracle installation without SMAWrac to one with SMAWrac

Make sure 10.1.0.4 Oracle patchset with the Oracle patches (P4334900_10104_SOLARIS64 and p4450598_10104_SOLARIS64) or a higher Oracle version is installed. Install SMAWrac for 10g after you installed the required SMAWcf, SMAWpas patches (as listed in Chapter 3.3).

 

Shutdown Oracle

 
Shutdown CRS via /etc/init.d/init.crs stop

 
Remove libskgxn2.so in $ORA_CRS_HOME/lib.

 
Create a link libskgxn2.so to /opt/ORCLcluster/lib/libskgxn2.so in  $ORA_CRS_HOME/lib

 

Edit root.sh on each node. There is a variable VNDR_CLUSTER in here that needs to be set to "true". So set this to true. This step is necessary to use the Oracle scripts for adding  new nodes later.

 
Also (if necessary, because the CLSCFG_MISCNT has been manipulated before): remove the line CLSCFG_MISCNT="-misscount 180" and remove $CLSCFG_MISCNT at the end of line 572


Start up a single node. In 10.1.0.4 you should be able to use /etc/init.d/init.crs start


Invoke "crsctl unset css misscount", if you've overridden this to another value before (as described in Chapter 3.4.2).


Restart CRS on this node.

 
Start CRS on all the remaining nodes.


Additional notes:

 

Please check if the correct interconnect is registered in the Oracle Cluster Registry:


You can use “oifcfg getif” for this. For the cluster interconnect it should look like this (example):

 

cip0 192.168.1.0   global    cluster_interconnect.

 

To get all the interfaces listed:

 

oifcfg iflist

 

To add a cluster_interconnect interconnect (example):

oifcfg setif -global cip0/192.168.1.0:cluster_interconnect
 
To remove a cluster_interconnect use (example):


oifcfg delif -global cip0/192.168.8.0

3.4.3 Installing Oracle RAC 10g R2 (Release 10.2.0.x) with SMAWrac

This description assumes that you have PRIMECLUSTER including SMAWrac for 10g installed and configured on all the systems that should be part of the Oracle 10g DB cluster.

After you started the Oracle Universal Installer as described in the Oracle Real Application Clusters Installation and Configuration Guide 10g Release 2, you need to complete some generic information on the Cluster Configuration page. At this point of the CRS installation you will be asked to enter public and private node names of the systems that are part of this 10g RAC cluster. Use the host names that were assigned to CIP (FSC Cluster IP) as private host names.

For example if you configured a cluster with the nodes sys1 and sys2 you probably used sys1RMS and sys2RMS as private nodenames. The /etc/hosts then shows the following entries:

192.168.1.1     sys1RMS       sys1rms
192.168.1.2     sys2RMS       sys2rms

Also, use the cluster name you choose for PRIMECLUSTER as Oracle clustername.

On the Specify Network Interface Usage page the OUI asks to assign the public and private networks. In this step you choose the CIP (Cluster IP) network for your private network addresses.

In our example the OUI will list a network 192.168.1.0.  Choose this network as the private network.

Now follow the steps described in the Oracle RAC Installation and Configuration Guide to configure the Cluster Registry device and the Voting Disk. It is recommended to use mirrored devices for both whenever possible.

Note: In Oracle 10g R2 the OUI optionally allows the use of a cluster configuration file to support the installation. This file has the following format: First line contains the clustername following that there is a line reserved for each system in the cluster. Each line should contain the system name, the private nodename, and the virtual IP address as required by VIPCA. Each item on a line is separated by a space.

 

For example:

 

CLUSTERNAME

sys1 sys1RMS sys1-v

sys2 sys2RMS sys2-v

 

You will be asked for the location of the cluster configuration file on the “Specify Cluster Configuration” screen of OUI.

3.5 Product use

-/-

3.6 Obsolete functions

The following steps were recommended when a  SMAWrac for 10g  was not available. If you plan to install Oracle RAC 10g 10.1.0.4 or higher with SMAWrac for 10g, do not change the CLSCFG_MISCNT  parameter.

After the CRS software did get distributed to all node of the cluster the Oracle installer will ask you to run the root.sh script on all the nodes. Before you run this script you must to edit one line. The script can be found in the $ORA_CRS_HOME directory. Please change the line that says CLSCFG_MISCNT="" to CLSCFG_MISCNT="-misscount 180". Setting this parameter as described will eliminates a case where CSS (part of CRS) evict one set of nodes and PRIMECLUSTER evicts a disjoint set of nodes.

If you can’t find the CLSCFG_MISCNT=”” line in the root.sh script, you need to include it yourself.

After Line 185 under SunOs Section just after the line (SCRBASE=/var/opt/oracle/scls_scr)

Add:

CLSCFG_MISCNT="-misscount 180"

Then to the end of line 572 please add $CLSCFG_MISCNT

(For example it should look like)

$CH/bin/clscfg -install -nn  sys1,1,sys2,2 -pn sys1RMS,1,sys2RMS,2 \
      $HOSTNAMES_ARGS -o $CH -c crs -l "AMERICAN_AMERICA.WE8ISO8859P1" -q /dev/vdisk/css_vote $CLSCFG_MISCNT

Explanation: sys1, sys2 are the public names and sys1RMS, sys2RMS are private names that were assigned in an earlier steps. "/dev/vdisk/css_vote" is a placeholder for the CSS voting device.

After you have edited these scripts run them as requested.

There is an alternate way to change the CLSCFG_MISCNT parameter:

After the completion of the CRS installation shutdown all nodes but one.
Execute "crsctl set css misscount 180"
Reboot the final node
Start the other nodes.

This will allow you to tune the misscount parameter after the CRS installation.

You can verify that the misscount parameter is set correctly by issuing the following command:

crsctl get css misscount

after you ran the root.sh script (To issue this command CRS needs installed and on all nodes).

The crsctl command can be found in the $ORA_CRS_HOME/bin

 

3.7 Incompatibilities

-/-

3.8 Restrictions

-/-


 Copyright © Fujitsu Limited 2004

 

Copyright©2004 Fujitsu Siemens Computers GmbH