11 Installing in High Availability Environments: OracleAS Cold Failover Cluster

11.1.1 Special Considerations for Symmetrical Nodes

If the nodes of your cluster are symmetrical, you can choose to perform faster procedures when configuring an OracleAS Cold Failover Cluster on a shared disk.

Review the following information to determine whether or not the two nodes of your cluster are symmetrical.

The two nodes of an OracleAS Cold Failover Cluster are symmetrical if they have an identical:

• Hardware configuration (for example, the same memory and CPU specifications)

• Software configuration (for example, the same operating system version and patch level)

• Oracle configuration (for example, the same Oracle products and Oracle homes are installed on both nodes)

11.2.1 Ensure that the Event Log Service Is Running

The "Event Log" service must be running on both nodes in the cluster. You can check it in the Services dialog. To access the Services dialog:

• Windows 2000: Select Start > Programs > Administrative Tools > Services.

• Windows 2003: Select Start > Administrative Tools > Services.

11.2.2 Get a Virtual Address for the Cluster

You need a virtual address to associate with the cluster. A virtual address consists of a virtual hostname and an IP address. Clients access the OracleAS Cold Failover Cluster using the virtual hostname. The virtual address is in addition to each node's own hostname and IP address. Figure 11-13 shows a virtual address for the two nodes in the cluster.

To get a virtual address, consult your network administrator. Virtual hostnames and IP addresses are any valid hostname and IP address in the context of the subnet containing the cluster.

11.2.3 Verify that Microsoft Cluster Server (MSCS) Is Installed on Both Nodes

To verify that MSCS is installed on a computer, check that you can launch the Cluster Administrator from the Start menu:

Windows 2000: Select Start > Programs > Administrative Tools > Cluster Administrator.

Windows 2003: Select Start > Administrative Tools > Cluster Administrator.

Note that the "Cluster IP Address" and "Cluster Name" used by MSCS are different from the virtual hostname and virtual IP created in the previous step.

11.2.4 Determine the Name of the Cluster

You can use the Cluster Administrator to find out the name of your cluster.

11.2.5 Determine a Domain User to Administer Oracle Fail Safe

You need a domain user to own the "OracleMSCSServices" service, which gets installed when you install Oracle Fail Safe.

Requirements for this user:

• This user must be defined at the domain level (as opposed to a user defined locally) because you need to specify the same user on both nodes during installation.

• Make sure that you do not have a local user with the same name on either node.

• This user must have Administrator privileges on both nodes in the cluster.

• This user must also belong to the DBA group.

During Oracle Fail Safe installation, you specify the domain and the user using the domainname\username format. If you are running on a Microsoft Windows 2000 domain, you can also use the username@dnsDomainName format.

11.2.6 Install Oracle Fail Safe on the Local Storage of Each Node

You need to install Oracle Fail Safe on the local storage of both nodes. For example, Figure 11-13 shows Oracle Fail Safe installed on C:\Oracle\OFS on both nodes.

Oracle Fail Safe is shipped with Oracle Application Server. It is available on the Oracle Fail Safe CD-ROM.

Overview of Steps to Install Oracle Fail Safe on Both Nodes

The sequence of steps for installing Oracle Fail Safe on each node is:

1. Before you start installing Oracle Fail Safe, you need to know the domain and user who will own the "OracleMSCSServices" service. This service gets installed when you install Oracle Fail Safe. See Section 11.2.5, "Determine a Domain User to Administer Oracle Fail Safe" for details on this user.

2. Install Oracle Fail Safe on node 1. See details in the next section, "Steps for Installing Oracle Fail Safe".

3. Restart node 1.

4. Install Oracle Fail Safe on node 2.

5. Restart node 2.

6. Verify the cluster using Oracle Fail Safe Manager.

Steps for Installing Oracle Fail Safe

This section describes the screens for installing Oracle Fail Safe. For a full description of the screens, refer to the Oracle Fail Safe Installation Guide.

1. Insert the Oracle Fail Safe CD-ROM and double-click setup.exe to start up the installer.

2. Welcome screen: click Next.

3. Specify File Locations screen:

   Name: Enter the name for this Oracle home. Example: ofs.

   Path (in the Destination section): Enter the full path where you want to install Oracle Fail Safe. You must install Oracle Fail Safe on the local storage. Example: C:\oracle\OFS.

   Click Next.

4. Select Installation Type screen: Select Typical, and click Next.

   This installs the following components:

   • Oracle Fail Safe Manager

   • Oracle Services for MSCS

5. Reboot Needed After Installation screen: This screen reminds you that you need to restart your computer after installation. Click Next.

6. Summary screen: Click Install.

7. Oracle Services for MSCS Account/Password screen:

   Domain\Username: Enter the domain name and the username under which you want to run the OracleMSCSServices service.

   Password and Confirm Password: Specify and confirm the password for the user.

   Click OK.

8. Configuration Assistants screen: This screen shows the progress as the configuration assistants run.

9. End of Installation: Click Exit.

Verify the Cluster

After installing Oracle Fail Safe, verify the cluster using Oracle Fail Safe Manager.

1. Start Oracle Fail Safe Manager from the Start menu:

   Start > Programs > Oracle - OracleHomeName > Oracle Fail Safe Manager

   OracleHomeName refers to the name that you gave to the Oracle home where you installed Oracle Fail Safe.

2. Enter the cluster name in Cluster Alias in the Add Cluster to Tree dialog (Figure 11-1). You defined the cluster name using Cluster Administrator. Click OK.

   Figure 11-1 Oracle Fail Safe Manager: Add Cluster to Tree dialog

   
   Description of "Figure 11-1 Oracle Fail Safe Manager: Add Cluster to Tree dialog"
   
   

3. In the left frame, select the cluster. This causes Oracle Fail Safe Manager to display the Welcome dialog (Figure 11-2). In the figure, "FSWIN-CLU1" is the cluster name.

   Click Verify Cluster.

   You might see some warnings related to Oracle software. These warnings are expected because you have not installed any products in the cluster yet. However, if you see any system warnings, you should investigate them.

   Figure 11-2 Oracle Fail Safe Manager: Welcome / Verify Cluster dialog

   
   Description of "Figure 11-2 Oracle Fail Safe Manager: Welcome / Verify Cluster dialog"
   
   

11.2.7 Create a Group in Oracle Fail Safe

A group in Oracle Fail Safe is a logical collection of resources that will fail over to the standby node as a unit. Before you install OracleAS Infrastructure in an OracleAS Cold Failover Cluster, you need to create a group using Oracle Fail Safe Manager, and add these resources to the group:

Follow these steps to create and set up a group. This procedure creates a group with default attributes (for things such as failover and failback policies). You can change these attributes later if necessary. For details, see the Oracle Application Server High Availability Guide and the Oracle Fail Safe documentation.

1. Start up Oracle Fail Safe Manager from the Start menu:

   Start > Programs > Oracle - OracleHomeName > Oracle Fail Safe Manager

   OracleHomeName refers to the name that you gave to the Oracle home directory where you installed Oracle Fail Safe.

2. Expand the cluster on the left side.

3. Right-click Groups, and select Create from the pop-up menu. This starts up the Create Group wizard.

4. Follow the screens in the Create Group wizard to create a group called "OracleAS".

   1. General, Step 1, screen: Enter the group name for the infrastructure resources and click Next. This guide calls the group "OracleAS".

      Figure 11-3 Oracle Fail Safe Manager: Create Group Wizard, General Screen

      
      Description of "Figure 11-3 Oracle Fail Safe Manager: Create Group Wizard, General Screen"
      
      

   2. Failback Policies, Step 2, screen: Select Prevent Failback and click Next.

      Figure 11-4 Oracle Fail Safe Manager: Create Group Wizard, Failback Policies Screen

      
      Description of "Figure 11-4 Oracle Fail Safe Manager: Create Group Wizard, Failback Policies Screen"
      
      

   3. Finish Creating the Group screen: Review the information and click OK.

      Figure 11-5 Oracle Fail Safe Manager: Create Group Wizard, Finish Creating the Group Screen

      
      Description of "Figure 11-5 Oracle Fail Safe Manager: Create Group Wizard, Finish Creating the Group Screen"
      
      

   4. Add Virtual Address screen: Click Yes.

      Figure 11-6 Oracle Fail Safe Manager: Create Group Wizard, Add Virtual Address Screen

      
      Description of "Figure 11-6 Oracle Fail Safe Manager: Create Group Wizard, Add Virtual Address Screen"
      
      

   5. Add Resource to Group - Virtual Address screen:

      Select Show networks accessible by clients.

      Network: Select the name associated with the primary network interface card on the node. By default, it is "Local Area Connection".

      Host Name: Enter the virtual hostname. Example: vhost.

      IP Address: Enter the IP of the virtual hostname. Example: 138.2.229.77.

      Click Next.

      Figure 11-7 Oracle Fail Safe Manager: Create Group Wizard, Add Resource to Group - Virtual Address Screen

      
      Description of "Figure 11-7 Oracle Fail Safe Manager: Create Group Wizard, Add Resource to Group - Virtual Address Screen"
      
      

   6. Finish Adding the Virtual Address to the Group screen: Review the information and click OK.

      Figure 11-8 Oracle Fail Safe Manager: Create Group Wizard, Finish Adding the Virtual Address to the Group Screen

      
      Description of "Figure 11-8 Oracle Fail Safe Manager: Create Group Wizard, Finish Adding the Virtual Address to the Group Screen"
      
      

5. Verify that you can see the group that you just created in Oracle Fail Safe Manager (Figure 11-9) and that the group has these two resources in it:

   • IP address of the virtual host

   • Virtual hostname (shown as Network Name)

   Figure 11-9 Oracle Fail Safe Manager Showing the Resources in the New Group

   
   Description of "Figure 11-9 Oracle Fail Safe Manager Showing the Resources in the New Group"
   
   

6. Using Cluster Administrator, move the shared disk where you will be installing OracleAS Infrastructure into the group that you just created in Oracle Fail Safe Manager.

   1. Start up Cluster Administrator from the Start menu:

      Windows 2000: Start > Programs > Administrative Tools > Cluster Administrator

      Windows 2003: Start > Administrative Tools > Cluster Administrator

   2. On the left side, select the disk group that contains the shared disk. In Figure 11-10, Disk I is the shared disk.

      Note the "OracleAS" group on the left side. This is the group that you created in Oracle Fail Safe Manager.

      Figure 11-10 Cluster Administrator Showing the Shared Disk

      
      Description of "Figure 11-10 Cluster Administrator Showing the Shared Disk"
      
      

   3. Drag and drop the shared disk (Disk I in the example) from the right side to the "OracleAS" group on the left side. If the Cluster Administrator prompts you to confirm (Figure 11-11), click Yes.

      Figure 11-11 Cluster Administrator: Move Resources Confirmation Dialog

      
      Description of "Figure 11-11 Cluster Administrator: Move Resources Confirmation Dialog"
      
      

7. In Oracle Fail Safe Manager, check that the group now includes the shared disk.

   Figure 11-12 Oracle Fail Safe Manager After Adding the Shared Disk to the Group

   
   Description of "Figure 11-12 Oracle Fail Safe Manager After Adding the Shared Disk to the Group"
   
   

