Skip Headers

Oracle® Fail Safe Installation Guide
Release 3.3.1 for Windows
Part No. A96685-01
Go To Table Of Contents
Contents
Go To Index
Index

Previous Next

1
Introduction and Preinstallation Checklist

This guide uses a step-by-step approach to assist you with the installation of Oracle Fail Safe. Oracle Fail Safe comprises multiple components: Oracle Fail Safe Manager, Oracle Services for MSCS, and server components specific to Oracle Fail Safe.

Oracle Fail Safe Manager is a graphical user interface through which you configure and manage Oracle single-instance databases, Oracle Reports, Oracle Forms and so on for high availability in an MSCS cluster. Oracle Services for MSCS is the main server component. Both the manager and the server are shared with Oracle Real Application Clusters Guard. For this reason, you are asked early in the installation process if you want to install Oracle Fail Safe or Oracle Real Application Clusters Guard.

Typically, you will perform your installation using the Oracle Universal Installer graphical user interface. If you need to perform the same installation on multiple systems, you may want to run Oracle Universal Installer in silent mode to automate the installation process in batch files or scripts. Silent installations are described in Appendix B.

The following topics are discussed in this chapter:

Topic Reference
Conventions   Section 1.1  
Cluster Setup Prerequisites   Section 1.2  
Recommended Order for Software Installation   Section 1.3  
Adding a Node to an Existing Cluster   Section 1.4  
Postinstallation Procedures   Section 1.5  

1.1 Conventions

Screen captures that were taken during an Oracle Fail Safe installation, configuration, and deployment effort form the basis for this guide. The screens and dialog boxes represent valid choices made during an actual installation of Oracle Fail Safe.

1.2 Cluster Setup Prerequisites

You should perform the following configuration tasks prior to the installation of Oracle Fail Safe:

1.3 Recommended Order for Software Installation

Although this guide describes the Oracle Fail Safe installation in detail, other products also must be installed to implement your Oracle Fail Safe environment. Figure 1-1 shows the recommended order for installing software on a two-node cluster (note that the numbers in the figure do not correspond to the numbered steps in the subsequent list because the list contains more detailed information than the figure).

Figure 1-1 Recommended Order for Installing Software on a Two-Node Cluster

Description of nu-fsinstall.gif follows
Description of the illustration nu-fsinstall.gif

The following list provides more detail about the installation order and other tasks to help you get started with Oracle Fail Safe:

  1. On each cluster node, install:

    1. Microsoft Windows on a private (system) disk.

    2. Microsoft Cluster Server (MSCS) on a private disk if you installed Microsoft Windows NT in step a. (MSCS is included in a Windows 2000 installation.)

    See the Oracle Fail Safe Release Notes for information about the versions of Microsoft Windows that can be used with Oracle Fail Safe and for a link to the Oracle Fail Safe Web site. The Oracle Fail Safe Web site contains more information about installing Microsoft Cluster Server.

  2. On each cluster node, test the TCP/IP connections using the Windows ping command.

    To validate that the IP addresses and host names resolve properly across the cluster, perform the following tests to ensure that pinging returns the same address on each node:

    1. Ping Node 1 on each node.

    2. Ping Node 2 on each node, then Node 3, and so on for each cluster node.

    3. Ping the cluster alias from each cluster node.

    See the Oracle Fail Safe Concepts and Administration Guide for more information about network configuration problems.

  3. On each cluster node, create an Oracle home on a private disk (for example, the system disk) on each node for each Oracle product that you intend to install. To minimize downtime during future upgrades, Oracle Corporation recommends that you use a separate Oracle home for each major component (for example, a separate Oracle home each for the database, application software, and Oracle Fail Safe). To allow applications to fail over, ensure that the Oracle homes on each cluster node are named in the same way (for example, name the Oracle Fail Safe home on each system ofs_home, and name the database home on each system dbs_home).

  4. Install optional Oracle software (database server, Forms and Reports Servers, Web servers, and other applications) that you plan to use with Oracle Fail Safe into the Oracle home (or homes) on each node. Place all application and database data, control, and log files on shared cluster disks so that they can fail over.

    If you are installing Oracle database server software, you can create the database before or after you install Oracle Fail Safe. Create the database as you would in a noncluster environment, including the database listener. However, the database must be created on a cluster disk or disks.

  5. On each cluster node, install the server component of Oracle Fail Safe, Oracle Services for MSCS. If desired, you can install the client component, Oracle Fail Safe Manager, at the same time.

    See Chapter 2 for complete information about installing Oracle Fail Safe.

  6. Optionally, install Oracle Fail Safe Manager on one or more client systems (for example, to set up additional management consoles).

