#ident "@(#)$RCSfile: SMAWrac_9207_64_3.0-01.readme.txt,v $ - $Revision: 1.1 $ - $Date: 2005/12/08 00:01:00 $" # # Copyright (c) 1990 Pyramid Technology # Copyright (c) 1996 Siemens Nixdorf / Siemens AG # Copyright (c) 2000, 2001, 2002, 2003, 2004 Fujitsu Siemens Computers # All Rights Reserved # # THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF # Fujitsu Siemens Computers. # The copyright notice above does not evidence any # actual or intended publication of such source code. # README file for customers This readme file explains the steps involved in installing/checking/removing the Fujitsu Siemens 9iRAC package for Oracle 9.2.0.7 64-bit. Fixes in this version: Added changes required by Oracle RAC 9.2.0.7 Software Dependencies: The Fujitsu Siemens RAC package for Oracle 9.2.0.7 64-bit requires the following packages to be installed: * OS Solaris 8 01/01 or higher * SMAWcf 1.2A10 or higher * SMAWpas 1.0A20 or higher * RMS 3.1E30 or higher Additional hints: - SMAWcf cluster framework is also required by SMAWpas, the PAS package does not declare a dependency to SMAWcf; this is covered by SMAWpas - SMAWpas parallel application services the RAC package declares a dependency to SMAWpas - RMS reliable monitoring system this package is only required for node elimination, there are no binary interfaces between the PAS package and RMS, therefore the RAC package does not declare a dependency to RMS Installation At this point you have already uncompressed and opened the tar file "SMAWrac_9207_64_3.0.tar.Z" In your current directory you have now the following files: * SMAWrac.ds (datastream containing the package SMAWrac) * readme (this document) The next steps are as follows: 1: Install SMAWrac package from the file SMAWrac.ds with 'pkgadd -d ./SMAWrac.ds SMAWrac' (you need to have superuser privileges for this) This step creates a directory "/opt/SMAW/SMAWrac/rac_9207_64_3.0" with several files. 2: Run the shell script "/opt/SMAW/SMAWrac/rac_9207_64_3.0/prepare_rac.sh" This step installs a library that will be used by runInstaller during Oracle installation. It reports the cluster configuration to runInstaller. 3: Install Oracle 9i Release 9.2.0.7 or higher runInstaller should detect the cluster and perform a cluster installation. 4: Run the shell script "/opt/SMAW/SMAWrac/rac_9207_64_3.0/enable_rac.sh" This step places the PRIMECLUSTER communication library into Oracle's lib-directory. The package can be removed in two steps: R1: run /opt/SMAW/SMAWrac/rac_9207_64_3.0/remove_rac.sh with superuser privileges; this step restores Oracle's default/dummy communication library. R2: remove the package with pkgrm SMAWrac To update from a Oracle 9.2.0.1 installation to Oracle 9.2.0.7: Simply remove the old package as decribed in the respective Readme. Afterwards install this package and run the "enable_rac" step only. Restrictions This package is not compatible with Oracle 9i versions prior 9.2.0.7. Installation Hints Oracle's runInstaller in the current release (9.2.0.1) is checking for the existence of the directory "/opt/SUNWcluster" before it is using files from the directory "/opt/ORCLcluster". This bug should be fixed with a later release. As a workaround the script "prepare_rac.sh" is creating the directory "/opt/SUNWcluster. This directory is not used for any other purpose and should be empty. All three scripts (prepare_rac.sh, enable_rac.sh and remove_rac.sh) try to accomplish the corresponding function on each node in the cluster. The scripts do this with two utilities (cfsh, cfcp) which were released with PRIMECLUSTER V4.0. Should these two utilities not exist, the scripts try to revert to rsh and rcp respectively. Please note that the remote node address in a cfsh/cfcp command refers to the node's cluster name, whereas the remote node address in a rsh/rcp command refers to the node's network name. Usually both name spaces are identical (it makes little or no sense to have two different naming schemes). However, should these two naming schemes be different, manual intervention is required. Installation of SMAWrac is only required on nodes that will be used by an instance of Oracle 9i RAC; nodes that will not be used for this do not require the installation of SMAWrac or its components. Manual intervention is required should a script not succeed on a remote node. The easiest manual workaround is to install SMAWrac on the other node directly and to run the script directly on the other node. Alternatively, the directory /opt/SMAW/SMAWrac/rac_9207_64_3.0 has to be copied to the rmote node (using the same name) and the scripts have to be called directly on the remote node.