11.3.1 OracleAS Cold Failover Cluster (Infrastructure): Overview of Installation Steps

To set up an OracleAS Cold Failover Cluster (Infrastructure) configuration, perform these steps:

11.3.2 OracleAS Cold Failover Cluster (Infrastructure): Details of Installation Steps

This section lists the steps for installing OracleAS Infrastructure in an OracleAS Cold Failover Cluster (Infrastructure) configuration.

Step 1 Perform Pre-Installation Steps

Perform the pre-installation steps listed in Section 11.2, "Pre-Installation Steps for OracleAS Cold Failover Cluster".

Step 2 Install OracleAS Infrastructure on the Shared Drive from Node 1

For OracleAS Cold Failover Cluster (Infrastructure), you install both OracleAS Metadata Repository and Oracle Identity Management in the same Oracle home by selecting Identity Management and OracleAS Metadata Repository in the Select Installation Type screen. This option creates a new database for the OracleAS Metadata Repository and a new Oracle Internet Directory.

Key Points

• The destination directory must be on the shared disk.

• Remember to select High Availability and Replication in the Select Configuration Options screen. By default, this option is not selected.

• You enter the virtual hostname in the Specify Virtual Hostname screen.

Installer Screens

Run the installer and follow the screen sequence shown in Table 11-4:

Step 3 Stop the OracleAS Infrastructure Services on Node 1, and Set Their Startup Type to Manual

1. Display the Services window.

   Windows 2000: Select Start > Programs > Administrative Tools > Services.

   Windows 2003: Select Start > Administrative Tools > Services.

2. Stop these services:

   • Oracle<OracleHomeName>ASControl

   • Oracle<OracleHomeName>ProcessManager

   • Oracle<OracleHomeName>TNSListener

   • OracleService<SID>

   To stop a service, right-click the service and select Stop from the pop-up menu.

3. Set the start type of the services listed above to manual.

   1. Right-click the service, and select Properties.

   2. Select Manual from the "Startup Type" section, and click OK.

Step 4 Configure Node 2

If the nodes on which you are installing OracleAS Cold Failover Cluster (Infrastructure) are symmetrical, you may perform the steps in Part A - Nodes are Symmetrical to configure node 2. If the nodes are not symmetrical, you must perform the steps in Part B - Nodes are Asymmetrical. To find out if the nodes are symmetrical, see Section 11.1.1, "Special Considerations for Symmetrical Nodes".

Part A - Nodes are Symmetrical

1. Export the Oracle Registry Settings From Node 1

   1. From Node 1, select Run from the Windows Start menu, and enter regedit in the resulting text field.

   2. Locate and select the HKEY_LOCAL_MACHINE\SOFTWARE\Oracle entry in the Windows registry.

   3. Select Export Registry File from the Registry menu.

   4. In the resulting dialog box, make sure that the Selected Branch radio button is selected and that the HKEY_LOCAL_MACHINE\SOFTWARE\Oracle branch is selected.

   5. Enter a name for the exported registry file and click Save.

      For example, enter oracle_registry_entries.

      Note that you can save the registry file to either the local disk or the shared disk. If you save to the local disk, you will have to copy the file to Node 2.

2. Copy the Oracle Inventory from Node 1 to Node 2

   The Oracle Universal Installer inventory stores information about all Oracle software products installed in all Oracle homes on a host, provided the product was installed using Oracle Universal Installer.

   The Oracle inventory information is stored in Extensible Markup Language (XML) format in a single directory structure on the host. The inventory is usually located in the following directory on Windows systems:

   C:\Program Files\Oracle\Inventory
   
   

   You can always find the location of the inventory by selecting the following registry key in the Windows registry and viewing the value of the inst_loc string:

   \\HKEY_LOCAL_MACHINE\\Software\Oracle\
   
   

   To copy the Oracle Inventory to Node 2, select the entire directory (for example, C:\Program Files\Oracle\Inventory) and copy it to the same location on Node 2.

3. Import the Registry Settings into the Windows Registry on Node 2

   1. Log in to Node 2.

   2. Double-click the oracle_registry_entries.reg file you created when you exported the registry entries from Node 1.

   3. When prompted to add the registry entries, click Yes.

4. Create and Start the Required Windows Services for 10g Release 2 (10.1.2).

   To create the Windows services on Node 2, you can use the SC tool (sc.exe), which is a services control management tool provided by Microsoft.

   
   

   Note: Before you use this procedure, make sure that the version of the sc.exe program you are using is version 5.0.2134.1 or later. For more information, refer to the Microsoft Web site.

   
   

   Use the SC tool to create the required services on Node 2. Note that the SC tool requires a space after each option.

   1. Oracle Process Manager and Notification Server (OPMN):

      sc create Oracle<home name>ProcessManager 
            binPath= "ORACLE_HOME\opmn\bin\opmn.exe -S"
      
      

      For example:

      sc create OracleINFRAProcessManager
            binPath= "C:\oracle\OraInfra\opmn\bin\opmn.exe -S"
      
      

   2. Oracle Enterprise Manager 10g Application Server Control:

      sc create Oracle<home name>ASControl 
            binPath= "ORACLE_HOME\bin\nmesrvc.exe"
      
      

      For example:

      sc create OracleINFRAASControl
            binPath= "C:\oracle\OraInfra\bin\nmesrvc.exe"
      
      

   3. The OracleAS Metadata Repository database listener:

      sc create Oracle<home name>TNSListener
            binPath= "ORACLE_HOME\bin\TNSLSNR"
      
      

      For example:

      sc create OracleINFRATNSListener
            binPath= "C:\oracle\OraInfra\bin\TNSLSNR"
      
      

   4. The OracleAS Metadata Repository database:

      sc create OracleService<oracle_sid>
            binPath= "ORACLE_HOME\bin\oracle.exe oracle_sid"
      
      

      Note that oracle_sid should be in upper case. For example:

      sc create OracleServiceORCL
            binPath= "C:\oracle\OraInfra\bin\ORACLE.EXE ORCL"
      
      

   5. The Database Console:

      sc create OracleDBConsole<oracle_sid>
            binPath= "ORACLE_HOME\bin\nmesrvc"
      
      

      Note that oracle_sid should be in upper case. For example:

      sc create OracleDBConsoleORCL
            binPath= "C:\oracle\OraInfra\bin\nmesrvc"
      
      

   6. The Oracle Job Scheduler:

      sc create OracleJobScheduler<oracle_sid>
            binPath= "ORACLE_HOME\bin\extjob.exe oracle_sid"
      
      

      Note that oracle_sid should be in upper case. For example:

      sc create OracleJobSchedulerORCL
            binPath= "C:\oracle\OraInfra\bin\extjob.exe ORCL"
      
      

5. Add Required Paths to the PATH Environment Variable

   Use the System control panel to add the following to the beginning of the Windows PATH variable:

   %ORACLE_HOME%\bin;%ORACLE_HOME%\jlib;
   
   

   
   

   See Also: The Windows online help for instructions on how to set the PATH variable for your specific Windows platform.

   
   

6. Create a Global Environment Variable.

   Use the System control panel to create the ORACLE_HOSTNAME environment variable and set the value to the virtual hostname.

   For details on how to set environment variables, see Section 4.6.1, "How to Set Environment Variables".

7. Remove the Database Instance.

   On node 1, run the following command to remove the OracleAS Metadata Repository database instance.

   F:\oracle\bin> oradim -delete -sid sid
   
   

8. Restart Node 1.

   Restart node 1. During the restart, the resources defined under the "OracleAS" group fail over to node 2. The resources include the virtual hostname, the IP of the virtual host, and the shared disk. Node 2 now owns these resources.

Part B - Nodes are Asymmetrical

If the two nodes are not symmetrical, perform the following steps to configure node 2:

1. Remove the Database Instance.

   On node 1, run the following command to remove the OracleAS Metadata Repository database instance.

   F:\oracle\bin> oradim -delete -sid sid
   
   

2. Restart Node 1.

   Restart node 1. During the restart, the resources defined under the "OracleAS" group fail over to node 2. The resources include the virtual hostname, the IP of the virtual host, and the shared disk. Node 2 now owns these resources.

3. Delete the Oracle Home.

   From node 2, delete these directories on the shared disk:

   • Oracle home directory where you installed OracleAS Infrastructure

   • the directory where you installed the database files

   You need to delete these directories because you will be installing the files in the same directories when you perform the installation from node 2. See the next step.

4. Install OracleAS Infrastructure on the Shared Disk from Node 2.

   Install OracleAS Infrastructure on the shared drive again, but this time install it from node 2. Make sure you use the same values (same Oracle home name and destination directory, same instance name and password, and so on) that you used when you installed it from node 1.

   You need to install OracleAS Infrastructure from node 2 so that the installer can update the Windows registry and inventory information on node 2's local storage.

   See Step 2, "Install OracleAS Infrastructure on the Shared Drive from Node 1" for specific steps.

Step 5 Restart Node 2

Restart node 2.

Note that the OracleAS Infrastructure services will fail to start up because the shared drive failed over to node 1 during the node 2 restart. Node 2 is unable to access the shared drive to start up the infrastructure services.

Click OK.

Figure 11-14 Error Message When Node 2 Boots Up

Description of "Figure 11-14 Error Message When Node 2 Boots Up"

Step 6 Move the Group to Node 2

Once node 2 is up, move the group to node 2. In Cluster Administrator, right-click the group and select Move Group (Figure 11-15).

Figure 11-15 Cluster Administrator: Move the Group to Node 2

Description of "Figure 11-15 Cluster Administrator: Move the Group to Node 2"

Step 7 Start up OracleAS Infrastructure Services on Node 2

After moving the group to node 2, start up OracleAS Infrastructure services on node 2.

1. Start up the database services:

   • OracleService<SID>

   • Oracle<OracleHomeName>TNSListener

2. Start up the database, if it is not started. To check if the database is started, you can log in to the database using SQL*Plus:

   C:\> sqlplus "sys/password as sysdba"
   
   

   If SQL*Plus reports that you are connected to an idle instance, then the database is not started. Start up the database by running the following command in SQL*Plus:

   SQL> startup
   
   

3. Start up the remaining services.

   • Oracle<OracleHomeName>ProcessManager

   • Oracle<OracleHomeName>ASControl

Step 8 Verify Installation