Figure 1-2 indicates the software and files that should be installed on private disks and shared cluster disks.

Figure 1-2 Software Installed on Private, Shared-Nothing Cluster Disks

Description of nu-fsinstall2.gif follows
Description of the illustration nu-fsinstall2.gif

1.4 Adding a Node to an Existing Cluster

If you want to add a node to an existing cluster, perform the following operations:

  1. On the system that you want to add to the cluster, install:

    1. Microsoft Windows on a private (system) disk.

    2. Microsoft Cluster Server (MSCS) on a private disk if you installed Microsoft Windows NT in step a. (MSCS is included in a Windows 2000 installation.)

    See the Oracle Fail Safe Release Notes for information about the versions of Microsoft Windows that can be used with Oracle Fail Safe and for a link to the Oracle Fail Safe Web site. The Oracle Fail Safe Web site contains more information about installing Microsoft Cluster Server.

    The new node is now joined to the cluster.

  2. On each cluster node (including the new node), test the TCP/IP connections using the Windows ping command.

    To validate that the IP addresses and host names resolve properly across the cluster, perform the following tests to ensure that pinging returns the same address on each node:

    1. Ping Node 1 on each node.

    2. Ping Node 2 on each node, then Node 3, and so on for each cluster node.

    3. Ping the cluster alias from each cluster node.

    See the Oracle Fail Safe Concepts and Administration Guide for more information about network configuration.

  3. On the new node, install any desired optional Oracle software (database server, Forms and Reports Servers, Web servers, and other applications) that you plan to use with Oracle Fail Safe. Install executable application files in an Oracle home or homes located on private disks (for example, on the system disk for each node).

  4. On the new node, install Oracle Services for MSCS (which is the server component of Oracle Fail Safe). You can install Oracle Fail Safe Manager at the same time.

1.5 Postinstallation Procedures

After you have successfully installed Oracle Fail Safe, perform the following tasks:

  1. If you installed optional Oracle software, perform the following tasks:

    • Configure application data and log files on the shared cluster disks.

    • Configure alert and trace files on either the shared cluster disks or on the private disk.

      Configuring alert and trace files on private disks allows the administrator to determine on which node problems occur, but requires that you maintain multiple sets of files. Placing parameter files on private disks is recommended only when you want the parameters to be different on each cluster node. For example, this can be useful if you want a database to use fewer resources on its failover node than on its primary node (such as when you know another application or database server on the failover node needs resources).

      For information about re-creating Oracle databases on cluster disks, refer to the Import/Export documentation that is specific to your database.

  2. Start Oracle Fail Safe Manager, connect to the cluster alias with a domain account that has Administrator privileges on each cluster node, and run the Verify Cluster operation when prompted.

    See Chapter 3 for information to help you get started with Oracle Fail Safe.

  3. Refer to the Oracle Fail Safe tutorial for step-by-step information about creating a group and adding resources to it. (To invoke the tutorial from the Oracle Fail Safe Manager, choose Help -> Tutorial.)


Previous Next
Oracle Logo
Copyright © 1999, 2002 Oracle Corporation

All rights reserved
Go To Table Of Contents
Contents
Go To Index
Index