|Oracle9i Installation and Database Administration Guide
Release 2 (18.104.22.168.10) for Fujitsu Siemens Computers BS2000/OSD
Part Number B12034-01
This chapter describes what is BS2000 specific for RAC. Parts of this chapter are:
For more information see Oracle9i Real Application Clusters (a complex of books).
When you plan to create an RAC database or migrate your single instance database to an RAC database please contact your Oracle Customer Support Representative before starting the task.
In order to achieve the capabilities of RAC Oracle needs
The interprocess communication system enables Oracle to exchange messages and coordinate operations between the instances on the cluster, the node monitor is telling Oracle which node is part of the cluster and which is not (and prohibits 'dead nodes' to interfere with the 'healthy' ones), the shared file system is giving access of the common database files to the instances on the different nodes of the cluster.
This set of functions is delivered on BS2000 by HIPLEX MSCF. You must run HIPLEX MSCF as an XCS ('cross coupled system') network with an XCS shared pubset. RAC cannot operate without these prerequisites.
For more information on HIPLEX MSCF see BS2000/OSD HIPLEX MSCF, BS2000 Processor Networks.
Installation of the RAC software is not different from the single instance BS2000 installation. RAC is part of the Oracle9i Release 2 tape (see chapter Installing/Upgrading Oracle Server Software) and is implictely installed when you install Oracle9i.
It is important to install the Oracle software on an XCS shared pubset in order to have shared access from different XCS nodes (i.e. the default pubset of your installation userid should be an XCS pubset).
Oracle9i Real Applications Cluster Setup and Configuration makes a distinction of 4 steps for RAC installation:
With an MSCF XCS cluster and an XCS shared pubset you implicitely got clusterware and shared disks with a cluster file system (as refered to in Oracle9i Real Applications Cluster Setup and Configuration, ch. about Configuring the Shared Disks). This means: we are arrived at the end of step 2.
The usual single instance installation puts us at the end of step 3.
The fourth step is the subject of the next section.
There is no Database Configuration Assistant on BS2000. You must use the manual creation method (see chapter about "Manually Creating Real Application Cluster Databases" in Oracle9i Real Applications Cluster Setup and Configuration).
In order to avoid RAC process overhead for non-RAC instances on BS2000 an ORAENV parameter is telling Oracle if RAC should be switched on or off:
This parameter controls RAC operation on a BS2000 cluster. It does not replace INIT.ORA parameters like CLUSTER_DATABASE=TRUE etc. The meaning of all RAC related parameters is unchanged. ENABLE_RAC=TRUE in ORAENV must be set as a prerequisite to use RAC on BS2000.
One more ORAENV parameter is important:
RAC is relying on timer accuracy which must be much more precise than usually available on BS2000. Therefore a special method to improve timer accuracy has been implemented for RAC. This parameter says: all timer limits below the given value should be handled by this precise method, all limits above by the traditional method.
The type of the value is thousandth of seconds. E.g., ALARM_TIMER_LIMIT=10000 says: below 10 seconds use the precise method, above the traditional method.
ALARM_TIMER_LIMIT=10000 is the recommended setting for RAC on BS2000.
When a cluster node is using a ZAS-LAN interface one more parameter may be helpful. In this case contact your Oracle Customer Support Representative.
In general comments and hints given in the chapter "Manually Creating Real Application Cluster Databases" in Oracle9i Real Applications Cluster Setup and Configuration are valid for BS2000, e.g.
In this step following differences may be observed:
do not differ from the proceeding explained in the chapter "Manually Creating Real Application Cluster Databases" of Oracle9i Real Applications Cluster Setup and Configuration.
On BS2000 there is no