To verify that OracleAS Infrastructure was installed correctly, access the Application Server Control page for the OracleAS Infrastructure using the virtual hostname in the URL (for example: http://vhost.mydomain.com:1156).

The virtual hostname is the value you entered in the Specify Virtual Hostname screen (step 6.).

The default port number is 1156. You can verify the port number by looking in the ORACLE_HOME\install\portlist.ini file.

Step 9 Create a pfile for the Database

Oracle Fail Safe requires that the database has a pfile, which is a text file that contains the parameters for the database. See Section 11.12.1, "Create a pfile for the Database" for specific steps.

Step 10 Make OracleAS Metadata Repository Highly Available

Add OracleAS Metadata Repository as a resource to the group that you created in Oracle Fail Safe. This enables Oracle Fail Safe to fail over OracleAS Metadata Repository to the secondary node if the primary node fails.

See Section 11.12.2, "Make OracleAS Metadata Repository Highly Available" for details.

Step 11 Add the Shared Disk as a Dependency for the Listener

This enables the listener to fail over successfully. You do this using Oracle Fail Safe. See Section 11.12.3, "Add the Shared Disk as a Dependency for the Listener".

Step 12 Make OPMN Highly Available

Add OPMN as a resource to the group that you created in Oracle Fail Safe. See Section 11.12.4, "Make OPMN Highly Available" for details.

Step 13 Make Application Server Control Highly Available

Add Application Server Control as a resource to the group that you created in Oracle Fail Safe. See Section 11.12.6, "Make Application Server Control Highly Available" for details.

Step 14 Check that the Correct Listener Is Active

Oracle Fail Safe creates another listener, and this is the listener that needs to be running. See Section 11.12.7, "Check that the Correct Listener Is Active" for details.

11.4.1 Distributed OracleAS Cold Failover Cluster (Infrastructure): Overview of Installation Steps

To set up a distributed OracleAS Cold Failover Cluster (Infrastructure) configuration, perform these steps:

11.4.2 Distributed OracleAS Cold Failover Cluster (Infrastructure): Details of Installation Steps

Step 1 Perform Pre-Installation Steps

Perform the pre-installation steps listed in Section 11.2, "Pre-Installation Steps for OracleAS Cold Failover Cluster".

Step 2 Install OracleAS Infrastructure on the Shared Drive from Node 1

In a distributed OracleAS Cold Failover Cluster (Infrastructure) configuration, you install both OracleAS Metadata Repository and Oracle Identity Management components (except for OracleAS Single Sign-On, Oracle Delegated Administration Services, and OCA) in the same Oracle home by selecting Identity Management and OracleAS Metadata Repository in the Select Installation Type screen. This option creates a new database for the OracleAS Metadata Repository and a new Oracle Internet Directory.

The steps are the same as those listed in step 2, "Install OracleAS Infrastructure on the Shared Drive from Node 1", except that in the Select Configuration Options screen, do not select OracleAS Single Sign-On, Oracle Application Server Delegated Administration Services, and OracleAS Certificate Authority (OCA).

Step 3 Stop the OracleAS Infrastructure Services on Node 1, and Set Their Startup Type to Manual

1. Display the Services window.

   Windows 2000: Select Start > Programs > Administrative Tools > Services.

   Windows 2003: Select Start > Administrative Tools > Services.

2. Stop these services:

   • Oracle<OracleHomeName>ASControl

   • Oracle<OracleHomeName>ProcessManager

   • Oracle<OracleHomeName>TNSListener

   • OracleService<SID>

   To stop a service, right-click the service and select Stop from the pop-up menu.

3. Set the start type of the services listed above to manual.

   1. Right-click the service, and select Properties.

   2. Select Manual from the "Startup Type" section, and click OK.

Step 4 Configure Node 2

If the nodes on which you are installing OracleAS Cold Failover Cluster (Infrastructure) are symmetrical, you may perform the steps in Part A - Nodes are Symmetrical to configure node 2. If the nodes are not symmetrical, you must perform the steps in Part B - Nodes are Asymmetrical. To find out if the nodes are symmetrical, see Section 11.1.1, "Special Considerations for Symmetrical Nodes".

Part A - Nodes are Symmetrical

1. Export the Oracle Registry Settings From Node 1

   1. From Node 1, select Run from the Windows Start menu, and enter regedit in the resulting text field.

   2. Locate and select the HKEY_LOCAL_MACHINE\SOFTWARE\Oracle entry in the Windows registry.

   3. Select Export Registry File from the Registry menu.

   4. In the resulting dialog box, make sure that the Selected Branch radio button is selected and that the HKEY_LOCAL_MACHINE\SOFTWARE\Oracle branch is selected.

   5. Enter a name for the exported registry file and click Save.

      For example, enter oracle_registry_entries.

      Note that you can save the registry file to either the local disk or the shared disk. If you save to the local disk, you will have to copy the file to Node 2.

2. Copy the Oracle Inventory from Node 1 to Node 2

   The Oracle Universal Installer inventory stores information about all Oracle software products installed in all Oracle homes on a host, provided the product was installed using Oracle Universal Installer.

   The Oracle inventory information is stored in Extensible Markup Language (XML) format in a single directory structure on the host. The inventory is usually located in the following directory on Windows systems:

   C:\Program Files\Oracle\Inventory
   
   

   You can always find the location of the inventory by selecting the following registry key in the Windows registry and viewing the value of the inst_loc string:

   \\HKEY_LOCAL_MACHINE\\Software\Oracle\
   
   

   To copy the Oracle Inventory to Node 2, select the entire directory (for example, C:\Program Files\Oracle\Inventory) and copy it to the same location on Node 2.

3. Import the Registry Settings into the Windows Registry on Node 2

   1. Log in to Node 2.

   2. Double-click the oracle_registry_entries.reg file you created when you exported the registry entries from Node 1.

   3. When prompted to add the registry entries, click Yes.

4. Create and Start the Required Windows Services for 10g Release 2 (10.1.2).

   To create the Windows services on Node 2, you can use the SC tool (sc.exe), which is a services control management tool provided by Microsoft.

   
   

   Note: Before you use this procedure, make sure that the version of the sc.exe program you are using is version 5.0.2134.1 or later. For more information, refer to the Microsoft Web site.

   
   

   Use the SC tool to create the required services on Node 2. Note that the SC tool requires a space after each option.

   1. Oracle Process Manager and Notification Server (OPMN):

      sc create Oracle<home name>ProcessManager 
            binPath= "ORACLE_HOME\opmn\bin\opmn.exe -S"
      
      

      For example:

      sc create OracleINFRAProcessManager
            binPath= "C:\oracle\OraInfra\opmn\bin\opmn.exe -S"
      
      

   2. Oracle Enterprise Manager 10g Application Server Control:

      sc create Oracle<home name>ASControl 
            binPath= "ORACLE_HOME\bin\nmesrvc.exe"
      
      

      For example:

      sc create OracleINFRAASControl
            binPath= "C:\oracle\OraInfra\bin\nmesrvc.exe"
      
      

   3. The OracleAS Metadata Repository database listener:

      sc create Oracle<home name>TNSListener
            binPath= "ORACLE_HOME\bin\TNSLSNR"
      
      

      For example:

      sc create OracleINFRATNSListener
            binPath= "C:\oracle\OraInfra\bin\TNSLSNR"
      
      

   4. The OracleAS Metadata Repository database:

      sc create OracleService<oracle_sid>
            binPath= "ORACLE_HOME\bin\oracle.exe oracle_sid"
      
      

      Note that oracle_sid should be in upper case. For example:

      sc create OracleServiceORCL
            binPath= "C:\oracle\OraInfra\bin\ORACLE.EXE ORCL"
      
      

   5. The Database Console:

      sc create OracleDBConsole<oracle_sid>
            binPath= "ORACLE_HOME\bin\nmesrvc"
      
      

      Note that oracle_sid should be in upper case. For example:

      sc create OracleDBConsoleORCL
            binPath= "C:\oracle\OraInfra\bin\nmesrvc"
      
      

   6. The Oracle Job Scheduler:

      sc create OracleJobScheduler<oracle_sid>
            binPath= "ORACLE_HOME\bin\extjob.exe oracle_sid"
      
      

      Note that oracle_sid should be in upper case. For example:

      sc create OracleJobSchedulerORCL
            binPath= "C:\oracle\OraInfra\bin\extjob.exe ORCL"
      
      

5. Add Required Paths to the PATH Environment Variable

   Use the System control panel to add the following to the beginning of the Windows PATH variable:

   %ORACLE_HOME%\bin;%ORACLE_HOME%\jlib;
   
   

   
   

   See Also: The Windows online help for instructions on how to set the PATH variable for your specific Windows platform.

   
   

6. Create a Global Environment Variable.

   Use the System control panel to create the ORACLE_HOSTNAME environment variable and set the value to the virtual hostname.

   For details on how to set environment variables, see Section 4.6.1, "How to Set Environment Variables".

7. Remove the Database Instance.

   On node 1, run the following command to remove the OracleAS Metadata Repository database instance.

   F:\oracle\bin> oradim -delete -sid sid
   
   

8. Restart Node 1.

   Restart node 1. During the restart, the resources defined under the "OracleAS" group fail over to node 2. The resources include the virtual hostname, the IP of the virtual host, and the shared disk. Node 2 now owns these resources.

Part B - Nodes are Asymmetrical

If the two nodes are not symmetrical, perform the following steps to configure node 2:

1. Remove the Database Instance.

   On node 1, run the following command to remove the OracleAS Metadata Repository database instance.

   F:\oracle\bin> oradim -delete -sid sid
   
   

2. Restart Node 1.

   Restart node 1. During the restart, the resources defined under the "OracleAS" group fail over to node 2. The resources include the virtual hostname, the IP of the virtual host, and the shared disk. Node 2 now owns these resources.

3. Delete the Oracle Home.

   From node 2, delete these directories on the shared disk:

   • Oracle home directory where you installed OracleAS Infrastructure

   • the directory where you installed the database files

   You need to delete these directories because you will be installing the files in the same directories when you perform the installation from node 2. See the next step.

4. Install OracleAS Infrastructure on the Shared Disk from Node 2.

   Install OracleAS Infrastructure on the shared drive again, but this time install it from node 2. Make sure you use the same values (same Oracle home name and destination directory, same instance name and password, and so on) that you used when you installed it from node 1.

   You need to install OracleAS Infrastructure from node 2 so that the installer can update the Windows registry and inventory information on node 2's local storage.

   See Step 2, "Install OracleAS Infrastructure on the Shared Drive from Node 1" for specific steps.

Step 5 Restart Node 2

Restart node 2.

Note that the OracleAS Infrastructure services will fail to start up because the shared drive failed over to node 1 during the node 2 restart. Node 2 is unable to access the shared drive to start up the infrastructure services.

Click OK.

Figure 11-17 Error Message When Node 2 Boots Up

Description of "Figure 11-17 Error Message When Node 2 Boots Up"

Step 6 Move the Group to Node 2

Once node 2 is up, move the group to node 2. In Cluster Administrator, right-click the group and select Move Group (Figure 11-18).

Figure 11-18 Cluster Administrator: Move the Group to Node 2

Description of "Figure 11-18 Cluster Administrator: Move the Group to Node 2"

Step 7 Start up OracleAS Infrastructure Services on Node 2

After moving the group to node 2, start up OracleAS Infrastructure services on node 2.

1. Start up the database services:

   • OracleService<SID>

   • Oracle<OracleHomeName>TNSListener

2. Start up the database, if it is not started. To check if the database is started, you can log in to the database using SQL*Plus:

   C:\> sqlplus "sys/password as sysdba"
   
   

   If SQL*Plus reports that you are connected to an idle instance, then the database is not started. Start up the database by running the following command in SQL*Plus:

   SQL> startup
   
   

3. Start up the remaining services.

   • Oracle<OracleHomeName>ProcessManager

   • Oracle<OracleHomeName>ASControl

Step 8 Verify Installation

To verify that OracleAS Infrastructure was installed correctly, access the Application Server Control page for the OracleAS Infrastructure using the virtual hostname in the URL (for example: http://vhost.mydomain.com:1156).

The virtual hostname is the value you entered in the Specify Virtual Hostname screen (step 6.).

The default port number is 1156. You can verify the port number by looking in the ORACLE_HOME\install\portlist.ini file.

Step 9 Create a pfile for the Database

Oracle Fail Safe requires that the database has a pfile, which is a text file that contains the parameters for the database. See Section 11.12.1, "Create a pfile for the Database" for specific steps.

Step 10 Make OracleAS Metadata Repository Highly Available

Add OracleAS Metadata Repository as a resource to the group that you created in Oracle Fail Safe. This enables Oracle Fail Safe to fail over OracleAS Metadata Repository to the secondary node if the primary node fails.

See Section 11.12.2, "Make OracleAS Metadata Repository Highly Available" for details.

Step 11 Add the Shared Disk as a Dependency for the Listener

This enables the listener to fail over successfully. You do this using Oracle Fail Safe. See Section 11.12.3, "Add the Shared Disk as a Dependency for the Listener".

Step 12 Make OPMN Highly Available

Add OPMN as a resource to the group that you created in Oracle Fail Safe. See Section 11.12.4, "Make OPMN Highly Available" for details.

Step 13 Make Application Server Control Highly Available

Add Application Server Control as a resource to the group that you created in Oracle Fail Safe. See Section 11.12.6, "Make Application Server Control Highly Available" for details.

Step 14 Check that the Correct Listener Is Active

Oracle Fail Safe creates another listener, and this is the listener that needs to be running. See Section 11.12.7, "Check that the Correct Listener Is Active" for details.

Step 15 Install OracleAS Single Sign-On and Oracle Delegated Administration Services

You install OracleAS Single Sign-On and Oracle Delegated Administration Services on the local disks of each node. You perform these installations separately.

Pre-Installation Steps

This installation is actually an OracleAS Cluster (Identity Management) installation. As such, you perform the OracleAS Cluster (Identity Management) setup steps in Chapter 12, "Installing in High Availability Environments: OracleAS Cluster (Identity Management)":

• Section 12.2.1, "Use the Same Path for the Oracle Home Directory (recommended)"

• Section 12.2.2, "Synchronize Clocks on All Nodes"

• Section 12.2.3, "Configure Virtual Server Names and Ports for the Load Balancer"

• Section 12.2.5, "Set up Cookie Persistence on the Load Balancer"

Installation Steps

The steps are the same as those listed in Section 12.6.5, "Installing OracleAS Single Sign-On and Oracle Delegated Administration Services on Each Node".

11.5.1 OracleAS Cold Failover Cluster (Identity Management): Overview of Installation Steps

To create an OracleAS Cold Failover Cluster (Identity Management) configuration against an existing cold failover cluster database, perform these steps:

11.5.2 OracleAS Cold Failover Cluster (Identity Management): Details of Installation Steps

Perform the following steps to install Oracle Application Server in an OracleAS Cold Failover Cluster (Identity Management) configuration.

Step 1 Perform Pre-Installation Steps

Perform the pre-installation steps listed in Section 11.2, "Pre-Installation Steps for OracleAS Cold Failover Cluster".

Step 2 Install OracleAS Metadata Repository

Use the OracleAS Metadata Repository Creation Assistant to install the OracleAS Metadata Repository in an existing database. See the Oracle Application Server Metadata Repository Creation Assistant User's Guide for details.

If you do not have an existing database, you can use the installer to create one. Note that you have to create the database with a virtual hostname. The database should run in an active-passive configuration, typically on a hardware cluster. See Section 11.8, "Installing Only the OracleAS Metadata Repository in an OracleAS Cold Failover Cluster Environment" for details.

Step 3 Install the Oracle Identity Management Components

You install the Oracle Identity Management on the other shared disk. Follow the installation steps described in Table 11-7.

Key Points

• When the installer prompts you for the Oracle home path, enter a path on the shared disk. Make sure that both nodes can access this path.

• In the Select High Availability or Replication Option screen, select Virtual Host.

• In the Specify Virtual Hostname screen, enter the virtual hostname.

Installer Screens

Step 4 Stop the Oracle Application Server Services on Node 1, and Set Their Startup Type to Manual

1. Display the Services window.

   Windows 2000: Select Start > Programs > Administrative Tools > Services.

   Windows 2003: Select Start > Administrative Tools > Services.

2. Stop these services.

   • Oracle<OracleHomeName>ASControl

   • Oracle<OracleHomeName>ProcessManager

   To stop a service, right-click the service and select Stop from the pop-up menu.

3. Set the start type of the services listed above to manual.

   1. Right-click the service, and select Properties.

   2. Select Manual from the "Startup Type" section, and click OK.

Step 5 Configure Node 2

If the nodes on which you are installing OracleAS Cold Failover Cluster (Infrastructure) are symmetrical, you may perform the steps in Part A - Nodes are Symmetrical to configure node 2. If the nodes are not symmetrical, you must perform the steps in Part B - Nodes are Asymmetrical. To find out if the nodes are symmetrical, see Section 11.1.1, "Special Considerations for Symmetrical Nodes".

Part A - Nodes are Symmetrical

1. Export the Oracle Registry Settings From Node 1

   1. From Node 1, select Run from the Windows Start menu, and enter regedit in the resulting text field.

   2. Locate and select the HKEY_LOCAL_MACHINE\SOFTWARE\Oracle entry in the Windows registry.

   3. Select Export Registry File from the Registry menu.

   4. In the resulting dialog box, make sure that the Selected Branch radio button is selected and that the HKEY_LOCAL_MACHINE\SOFTWARE\Oracle branch is selected.

   5. Enter a name for the exported registry file and click Save.

      For example, enter oracle_registry_entries.

      Note that you can save the registry file to either the local disk or the shared disk. If you save to the local disk, you will have to copy the file to Node 2.

2. Copy the Oracle Inventory from Node 1 to Node 2

   The Oracle Universal Installer inventory stores information about all Oracle software products installed in all Oracle homes on a host, provided the product was installed using Oracle Universal Installer.

   The Oracle inventory information is stored in Extensible Markup Language (XML) format in a single directory structure on the host. The inventory is usually located in the following directory on Windows systems:

   C:\Program Files\Oracle\Inventory
   
   

   You can always find the location of the inventory by selecting the following registry key in the Windows registry and viewing the value of the inst_loc string:

   \\HKEY_LOCAL_MACHINE\\Software\Oracle\
   
   

   To copy the Oracle Inventory to Node 2, select the entire directory (for example, C:\Program Files\Oracle\Inventory) and copy it to the same location on Node 2.

3. Import the Registry Settings into the Windows Registry on Node 2

   1. Log in to Node 2.

   2. Double-click the oracle_registry_entries.reg file you created when you exported the registry entries from Node 1.

   3. When prompted to add the registry entries, click Yes.

4. Create and Start the Required Windows Services for 10g Release 2 (10.1.2).

   To create the Windows services on Node 2, you can use the SC tool (sc.exe), which is a services control management tool provided by Microsoft.

   
   

   Note: Before you use this procedure, make sure that the version of the sc.exe program you are using is version 5.0.2134.1 or later. For more information, refer to the Microsoft Web site.

   
   

   Use the SC tool to create the required services on Node 2. Note that the SC tool requires a space after each option.

   1. Oracle Process Manager and Notification Server (OPMN):

      sc create Oracle<home name>ProcessManager 
            binPath= "ORACLE_HOME\opmn\bin\opmn.exe -S"
      
      

      For example:

      sc create OracleINFRAProcessManager
            binPath= "C:\oracle\OraInfra\opmn\bin\opmn.exe -S"
      
      

   2. Oracle Enterprise Manager 10g Application Server Control:

      sc create Oracle<home name>ASControl 
            binPath= "ORACLE_HOME\bin\nmesrvc.exe"
      
      

      For example:

      sc create OracleINFRAASControl
            binPath= "C:\oracle\OraInfra\bin\nmesrvc.exe"
      
      

5. Add Required Paths to the PATH Environment Variable

   Use the System control panel to add the following to the beginning of the Windows PATH variable:

   %ORACLE_HOME%\bin;%ORACLE_HOME%\jlib;
   
   

   
   

   See Also: The Windows online help for instructions on how to set the PATH variable for your specific Windows platform.

   
   

6. Restart Node 1.

   Restart node 1. During the restart, the resources defined under the "OracleAS" group fail over to node 2. The resources include the virtual hostname, the IP of the virtual host, and the shared disk. Node 2 now owns these resources.

Part B - Nodes are Asymmetrical

If the two nodes are not symmetrical, perform the following steps to configure node 2:

1. Restart Node 1.

   Restart node 1. During the restart, the resources defined under the "OracleAS" group fail over to node 2. The resources include the virtual hostname, the IP of the virtual host, and the shared disk. Node 2 now owns these resources.

2. Delete the Oracle Home.

   From node 2, delete these directories on the shared disk:

   • Oracle home directory where you installed OracleAS Infrastructure

   • the directory where you installed the database files

   You need to delete these directories because you will be installing the files in the same directories when you perform the installation from node 2. See the next step.

3. Install Oracle Identity Management Components on the Shared Disk from Node 2

   Install the Oracle Identity Management components on the shared drive again, but this time install it from node 2. Make sure you use the same values (same Oracle home name and destination directory, same instance name and password, and so on) that you used when you installed it from node 1.

   You need to install the Oracle Identity Management components from node 2 so that the installer can update the Windows registry and inventory information on node 2's local storage.

   See Step 3, "Install the Oracle Identity Management Components" for specific steps.

Step 6 Restart Node 2

Restart node 2.

Note that the OracleAS Infrastructure services will fail to start up because the shared drive failed over to node 1 during the node 2 restart. Node 2 is unable to access the shared drive to start up the infrastructure services.

Click OK.

Figure 11-20 Error Message When Node 2 Boots Up

Description of "Figure 11-20 Error Message When Node 2 Boots Up"

Step 7 Move the Group to Node 2

Once node 2 is up, move the group to node 2. In Cluster Administrator, right-click the group and select Move Group (Figure 11-21).

Figure 11-21 Cluster Administrator: Move the Group to Node 2

Description of "Figure 11-21 Cluster Administrator: Move the Group to Node 2"

Step 8 Start up OracleAS Infrastructure Services on Node 2

After moving the group to node 2, start up OracleAS Infrastructure services on node 2.

1. Start up the database, if it is not started. To check if the database is started, you can log in to the database using SQL*Plus:

   C:\> sqlplus "sys/password as sysdba"
   
   

   If SQL*Plus reports that you are connected to an idle instance, then the database is not started. Start up the database by running the following command in SQL*Plus:

   SQL> startup
   
   

2. Start up the services.

   • Oracle<OracleHomeName>ProcessManager

   • Oracle<OracleHomeName>ASControl

Step 9 Verify Installation

To verify that the Oracle Identity Management components were installed correctly, access the Application Server Control page using the virtual hostname in the URL (for example: http://vhost.mydomain.com:1156).

The virtual hostname is the value you entered in the Specify Virtual Hostname screen (step 7.).

The default port number is 1156. You can verify the port number by looking in the ORACLE_HOME\install\portlist.ini file.

Step 10 Make OPMN Highly Available

Add OPMN as a resource to the group that you created in Oracle Fail Safe. See Section 11.12.4, "Make OPMN Highly Available" for details.

Step 11 Make Application Server Control Highly Available

Add Application Server Control as a resource to the group that you created in Oracle Fail Safe. See Section 11.12.6, "Make Application Server Control Highly Available" for details.

11.6.1 Distributed OracleAS Cold Failover Cluster (Identity Management): Overview of Installation Steps

To create a distributed OracleAS Cold Failover Cluster (Identity Management) configuration against an existing cold failover cluster database, perform these steps:

11.6.2 Distributed OracleAS Cold Failover Cluster (Identity Management): Details of Installation Steps

Step 1 Perform Pre-Installation Steps

Perform the pre-installation steps listed in Section 11.2, "Pre-Installation Steps for OracleAS Cold Failover Cluster".

Step 2 Install OracleAS Metadata Repository

Use the OracleAS Metadata Repository Creation Assistant to install the OracleAS Metadata Repository in an existing database. See the Oracle Application Server Metadata Repository Creation Assistant User's Guide for details.

If you do not have an existing database, you can use the installer to create one. Note that you have to create the database with a virtual hostname. See Section 11.8, "Installing Only the OracleAS Metadata Repository in an OracleAS Cold Failover Cluster Environment" for details.

Step 3 Install Oracle Internet Directory and Oracle Directory Integration and Provisioning

Install the Oracle Internet Directory and Oracle Directory Integration and Provisioning components on the other shared disk. Follow the installation steps described in Table 11-9.

Key Points

• In the Select Installation Type screen, select Identity Management.

• In the Select Configuration Options screen, select Oracle Internet Directory, Oracle Application Server Directory Integration and Provisioning, and High Availability and Replication.

• In the Select High Availability or Replication Option screen, select Virtual Host.

• In the Specify Virtual Hostname screen, enter the virtual hostname.

Installer Screens

Step 4 Stop the Oracle Application Server Services on Node 1, and Set Their Startup Type to Manual

1. Display the Services window.

   Windows 2000: Select Start > Programs > Administrative Tools > Services.

   Windows 2003: Select Start > Administrative Tools > Services.

2. Stop these services.

   • Oracle<OracleHomeName>ASControl

   • Oracle<OracleHomeName>ProcessManager

   To stop a service, right-click the service and select Stop from the pop-up menu.

3. Set the start type of the services listed above to manual.

   1. Right-click the service, and select Properties.

   2. Select Manual from the "Startup Type" section, and click OK.

Step 5 Configure Node 2

If the nodes on which you are installing OracleAS Cold Failover Cluster (Infrastructure) are symmetrical, you may perform the steps in Part A - Nodes are Symmetrical to configure node 2. If the nodes are not symmetrical, you must perform the steps in Part B - Nodes are Asymmetrical. To find out if the nodes are symmetrical, see Section 11.1.1, "Special Considerations for Symmetrical Nodes".

Part A - Nodes are Symmetrical

1. Export the Oracle Registry Settings From Node 1

   1. From Node 1, select Run from the Windows Start menu, and enter regedit in the resulting text field.

   2. Locate and select the HKEY_LOCAL_MACHINE\SOFTWARE\Oracle entry in the Windows registry.

   3. Select Export Registry File from the Registry menu.

   4. In the resulting dialog box, make sure that the Selected Branch radio button is selected and that the HKEY_LOCAL_MACHINE\SOFTWARE\Oracle branch is selected.

   5. Enter a name for the exported registry file and click Save.

      For example, enter oracle_registry_entries.

      Note that you can save the registry file to either the local disk or the shared disk. If you save to the local disk, you will have to copy the file to Node 2.

2. Copy the Oracle Inventory from Node 1 to Node 2

   The Oracle Universal Installer inventory stores information about all Oracle software products installed in all Oracle homes on a host, provided the product was installed using Oracle Universal Installer.

   The Oracle inventory information is stored in Extensible Markup Language (XML) format in a single directory structure on the host. The inventory is usually located in the following directory on Windows systems:

   C:\Program Files\Oracle\Inventory
   
   

   You can always find the location of the inventory by selecting the following registry key in the Windows registry and viewing the value of the inst_loc string:

   \\HKEY_LOCAL_MACHINE\\Software\Oracle\
   
   

   To copy the Oracle Inventory to Node 2, select the entire directory (for example, C:\Program Files\Oracle\Inventory) and copy it to the same location on Node 2.

3. Import the Registry Settings into the Windows Registry on Node 2

   1. Log in to Node 2.

   2. Double-click the oracle_registry_entries.reg file you created when you exported the registry entries from Node 1.

   3. When prompted to add the registry entries, click Yes.

4. Create and Start the Required Windows Services for 10g Release 2 (10.1.2).

   To create the Windows services on Node 2, you can use the SC tool (sc.exe), which is a services control management tool provided by Microsoft.

   
   

   Note: Before you use this procedure, make sure that the version of the sc.exe program you are using is version 5.0.2134.1 or later. For more information, refer to the Microsoft Web site.

   
   

   Use the SC tool to create the required services on Node 2. Note that the SC tool requires a space after each option.

   1. Oracle Process Manager and Notification Server (OPMN):

      sc create Oracle<home name>ProcessManager 
            binPath= "ORACLE_HOME\opmn\bin\opmn.exe -S"
      
      

      For example:

      sc create OracleINFRAProcessManager
            binPath= "C:\oracle\OraInfra\opmn\bin\opmn.exe -S"
      
      

   2. Oracle Enterprise Manager 10g Application Server Control:

      sc create Oracle<home name>ASControl 
            binPath= "ORACLE_HOME\bin\nmesrvc.exe"
      
      

      For example:

      sc create OracleINFRAASControl
            binPath= "C:\oracle\OraInfra\bin\nmesrvc.exe"
      
      

5. Add Required Paths to the PATH Environment Variable

   Use the System control panel to add the following to the beginning of the Windows PATH variable:

   %ORACLE_HOME%\bin;%ORACLE_HOME%\jlib;
   
   

   
   

   See Also: The Windows online help for instructions on how to set the PATH variable for your specific Windows platform.

   
   

6. Restart Node 1.

   Restart node 1. During the restart, the resources defined under the "OracleAS" group fail over to node 2. The resources include the virtual hostname, the IP of the virtual host, and the shared disk. Node 2 now owns these resources.

Part B - Nodes are Asymmetrical

If the two nodes are not symmetrical, perform the following steps to configure node 2:

1. Restart Node 1.

   Restart node 1. During the restart, the resources defined under the "OracleAS" group fail over to node 2. The resources include the virtual hostname, the IP of the virtual host, and the shared disk. Node 2 now owns these resources.

2. Delete the Oracle Home.

   From node 2, delete these directories on the shared disk:

   • Oracle home directory where you installed OracleAS Infrastructure

   • the directory where you installed the database files

   You need to delete these directories because you will be installing the files in the same directories when you perform the installation from node 2. See the next step.

3. Install Oracle Identity Management Components on the Shared Disk from Node 2

   Install the Oracle Identity Management components on the shared drive again, but this time install it from node 2. Make sure you use the same values (same Oracle home name and destination directory, same instance name and password, and so on) that you used when you installed it from node 1.

   You need to install the Oracle Identity Management components from node 2 so that the installer can update the Windows registry and inventory information on node 2's local storage.

   See Step 3, "Install the Oracle Identity Management Components" for specific steps.

Step 6 Restart Node 2

Restart node 2.

Note that the OracleAS Infrastructure services will fail to start up because the shared drive failed over to node 1 during the node 2 restart. Node 2 is unable to access the shared drive to start up the infrastructure services.

Click OK.

Figure 11-23 Error Message When Node 2 Boots Up

Description of "Figure 11-23 Error Message When Node 2 Boots Up"

Step 7 Move the Group to Node 2

Once node 2 is up, move the group to node 2. In Cluster Administrator, right-click the group and select Move Group (Figure 11-24).

Figure 11-24 Cluster Administrator: Move the Group to Node 2

Description of "Figure 11-24 Cluster Administrator: Move the Group to Node 2"

Step 8 Start up OracleAS Infrastructure Services on Node 2

After moving the group to node 2, start up OracleAS Infrastructure services on node 2.

1. Start up the database, if it is not started. To check if the database is started, you can log in to the database using SQL*Plus:

   C:\> sqlplus "sys/password as sysdba"
   
   

   If SQL*Plus reports that you are connected to an idle instance, then the database is not started. Start up the database by running the following command in SQL*Plus:

   SQL> startup
   
   

2. Start up the services.

   • Oracle<OracleHomeName>ProcessManager

   • Oracle<OracleHomeName>ASControl

Step 9 Verify Installation

To verify that the Oracle Identity Management components were installed correctly, access the Application Server Control page using the virtual hostname in the URL (for example: http://vhost.mydomain.com:1156).

The virtual hostname is the value you entered in the Specify Virtual Hostname screen (step 7.).

The default port number is 1156. You can verify the port number by looking in the ORACLE_HOME\install\portlist.ini file.

Step 10 Make OPMN Highly Available

Add OPMN as a resource to the group that you created in Oracle Fail Safe. See Section 11.12.4, "Make OPMN Highly Available" for details.

Step 11 Make Application Server Control Highly Available

Add Application Server Control as a resource to the group that you created in Oracle Fail Safe. See Section 11.12.6, "Make Application Server Control Highly Available" for details.

Step 12 Install OracleAS Single Sign-On and Oracle Delegated Administration Services

Install these components in an OracleAS Cluster (Identity Management) configuration. In this configuration, you install them on the local disks of each node. You perform these installations separately.

Pre-Installation steps: Because this installation is actually an OracleAS Cluster (Identity Management) installation, you can follow the OracleAS Cluster (Identity Management) setup steps in Chapter 12, "Installing in High Availability Environments: OracleAS Cluster (Identity Management)":

• Section 12.2.1, "Use the Same Path for the Oracle Home Directory (recommended)"

• Section 12.2.2, "Synchronize Clocks on All Nodes"

• Section 12.2.3, "Configure Virtual Server Names and Ports for the Load Balancer"

• Section 12.2.5, "Set up Cookie Persistence on the Load Balancer"

Installation steps: The installation steps are described in Section 12.6.5, "Installing OracleAS Single Sign-On and Oracle Delegated Administration Services on Each Node".

11.7.1 Oracle Delegated Administration Services and OracleAS Single Sign-On in OracleAS Cold Failover Cluster: Overview of Installation Steps

11.7.2 Oracle Delegated Administration Services and OracleAS Single Sign-On in OracleAS Cold Failover Cluster: Details of Installation Steps

Step 1 Perform Pre-Installation Steps

Perform the pre-installation steps listed in Section 11.2, "Pre-Installation Steps for OracleAS Cold Failover Cluster". Pre-installation tasks include:

• Section 11.2.1, "Ensure that the Event Log Service Is Running"

• Section 11.2.2, "Get a Virtual Address for the Cluster"

  You need to get two virtual addresses, one for each set of nodes.

• Section 11.2.3, "Verify that Microsoft Cluster Server (MSCS) Is Installed on Both Nodes"

  You need to install MSCS on all nodes.

• Section 11.2.4, "Determine the Name of the Cluster"

  You need two clusters, one for each set of nodes.

• Section 11.2.5, "Determine a Domain User to Administer Oracle Fail Safe"

• Section 11.2.6, "Install Oracle Fail Safe on the Local Storage of Each Node"

• Section 11.2.7, "Create a Group in Oracle Fail Safe"

  You need to create two groups, one for each set of nodes. The steps below use the following sample names for the Oracle Fail Safe groups:

  For the OracleAS Metadata Repository and Oracle Internet Directory installation, the group is called "MROID".

  For the Oracle Delegated Administration Services and OracleAS Single Sign-On installation, the group is called "SSODAS".

Step 2 Create staticports.ini Files

Create two staticports.ini files, one for each set of nodes. You need to have a staticports.ini file because you need to ensure that you get the same ports when you install from either node. For information on staticports.ini, see Section 4.4.4, "Using Custom Port Numbers (the "Static Ports" Feature)".

Step 3 Install OracleAS Metadata Repository and Oracle Internet Directory on the Shared Drive from Node 1

Install OracleAS Metadata Repository and Oracle Internet Directory in the same Oracle home by selecting Identity Management and OracleAS Metadata Repository in the Select Installation Type screen. This option creates a new database for the OracleAS Metadata Repository and a new Oracle Internet Directory.

The steps are the same as those listed in step 2, "Install OracleAS Infrastructure on the Shared Drive from Node 1", with these differences:

• In the Select Configuration Options screen, select these components/options:

  • Oracle Internet Directory

  • Oracle Application Server Directory Integration and Provisioning

  • High Availability and Replication

  Do not select these components:

  • Oracle Application Server Single Sign-On

  • Oracle Application Server Delegated Administration Services

  • Oracle Application Server Certificate Authority (OCA)

• In the Specify Port Configuration Options screen, select Manual and enter the fullpath to the staticports.ini file that you created in the previous step.

Step 4 Install Oracle Delegated Administration Services and OracleAS Single Sign-On from Node 3

From node 3, install Oracle Delegated Administration Services and OracleAS Single Sign-On on the shared disk by following the steps in Table 11-11.

Key Points

• When the installer prompts you for the Oracle home path, enter a path on the shared disk. Make sure that both nodes can access this path.

• In the Select High Availability or Replication Option screen, select Virtual Host.

• In the Specify Virtual Hostname screen, enter the virtual hostname.

Step 5 Stop the OracleAS Infrastructure Services on Node 1, and Set Their Startup Type to Manual

1. Display the Services window.

   Windows 2000: Select Start > Programs > Administrative Tools > Services.

   Windows 2003: Select Start > Administrative Tools > Services.

2. Stop these services:

   • Oracle<OracleHomeName>ASControl

   • Oracle<OracleHomeName>ProcessManager

   • Oracle<OracleHomeName>TNSListener

   • OracleService<SID>

   To stop a service, right-click the service and select Stop from the pop-up menu.

3. Set the start type of the services listed above to manual.

   1. Right-click the service, and select Properties.

   2. Select Manual from the "Startup Type" section, and click OK.

Step 6 Stop the OracleAS Infrastructure Services on Node 3, and Set Their Startup Type to Manual

1. Display the Services window.

   Windows 2000: Select Start > Programs > Administrative Tools > Services.

   Windows 2003: Select Start > Administrative Tools > Services.

2. Stop these services:

   • Oracle<OracleHomeName>ASControl

   • Oracle<OracleHomeName>ProcessManager

   To stop a service, right-click the service and select Stop from the pop-up menu.

3. Set the start type of the services listed above to manual.

   1. Right-click the service, and select Properties.

   2. Select Manual from the "Startup Type" section, and click OK.

Step 7 Remove the Database Instance

On node 1, run the following command to remove the OracleAS Metadata Repository database instance.

F:\oracle\bin> oradim -delete -sid sid

Step 8 Remove the Oracle Home for the OracleAS Metadata Repository and Oracle Internet Directory

From node 1, remove the Oracle home for the OracleAS Metadata Repository and Oracle Internet Directory. You need to remove it because you will be installing it again in the same directory from node 2.

Step 9 Remove the Oracle Home for Oracle Delegated Administration Services and OracleAS Single Sign-On

From node 3, remove the Oracle home for Oracle Delegated Administration Services and OracleAS Single Sign-On. You need to remove it because you will be installing it again in the same directory from node 4.

Step 10 Install OracleAS Metadata Repository and Oracle Internet Directory

From node 2, install the OracleAS Metadata Repository and Oracle Internet Directory. Use the same value for Oracle home, instance name, SID, and so on when you installed it from node 1. Follow the steps in step 3, "Install OracleAS Metadata Repository and Oracle Internet Directory on the Shared Drive from Node 1".

Step 11 Install Oracle Delegated Administration Services and OracleAS Single Sign-On

From node 4, install Oracle Delegated Administration Services and OracleAS Single Sign-On. Use the same value for Oracle home, instance name, SID, and so on when you installed it from node 3. Follow the steps in step 4, "Install Oracle Delegated Administration Services and OracleAS Single Sign-On from Node 3".

Step 12 Create a pfile for the Database

Oracle Fail Safe requires that the database has a pfile, which is a text file that contains the parameters for the database. See Section 11.12.1, "Create a pfile for the Database" for specific steps.

Step 13 Make OracleAS Metadata Repository Highly Available

Add OracleAS Metadata Repository as a resource to the "MROID" group in Oracle Fail Safe. This enables Oracle Fail Safe to fail over OracleAS Metadata Repository to the secondary node if the primary node fails. See Section 11.12.2, "Make OracleAS Metadata Repository Highly Available" for details.

Step 14 Add the Shared Disk as a Dependency for the Listener

This enables Oracle Fail Safe to access the shared disk first, then the listener, which is installed on the shared disk. See Section 11.12.3, "Add the Shared Disk as a Dependency for the Listener" for details.

Step 15 Make OPMN Highly Available

Add OPMN as a resource to the "MROID" group in Oracle Fail Safe. See Section 11.12.4, "Make OPMN Highly Available" for details.

Step 16 Make Application Server Control Highly Available

Add Application Server Control as a resource to the "MROID" group in Oracle Fail Safe. See Section 11.12.6, "Make Application Server Control Highly Available" for details.

Step 17 Move the "SSODAS" Group to Node 4

Using Cluster Administrator, move the "SSODAS" group to node 4. In Cluster Administrator, right-click the group and select Move Group.

Step 18 Start up Services on the Oracle Home in Node 4

Start up services associated with the Oracle home in node 4:

• Oracle<OracleHomeName>ProcessManager

• Oracle<OracleHomeName>ASControl

Step 19 Verify Installations

To verify the installation on nodes 1 and 2, access the Application Server Control page for the node using the virtual hostname in the URL (for example: http://vhost.mydomain.com:1156).

The virtual hostname is the value you entered in the Specify Virtual Hostname screen (step 6.). The default port number is 1156. You can verify the port number by looking in the ORACLE_HOME\install\portlist.ini file.

Similarly, to verify the installation on nodes 3 and 4, access the Application Server Control page for the node using the virtual hostname in the URL (for example, http://vhost_2.mydomain.com:1156).

The virtual hostname is the value you entered in the Specify Virtual Hostname screen (step 7.).

Step 20 Make OPMN Highly Available

Add OPMN as a resource to the "SSODAS" group in Oracle Fail Safe. See Section 11.12.4, "Make OPMN Highly Available" for details.

Step 21 Add the Shared Disk as a Dependency for OPMN

This ensures Oracle Fail Safe access the shared disk before starting up OPMN. See Section 11.12.5, "Add the Shared Disk as a Dependency for OPMN".

Step 22 Make Application Server Control Highly Available

Add Application Server Control as a resource to the "SSODAS" group in Oracle Fail Safe. See Section 11.12.6, "Make Application Server Control Highly Available" for details.

Step 23 Check that the Correct Listener Is Active

Oracle Fail Safe creates another listener, and this is the listener that needs to be running. See Section 11.12.7, "Check that the Correct Listener Is Active" for details.

11.9.1 Installing in Separate Oracle Homes

To install OracleAS Cold Failover Cluster (Middle-Tier) in separate Oracle Homes, perform the following steps.

11.9.2 Installing in a Single Oracle Home

To install OracleAS Cold Failover Cluster (Middle-Tier) on a shared disk, perform the following steps.

C:\> ORACLE_HOME\bin\chgtocfmt -v physhost_mt.mydomain.com -p password -n [-s] [-b] [-e] [-w physhost_mt.mydomain.com]

11.9.3 Expanding the Middle Tiers

After installing the OracleAS Cold Failover Cluster (Middle-Tier), you may decide you need a component that is not installed or configured on the middle tier.

If you decide to add additional components, see Section 7.14, "Expanding a MiddleTier" for installation instructions. If you need to configure components that were not previously configured, see the Oracle Application Server Administrator's Guide. For installations in separate Oracle homes, you will need to expand the middle tiers on both nodes of the cluster.

Note that the OracleAS Wireless component is not supported for a OracleAS Cold Failover Cluster (Middle-Tier) installed in single Oracle home.

After adding or configuring additional components, you need to run the chgtocfmt command using the -e option. All of the other options should be the same as the first time you ran it. For example, if you ran this command the first time:

C:\> ORACLE_HOME\bin\chgtocfmt -v vhost_mt.mydomain.com -p password -w cfcwebcache.mydomain.com

then you should run the following command after expanding the middle tiers:

C:\> ORACLE_HOME\bin\chgtocfmt -v vhost_mt.mydomain.com -p password -w cfcwebcache.mydomain.com -e

For installations in separate Oracle homes, you will need to run the chgtocfmt command on both nodes of the cluster.

11.10.1 Installation Steps

To create this configuration:

1. Set up the environment.

   • Section 11.2.1, "Ensure that the Event Log Service Is Running"

   • Section 11.2.2, "Get a Virtual Address for the Cluster"

   • Section 11.2.3, "Verify that Microsoft Cluster Server (MSCS) Is Installed on Both Nodes"

   • Section 11.2.4, "Determine the Name of the Cluster"

   • Section 11.2.5, "Determine a Domain User to Administer Oracle Fail Safe"

   • Section 11.2.6, "Install Oracle Fail Safe on the Local Storage of Each Node"

   • Section 11.2.7, "Create a Group in Oracle Fail Safe"

2. Create an alias for the hostnames.

   You do this by adding a line to the C:\%SystemRoot%\system32\drivers\etc\hosts file on each node. %SystemRoot% is either Winnt or Windows .

   Lines in the hosts file use the following format. You can have one or more aliases.

   ip_address   official_hostname   aliases...

   For example, if the nodes are called node1 and node2, and you want the alias to be called cfcwebcache, then you would add these lines to the hosts file:

   • In the hosts file on node1, add this line:

     123.45.67.22  node1.mydomain.com  node1  cfcwebcache.mydomain.com
     
     

   • In the hosts file on node2, add this line:

     123.45.67.33  node2.mydomain.com  node2  cfcwebcache.mydomain.com
     
     

3. Install OracleAS Infrastructure on the shared storage. See Section 11.3.2, "OracleAS Cold Failover Cluster (Infrastructure): Details of Installation Steps".

4. Create a staticports.ini file for the middle tiers. This is to ensure that the middle tiers use the same ports, and that the ports are different from the ports used by the OracleAS Infrastructure.

   When either node fails, a failover event occurs and all the OracleAS Infrastructure and middle-tier components will run on the same node. For the components to continue working, there must not be any port conflicts.

5. Install the middle tier on the local storage of each node.

   Notes for installing the middle tiers:

   • You need to use the same Oracle home path for both nodes.

   • You need to use the same Oracle Application Server instance name.

   • When the installer prompts you to enter the hostname for the Oracle Internet Directory, enter the virtual hostname for the OracleAS Infrastructure.

   • To install a J2EE and Web Cache middle tier, see Section 7.9, "Installing J2EE and Web Cache in a Database-Based Farm Repository and with Oracle Identity Management Access".

   • To install a Portal and Wireless middle tier, see Section 7.13, "Installing Portal and Wireless or Business Intelligence and Forms".

11.10.2 Post-Installation Steps

Perform the post-installation steps for node1 and node2 listed in Section 11.9.2.3, "Post-Installation Steps".

11.11.1 Edit the ORACLE_HOME\Apache\Apache\htdocs\index.html File

In the ORACLE_HOME\Apache\Apache\htdocs\index.html file, change all occurrences of the physical hostname (example: node1) to the virtual hostname (example: vhost), where node1 appears as a hostname.

Note that if node1 is used as part of the Oracle Application Server instance name, do not change it.

11.12.1 Create a pfile for the Database

A pfile is a text file that contains the database initialization parameters. Oracle Fail Safe requires a "pfile" for your database. You enter the fullpath to the pfile in the Parameter File field when you add the database to the group (see Figure 11-33).

1. Create a file called init<SID>.ora in the ORACLE_HOME\database directory.

2. Populate the file with the following lines:

   spfile=<ORACLE_HOME>\database\spfile<SID>.ora
   remote_login_passwordfile=<PARAMETER_VALUE>
   local_listener="(ADDRESS=(PROTOCOL=TCP)(HOST=<Virtual_IP>)(PORT=1521))"
   
   

   Replace <ORACLE_HOME> with the full path of your Oracle home directory.

   Replace <SID> with the SID of your database.

   Replace <PARAMETER_VALUE> with EXCLUSIVE or SHARED.

   Replace <Virtual_IP> with the virtual IP for the virtual hostname.

11.12.2 Make OracleAS Metadata Repository Highly Available

If you previously installed a database on a local disk of any node before you installed OracleAS Metadata Repository, you will need to move some files before making OracleAS Metadata Repository highly available. Move the following files to the shared disk where you installed the tablespaces.

• ORACLE_HOME\dbs\init.ora

• ORACLE_HOME\oradata\ORACLE_SID\control01.ctl

• ORACLE_HOME\oradata\ORACLE_SID\control02.ctl

• ORACLE_HOME\oradata\ORACLE_SID\control03.ctl

• ORACLE_HOME\oradata\ORACLE_SID\redo01.log

• ORACLE_HOME\oradata\ORACLE_SID\redo02.log

• ORACLE_HOME\oradata\ORACLE_SID\redo03.log

To make OracleAS Metadata Repository highly available, add it to the group.

1. On node 2, start up Oracle Fail Safe Manager from the Start menu.

   Start > Programs > Oracle - OracleHomeName > Oracle Fail Safe Manager

   OracleHomeName refers to the name that you gave to the Oracle home directory where you installed Oracle Fail Safe.

2. On the left side, expand Groups, right-click the group that you created in Section 11.2.7, "Create a Group in Oracle Fail Safe", and select Add Resource to Group. This starts up the Add Resource to Group wizard.

   Figure 11-31 Oracle Fail Safe Manager: Add Resource to Group

   
   Description of "Figure 11-31 Oracle Fail Safe Manager: Add Resource to Group"
   
   

3. Perform these steps in the Add Resource to Group wizard:

   1. Resource, Step 1

      Select Oracle Database, select the group, and click Next.

      Figure 11-32 Add Resource to Group Wizard (Adding Database), Resource, Step 1 Screen

      
      Description of "Figure 11-32 Add Resource to Group Wizard (Adding Database), Resource, Step 1 Screen"
      
      

   2. Database Identity, Step 2

      Enter the service name, the instance name, and the database name, and click Next.

      Figure 11-33 Add Resource to Group Wizard (Adding Database), Database Identity, Step 2 Screen

      
      Description of "Figure 11-33 Add Resource to Group Wizard (Adding Database), Database Identity, Step 2 Screen"
      
      

   3. Database Password, Step 3

      Select Yes, create the password file (recommended).

      User Name: Enter SYS as the username.

      Password and Confirm Password: Specify and confirm the password for the user SYS.

      Click Finish.

      Figure 11-34 Add Resource to Group Wizard (Adding Database), Database Password, Step 3 Screen

      
      Description of "Figure 11-34 Add Resource to Group Wizard (Adding Database), Database Password, Step 3 Screen"
      
      

   4. Finish Adding the Database to the Group screen

      Review the information and click OK. In particular, check that both nodes in the cluster are listed under Possible Owner Nodes.

      Figure 11-35 Add Resource to Group Wizard (Adding Database), Finish Adding the Database to the Group Screen

      
      Description of "Figure 11-35 Add Resource to Group Wizard (Adding Database), Finish Adding the Database to the Group Screen"
      
      

   5. Confirm Add Database to Group screen: click Yes.

      Figure 11-36 Add Resource to Group Wizard (Adding Database), Confirm Add Database to Group Screen

      
      Description of "Figure 11-36 Add Resource to Group Wizard (Adding Database), Confirm Add Database to Group Screen"
      
      

   6. If you get this warning about the listener: "FS-10230: The Oracle Net Listener LISTENER uses a host name ...", click Yes for Oracle Fail Safe to correct the discrepancies. Oracle Fail Safe has to set up a listener service with the name Oracle<OracleHomeName>TNSListenerFsl<virtualHostName>. This is the only listener service that runs on the nodes in the cluster.

      Figure 11-37 FS-10230 Warning

      
      Description of "Figure 11-37 FS-10230 Warning"
      
      

   7. Oracle Fail Safe Manager configures the database so that both nodes in the cluster can run it. During the configuration, Oracle Fail Safe Manager fails over the database from node 2 to node 1, as you can see in the "Node" column in Figure 11-38 ("STAJX17" is node 1). When it is complete, you get a screen similar to Figure 11-38.

      Figure 11-38 Add Resource to Group Wizard (Adding Database), Final Screen

      
      Description of "Figure 11-38 Add Resource to Group Wizard (Adding Database), Final Screen"
      
      

      You can ignore the warnings that are related to Oracle software, but you should investigate the warnings related to your system. Click OK in the status dialog.

   8. In the Oracle Fail Safe Manager, you should see the database listed under the group (Figure 11-39). You should see both the database SID and the database listener. Note that the listener is Oracle<OracleHomeName>TNSListenerFsl<virtualHostName>, not Oracle<OracleHomeName>TNSListener. Later in Section 11.12.7, "Check that the Correct Listener Is Active", you will disable the Oracle<OracleHomeName>TNSListener listener.

      Figure 11-39 Oracle Fail Safe Manager With the Database Added to the Group

      
      Description of "Figure 11-39 Oracle Fail Safe Manager With the Database Added to the Group"
      
      

11.12.3 Add the Shared Disk as a Dependency for the Listener

You need to set up the shared disk as a dependency for the listener (Disk X: in our example). You can do this by running commands or from the Cluster Administrator. Using the Cluster Administrator is recommended because it reduces the chances of making an error.

Using the Cluster Administrator

1. Start the Cluster Administrator from the Start menu:

   Windows 2000: Start > Programs > Administrative Tools > Cluster Administrator

   Windows 2003: Start > Administrative Tools > Cluster Administrator

2. Take the listener offline. To do this:

   1. On the left side, expand Groups.

   2. On the left side, select the group that you created earlier.

   3. On the right side, right-click the listener and select Take Offline.

      Figure 11-40 Cluster Administrator - Take the Listener Offline

      
      Description of "Figure 11-40 Cluster Administrator - Take the Listener Offline"
      
      

3. On the right side, right-click the listener, and select Properties.

4. Click the Dependencies tab, then click Modify.

   Figure 11-41 Cluster Administrator - Properties screen showing Dependencies tab

   
   Description of "Figure 11-41 Cluster Administrator - Properties screen showing Dependencies tab"
   
   

5. Move the disk to the Dependencies list, and click OK.

   Figure 11-42 Cluster Administrator - Modify Dependencies screen

   
   Description of "Figure 11-42 Cluster Administrator - Modify Dependencies screen"
   
   

6. Click Apply in the properties dialog.

7. Bring the listener back online. To do this, right-click the listener on the right side, then select Bring Online.

   Figure 11-43 Cluster Administrator - Bring the Listener Back Online

   
   Description of "Figure 11-43 Cluster Administrator - Bring the Listener Back Online"
   
   

Using Commands

Instead of using the Cluster Administrator, you can run commands from a shell.

1. Take the listener offline. You can do this using Cluster Administrator. See the first two steps in the "Using the Cluster Administrator" section above.

2. Run the following commands:

   C:\> cluster resource OracleiasTNSListenerFsliasha26 /offline
   C:\> cluster resource OracleiasTNSListenerFsliasha26 /addDep:"Disk F:"
   C:\> cluster resource OracleiasTNSListenerFsliasha26 /online
   
   

   Replace OracleiasTNSListenerFsliasha26 with the name of your listener. The listener name uses this format: Oracle<OracleHomeName>TNSListenerFsl<virtualHostName>.

   Replace Disk F: with the name of your shared disk.

11.12.4 Make OPMN Highly Available

To make OPMN highly available, add it to the Oracle Fail Safe group that you created in Section 11.2.7, "Create a Group in Oracle Fail Safe". OPMN corresponds to the Oracle<OracleHomeName>ProcessManager service.

1. Start up Oracle Fail Safe Manager.

2. On the left side, expand Groups, right-click the group that you created in Section 11.2.7, "Create a Group in Oracle Fail Safe", and select Add Resource to Group. This starts up the Add Resource to Group wizard.

   This is the same group and same menu item that you selected when you added the database to the group (see Figure 11-31).

3. Perform these steps in the Add Resource to Group wizard:

   1. Resource, Step 1

      Select Generic Service, verify that the group is correct, and click Next.

      Figure 11-44 Add Resource to Group Wizard (Adding OPMN), Resource, Step 1 Screen

      
      Description of "Figure 11-44 Add Resource to Group Wizard (Adding OPMN), Resource, Step 1 Screen"
      
      

   2. Generic Service Identity, Step 2

      Select Oracle<OracleHomeName>ProcessManager from Display Name, and click Next.

      Figure 11-45 Add Resource to Group Wizard (Adding OPMN), Generic Service Identity, Step 2 Screen

      
      Description of "Figure 11-45 Add Resource to Group Wizard (Adding OPMN), Generic Service Identity, Step 2 Screen"
      
      

   3. Generic Service Account, Step 3

      There are no startup parameters for OPMN. Click Next.

      Figure 11-46 Add Resource to Group Wizard (Adding OPMN), Generic Service Account, Step 3 Screen

      
      Description of "Figure 11-46 Add Resource to Group Wizard (Adding OPMN), Generic Service Account, Step 3 Screen"
      
      

   4. Generic Service Disks, Step 4

      There should not be anything under Selected Disks. Click Next.

      Figure 11-47 Add Resource to Group Wizard (Adding OPMN), Generic Service Disks, Step 4 Screen

      
      Description of "Figure 11-47 Add Resource to Group Wizard (Adding OPMN), Generic Service Disks, Step 4 Screen"
      
      

   5. Generic Service Dependencies, Step 5

      Available Resources list the resources in the group. The resources that you have to move to Resource Dependencies depend on the configuration that you are installing:

      Table 11-13 Resource Dependencies

      If you are installing this configuration:	Move these items to "Resource Dependencies"	Items Left in "Available Dependencies"
      OracleAS Cold Failover Cluster (Infrastructure) Distributed OracleAS Cold Failover Cluster (Infrastructure)	Database SID Database TNS listener	IP Address Network Name
      OracleAS Cold Failover Cluster (Identity Management) Distributed OracleAS Cold Failover Cluster (Identity Management) OracleAS Cold Failover Cluster (Middle-Tier)	none	IP Address Network Name
      For the OracleAS Metadata Repository and Oracle Internet Directory nodes in an Oracle Delegated Administration Services and OracleAS Single Sign-On in OracleAS Cold Failover Cluster	Database SID Database TNS listener	IP Address Network Name
      For the Oracle Delegated Administration Services and OracleAS Single Sign-On nodes in an Oracle Delegated Administration Services and OracleAS Single Sign-On in OracleAS Cold Failover Cluster	none	IP Address Network Name

      
      

      Click Next.

      Figure 11-48 Add Resource to Group Wizard (Adding OPMN), Generic Service Dependencies, Step 5 Screen

      
      Description of "Figure 11-48 Add Resource to Group Wizard (Adding OPMN), Generic Service Dependencies, Step 5 Screen"
      
      

   6. Generic Service Registry, Step 6: Click Finish.

      Figure 11-49 Add Resource to Group Wizard (Adding OPMN), Generic Service Registry, Step 6 Screen

      
      Description of "Figure 11-49 Add Resource to Group Wizard (Adding OPMN), Generic Service Registry, Step 6 Screen"
      
      

   7. Finish Adding the Generic Service to the Group

      Verify the information and click OK. In particular, check that both nodes in the cluster are listed under Possible Owner Nodes.

      Figure 11-50 Add Resource to Group Wizard (Adding OPMN), Finish Adding the Generic Service to the Group Screen

      
      Description of "Figure 11-50 Add Resource to Group Wizard (Adding OPMN), Finish Adding the Generic Service to the Group Screen"
      
      

   8. Confirm Add Generic Service to Group screen: Click Yes.

      Figure 11-51 Add Resource to Group Wizard (Adding OPMN), Confirm Add Generic Service to Group Screen

      
      Description of "Figure 11-51 Add Resource to Group Wizard (Adding OPMN), Confirm Add Generic Service to Group Screen"
      
      

      Oracle Fail Safe Manager now configures the Process Manager service so that both nodes in the cluster can run it. When it is done, it displays a screen similar to Figure 11-52. Click OK in the success dialog.

      Figure 11-52 Add Resource to Group Wizard (Adding OPMN), Final Screen

      
      Description of "Figure 11-52 Add Resource to Group Wizard (Adding OPMN), Final Screen"
      
      

   9. In the Oracle Fail Safe Manager, you should see the Process Manager service listed under the group.

      Figure 11-53 Oracle Fail Safe Manager With the Process Manager Service Added to the Group

      
      Description of "Figure 11-53 Oracle Fail Safe Manager With the Process Manager Service Added to the Group"
      
      

11.12.5 Add the Shared Disk as a Dependency for OPMN

This procedure is very similar to Section 11.12.3, "Add the Shared Disk as a Dependency for the Listener". The only difference is that you select Oracle<OracleHomeName>ProcessManager instead of the listener in Cluster Administrator.

1. Start the Cluster Administrator from the Start menu:

   Windows 2000: Start > Programs > Administrative Tools > Cluster Administrator

   Windows 2003: Start > Administrative Tools > Cluster Administrator

2. Take OPMN offline. To do this:

   1. On the left side, expand Groups.

   2. On the left side, select the group that you created earlier.

   3. On the right side, right-click Oracle<OracleHomeName>ProcessManager and select Take Offline.

3. On the right side, right-click Oracle<OracleHomeName>ProcessManager, and select Properties.

4. Click the Dependencies tab, then click Modify.

5. Move the disk to the Dependencies list, and click OK.

6. Click Apply in the properties dialog.

7. Bring OPMN back online. To do this, right-click Oracle<OracleHomeName>ProcessManager on the right side, then select Bring Online.

11.12.6 Make Application Server Control Highly Available

To make Application Server Control highly available, add it to the Oracle Fail Safe group that you created in Section 11.2.7, "Create a Group in Oracle Fail Safe". Application Server Control corresponds to the Oracle<OracleHomeName>ASControl service.

1. Start up Oracle Fail Safe Manager.

2. On the left side, expand Groups, right-click the group that you created in Section 11.2.7, "Create a Group in Oracle Fail Safe", and select Add Resource to Group. This starts up the Add Resource to Group wizard.

   This is the same group and same menu item that you selected when you added the database to the group (see Figure 11-31).

3. Perform these steps in the Add Resource to Group wizard:

   1. Resource, Step 1

      Select Generic Service, verify that the group is correct, and click Next.

      Figure 11-54 Add Resource to Group Wizard (Adding Application Server Control), Resource, Step 1 Screen

      
      Description of "Figure 11-54 Add Resource to Group Wizard (Adding Application Server Control), Resource, Step 1 Screen"
      
      

   2. Generic Service Identity, Step 2

      Select Oracle<OracleHomeName>ASControl from Display Name, and click Next.

      Figure 11-55 Add Resource to Group Wizard (Adding Application Server Control), Generic Service Identity, Step 2 Screen

      
      Description of "Figure 11-55 Add Resource to Group Wizard (Adding Application Server Control), Generic Service Identity, Step 2 Screen"
      
      

   3. Generic Service Account, Step 3

      There are no startup parameters for Application Server Control. Click Next.

      Figure 11-56 Add Resource to Group Wizard (Adding Application Server Control), Generic Service Account, Step 3 Screen

      
      Description of "Figure 11-56 Add Resource to Group Wizard (Adding Application Server Control), Generic Service Account, Step 3 Screen"
      
      

   4. Generic Service Disks, Step 4

      There should not be anything under Selected Disks. Click Next.

      Figure 11-57 Add Resource to Group Wizard (Adding Application Server Control), Generic Service Disks, Step 4 Screen

      
      Description of "Figure 11-57 Add Resource to Group Wizard (Adding Application Server Control), Generic Service Disks, Step 4 Screen"
      
      

   5. Generic Service Dependencies, Step 5

      Move the Process Manager service to the Resource Dependencies column. Click Next.

      Figure 11-58 Add Resource to Group Wizard (Adding Application Server Control), Generic Service Dependencies, Step 5 Screen

      
      Description of "Figure 11-58 Add Resource to Group Wizard (Adding Application Server Control), Generic Service Dependencies, Step 5 Screen"
      
      

   6. Generic Service Registry, Step 6: Click Finish.

      Figure 11-59 Add Resource to Group Wizard (Adding Application Server Control), Generic Service Registry, Step 6 Screen

      
      Description of "Figure 11-59 Add Resource to Group Wizard (Adding Application Server Control), Generic Service Registry, Step 6 Screen"
      
      

   7. Finish Adding the Generic Service to the Group

      Verify the information and click OK. In particular, check that both nodes in the cluster are listed under Possible Owner Nodes.

      Figure 11-60 Add Resource to Group Wizard (Adding Application Server Control), Finish Adding the Generic Service to the Group Screen

      
      Description of "Figure 11-60 Add Resource to Group Wizard (Adding Application Server Control), Finish Adding the Generic Service to the Group Screen"
      
      

   8. Confirm Add Generic Service to Group screen: Click Yes.

      Figure 11-61 Add Resource to Group Wizard (Adding Application Server Control), Confirm Add Generic Service to Group Screen

      
      Description of "Figure 11-61 Add Resource to Group Wizard (Adding Application Server Control), Confirm Add Generic Service to Group Screen"
      
      

      Oracle Fail Safe Manager now configures the Application Server Control service so that both nodes in the cluster can run it. When it is done, click OK in the success dialog.

   9. In the Oracle Fail Safe Manager, you should see the Application Server Control service listed under the group.

      Figure 11-62 Oracle Fail Safe Manager With the Application Server Control Service Added to the Group

      
      Description of "Figure 11-62 Oracle Fail Safe Manager With the Application Server Control Service Added to the Group"
      
      

11.12.7 Check that the Correct Listener Is Active

When you added the database to the group (in Section 11.12.2, "Make OracleAS Metadata Repository Highly Available"), Oracle Fail Safe created a listener called Oracle<OracleHomeName>TNSListenerFsl<virtualHostName>. Make sure that this listener is active and running.

The other listener, Oracle<OracleHomeName>TNSListener, is no longer used. You should stop it (if it is running) and set its startup type to manual so that it is not started up automatically.

11.13.1 If You Plan to Install Middle Tiers on OracleAS Cold Failover Cluster Nodes

If you plan to install a non-cold failover cluster middle tier on an OracleAS Cold Failover Cluster node (primary or secondary), perform these tasks before installing the middle tier:

• Section 11.13.1.1, "Create a staticports.ini File for the Middle Tier"

11.13.2 Procedure for Installing Middle Tiers Against an OracleAS Cold Failover Cluster Infrastructure

To install middle tiers against OracleAS Infrastructure in an OracleAS Cold Failover Cluster, follow the procedures as documented in Chapter 7, "Installing Middle Tiers", but with these differences:

• In the Register with Oracle Internet Directory screen, enter the virtual hostname in the Hostname field.

• If you are installing the middle tier on an OracleAS Cold Failover Cluster node, you must follow these additional requirements:

  • Read Section 11.13.1, "If You Plan to Install Middle Tiers on OracleAS Cold Failover Cluster Nodes".