Skip Headers

Oracle® Fail Safe Concepts and Administration Guide
Release 3.3.1 for Windows
Part No. A96684-01
Go To Table Of Contents
Contents
Go To Index
Index

Previous Next

12
Configuring Oracle Applications Concurrent Managers for High Availability

Oracle Fail Safe helps you configure an internal Oracle Applications concurrent manager for high availability. If a cluster node is shut down or fails, the group that contains the internal Oracle Applications concurrent manager fails over to another cluster node automatically.

Most interaction with Oracle Applications data is done through Applications forms. There are also reporting programs, however, that periodically need to be run. These programs may contain a large number of computations, so to ensure that they do not interfere with interactive operations, they can be configured to run on a concurrent processing server.

Processes that run on the concurrent processing server are called concurrent programs; they operate in the background while you and other users continue to work on other tasks. These programs are typically executable files written in C or reports written using Oracle Reports. You submit a request to run concurrent programs through Applications forms, which insert the request into a database table. When the table is read by a monitoring process, the request is assigned to one of several concurrent managers (also referred to as workers) running on the concurrent processing server. The concurrent manager processes the request and generates log and output files, which are stored on the concurrent processing server.

The internal concurrent manager process monitors the database table for new requests, controls other concurrent managers, and determines when a request should be processed and which concurrent manager should carry it out. It is the internal concurrent manager that you configure for high availability using Oracle Fail Safe.

The following topics are discussed in this chapter:

Topic Reference
Introduction   Section 12.1  
Discovering Standalone Oracle Applications Concurrent Managers   Section 12.2  
Adding Oracle Applications Concurrent Managers to a Group   Section 12.3  
Security Requirements for Oracle Applications Concurrent Managers   Section 12.4  
Troubleshooting Problems with Oracle Applications Concurrent Managers   Section 12.5  

Although this chapter describes how to make internal Oracle Applications concurrent managers highly available with Oracle Fail Safe, to provide high availability for your entire Internet solution you should also make the database used by the internal Oracle Applications concurrent manager highly available and any applications (such as Oracle Forms, Oracle Reports, and Oracle HTTP Servers) highly available.

12.1 Introduction

Figure 12-1 shows a two-node cluster in which the Oracle Applications concurrent manager, Oracle HTTP Server, and Oracle Forms Load Balancer Server have been configured for high availability on the application tier, the Oracle database has been configured on the database tier, and Web browsers and user-interface applications are installed on the client tier to create a three-tiered architecture. The Oracle Forms Load Balancer Clients and the Oracle Forms Servers associated with the Oracle Forms Load Balancer Server are installed on noncluster systems on the application tier.

Figure 12-1 Three-Tiered Architecture for Oracle Applications Concurrent Manager

Description of conc_man_architecture.gif follows
Description of the illustration conc_man_architecture.gif

12.2 Discovering Standalone Oracle Applications Concurrent Managers

You configure internal Oracle Applications concurrent managers for high availability using Oracle Fail Safe Manager. Before you can view standalone internal Oracle Applications concurrent managers in the Oracle Fail Safe Manager interface, they must first be discovered.

Oracle Services for MSCS discovers internal Oracle Applications concurrent managers by reviewing the list in the Windows service manager, finding all entries with a corresponding image name of ccmsvc.exe, and determining which have not already been configured for high availability. Oracle Fail Safe displays the newly discovered internal Oracle Applications concurrent managers in the Oracle Fail Safe Manager tree view under the Standalone Resources folder.

12.3 Adding Oracle Applications Concurrent Managers to a Group

You configure an internal Oracle Applications concurrent manager for high availability by adding it to a group using the Add Resource to Group Wizard in Oracle Fail Safe Manager. The group you specify must contain at least one virtual address. Typically, the group includes the following resources:

12.3.1 Before You Get Started

Before you add an internal Oracle Applications concurrent manager to a group, note the following:

  • Oracle Applications 11i must be installed on each node of the cluster that will be a possible owner node for the concurrent manager.

  • The database to which the internal Oracle Applications concurrent manager connects to fetch requests exists. (This database should be added to a group to provide a high level of availability, but this is not a requirement.)

    If the database with which the Oracle Applications concurrent manager is associated will be in the same group as the concurrent manager, add the database to the group before you add the concurrent manager to the group. This is required so that Oracle Fail Safe can set up the appropriate dependencies between the concurrent manager and the database with which it is associated. (Note that Oracle Fail Safe will also set up the appropriate dependency between the Oracle Applications concurrent manager and the Oracle Net network listener that is used by the highly available database.

  • A valid application configuration ID for use by the concurrent manager must exist in the Windows registry on each node of the cluster that will be a possible owner node for the concurrent manager. The application configuration ID identifies the runtime environment for the concurrent manager. Application configuration IDs are in the Windows registry at the following location, where <appl_config> is the application configuration ID:

    HKEY_LOCAL_MACHINE\Software\Oracle\Applications\11.5.0\<appl_config>
    
    

    Typically, the information on application configuration is added to the registry during the installation of Oracle Applications 11i.

12.3.2 Configuration Steps

Oracle Fail Safe Manager automates the steps required to make an internal Oracle Applications concurrent manager highly available with Oracle Fail Safe. In the Add Resource to Group Wizard in Oracle Fail Safe Manager, specify Oracle Concurrent Manager as the resource type.

Table 12-1 provides a quick reference of the tasks needed to configure an internal Oracle Applications concurrent manager for high availability. For step-by-step instructions about any particular task, refer to the Oracle Fail Safe online help. From the Oracle Fail Safe Manager menu bar, choose Help, then "Search for Help on."

Table 12-1 Steps for Configuring an Oracle Applications Concurrent Manager

Step Procedure Comments
1 Ensure that Oracle Applications 11i is installed on a private disk on each cluster node. See the Oracle Applications 11i documentation for installation information.
2 Invoke Oracle Fail Safe Manager. From the Windows Start menu, choose Oracle - <Oracle_Home>, then Oracle Fail Safe Manager.
3 Verify the cluster. Choose Troubleshooting, then Verify Cluster to run a procedure that validates the cluster hardware and software configurations.
4 Create a group and add one or more virtual addresses. Choose Groups, then Create to run the Create Group Wizard. The wizard helps you to set up failover and failback policies and automatically opens the Add Resource to Group Wizard to allow you to add a virtual address to the group. (Choose Resources, then Add to Group to add additional virtual addresses to the group.)
5 If the database with which the Oracle Applications concurrent manager is associated will be in the same group as the concurrent manager, add the database to the group before you add the concurrent manager to the group. This is required so that Oracle Fail Safe can set up the appropriate dependencies between the concurrent manager and the database with which it is associated.

Choose Resources, then Add to Group to run the Add Resource to Group Wizard. The wizard helps you to create and configure the Oracle database for high availability.

6 Add the internal Oracle Applications concurrent manager to the group. Choose Resources, then Add to Group to run the Add Resource to Group Wizard. The wizard helps you to create and configure the internal Oracle Applications concurrent manager for high availability.
7 Verify the group. Choose Troubleshooting, then Verify Group to check for and fix any problems with the group, virtual addresses, resources, or the failover configuration.
8 Configure other application components for failover. Configure other application and database servers with Oracle Fail Safe to make your entire application highly available.

12.3.3 Configuration Data for Oracle Applications Concurrent Managers

Oracle Fail Safe Manager provides the Add Resource to Group Wizard to help you configure an internal Oracle Applications concurrent manager for high availability. When you use the Add Resource to Group Wizard, you need the following data:

  • Possible owner nodes for the Oracle Applications concurrent manager, if the cluster consists of more than two nodes, or if one node is not available in a two-node cluster

  • The virtual address you want to associate with the internal Oracle Applications concurrent manager

  • The name of the internal Oracle Applications concurrent manager, the application configuration ID, and the directory on a shared cluster disk where you want log and output files stored

  • The Windows Administrator account under which the internal Oracle Applications concurrent manager will run

  • The connection information for the database from which the internal Oracle Applications concurrent manager fetches requests

  • The resource name of the database from which the internal Oracle Applications concurrent manager is associated (if that database has also been configured for high availability in the same group as the concurrent manager)

The clusterwide operation to add an internal Oracle Applications concurrent manager to a group will fail if:

  • Another concurrent manager with the same name already exists on the cluster

  • The application configuration ID does not exist in the Windows registry

  • The account under which the concurrent manager runs is not a Windows Administrator account on each node that is a possible owner node for the concurrent manager

  • Oracle Applications 11i is not installed on every cluster node that is a possible owner node for the concurrent manager

  • The database to which the internal Oracle Applications concurrent manager connects does not exist, the connection information for this database was entered incorrectly in the Add Resource to Group Wizard, or the information for this database in the tnsnames.ora file is incorrect

If there is an error adding or removing an internal Oracle Applications concurrent manager from a group, check the Windows Event Viewer (Application Log) for error messages from "Oracle Fail Safe."

The following sections describe in detail the data requirements for adding an internal Oracle Applications concurrent manager to a group.

12.3.3.1 Choose Nodes

If you are adding an Oracle Applications concurrent manager to a group and the cluster consists of more than two nodes, you are asked to specify which nodes should be possible owners for the Oracle Applications concurrent manager by specifying a list of selected nodes, as shown in Figure 12-2. To specify that a particular node should not be a possible owner for the Oracle Applications concurrent manager, select the node from the Selected Nodes list and click the left arrow.

Section 2.6.6 describes in detail the concept of the possible owner nodes list.

Figure 12-2 Choose Nodes Wizard Page When All Nodes Are Available

Description of pn_conc_wiz.gif follows
Description of the illustration pn_conc_wiz.gif

If you are adding an Oracle Applications concurrent manager to a group and the cluster consists of two or more nodes, but one or more nodes are unavailable, you are also asked to specify which nodes should be possible owners for the Oracle Applications concurrent manager. In this case, the wizard page displays which nodes are unavailable and why, as shown in Figure 12-3.

Figure 12-3 Choose Nodes Wizard Page When Any Node Is Unavailable

Description of pn_conc_wiz_unavail.gif follows
Description of the illustration pn_conc_wiz_unavail.gif

12.3.3.2 Oracle Applications Concurrent Manager Virtual Address

A group must contain at least one virtual address before you add an internal Oracle Applications concurrent manager to it. If the group to which you are adding an internal Oracle Applications concurrent manager contains more than one virtual address, you are asked to select which one you would like to associate with the internal Oracle Applications concurrent manager, as shown in Figure 12-4.

The virtual address will be the address that the concurrent manager uses as a host (computer) name.

Figure 12-4 Oracle Applications Concurrent Manager Virtual Address Wizard Page

Description of conc_virt_add.gif follows
Description of the illustration conc_virt_add.gif

12.3.3.3 Concurrent Manager Identity

The Add Resource to Group Wizard requests the following information about the internal Oracle Applications concurrent manager identity, as shown in Figure 12-5.

  • Concurrent manager name

    This is a name that will uniquely identify the internal Oracle Applications concurrent manager on the cluster.

  • Configuration ID

    This is the application configuration ID. It identifies an entry in the Windows registry:

     \\HKEY_LOCAL_MACHINE\Software\Oracle\APPLICATIONS\11.5.0\<config-id>
    
    

    This key defines the environment under which the internal Oracle Applications concurrent manager runs. It was defined when you installed Oracle Applications 11i.

  • Directory

    This specifies the cluster disk and parent directory for Oracle Applications concurrent manager log files and output files. The log files will be placed in a \log subdirectory of the parent directory and the output files will be placed in an \output subdirectory of the parent directory.

    If you specify a directory of X:\Apps_Logs, for example, then the log files will be placed in X:\Apps_Logs\log and the output files will be placed in X:\Apps_Logs\output.

    The parent directory is stored in the APPLCSF variable in the following Windows registry key:

    \\HKEY_LOCAL_MACHINE\Software\Oracle\APPLICATIONS\11.5.0\<config-id>\APPLCSF
    
    

Figure 12-5 Oracle Applications Concurrent Manager Identity Wizard Page

Description of concman_id.gif follows
Description of the illustration concman_id.gif

12.3.3.4 Concurrent Manager Authentication

The Add Resource to Group Wizard requests the following information about the account under which the internal Oracle Applications concurrent manager will run, as shown in Figure 12-6.

  • User name

    This is a user account with Windows Administrator privileges. If this is not a domain account, you must ensure that this account exists on each cluster node that is a possible owner for the internal Oracle Applications concurrent manager.

  • Password

    This is the password for the user account.

  • Confirm Password

    This is the same password as you entered in the Password field.

  • Domain

    This is the domain for the user account. If the user account is not a domain account, leave this box blank. Note that although you are not required to specify a domain account, such an account will make management easier and thus is recommended.

Figure 12-6 Concurrent Manager Authentication Wizard Page

Description of concman_auth.gif follows
Description of the illustration concman_auth.gif

12.3.3.5 Concurrent Manager Database

The Add Resource to Group Wizard requests the following information for the database from which the internal Oracle Applications concurrent manager gets requests, as shown in Figure 12-7.

  • User name

    This is the user name for an account that can connect to the database that contains the requests that the internal Oracle Applications concurrent manager reads.

  • Password

    This is the password for the account.

  • Confirm Password

    This is the same password as you entered in the Password field.

  • Service name

    This is the service name for the database.

  • Database

    This is the database name for the specified service name. You select a database from this box, if both of the following are true:

    • The group to which you are adding the internal Oracle Applications concurrent manager contains the database to which the concurrent manager connects.

    • The database resource name is not the same as the database service name.

      The database box is dimmed if the database resource name is the same as the database service name.

      The database box is not dimmed and you are asked to specify the database resource if the database resource name is not the same as the database service name; Oracle Fail Safe cannot automatically determine if the database in the group is the same database as that for which you are providing connection information.

      If a database is in the same group as that to which you are adding the internal Oracle Applications concurrent manager, but it is not the database to which the concurrent manager connects, then do not select it from the Database box.

Figure 12-7 Concurrent Manager Database Wizard Page

Description of concman_db.gif follows
Description of the illustration concman_db.gif

12.4 Security Requirements for Oracle Applications Concurrent Managers

To manage an internal Oracle Applications concurrent manager, use a user account with Administrator privileges. This account must have Administrator privileges on each cluster node that is a possible owner node for the concurrent manager. The account can be either a domain account (recommended) or an account local to each node.

The account that the internal Oracle Applications concurrent manager uses to connect to the database from which the concurrent manager fetches requests, needs no special privileges.

12.5 Troubleshooting Problems with Oracle Applications Concurrent Managers

General information about troubleshooting fail-safe resources is in Chapter 6. For general information about troubleshooting internal Oracle Applications concurrent managers, see the Oracle Applications 11i documentation.

If you have problems with an internal Oracle Applications concurrent manager configured for high availability, run the Verify Cluster operation to validate and fix any problems.

When you issue a Verify Group command on a group containing an internal Oracle Applications concurrent manager, Oracle Fail Safe does the following on all nodes that are possible owner nodes for the concurrent manager:

You can run the Verify Group operation at any time. However, you should run it when any of the following occurs:

If any problems are found during the group verification, Oracle Fail Safe prompts you to fix them or returns an error message that further describes the problem.

12.5.1 Problems Adding an Oracle Applications Concurrent Manager to a Group

To troubleshoot problems when adding a standalone internal Oracle Applications concurrent manager to a group, ensure that:

  • The database to be used by the concurrent manager is set up and accessible.

  • The account under which the concurrent manager is to run has Administrator privileges on all cluster nodes that will be possible owner nodes for the concurrent manager.

  • The application configuration ID specified in the Add Resource to Group Wizard exists on all cluster nodes that are possible owner nodes for the concurrent manager.

12.5.2 Problems Placing a Group Online

If there is a problem placing a group that contains an internal Oracle Applications concurrent manager online, try the following:

  • Verify the group.

    When you use the Verify Group command (from the Oracle Fail Safe Manager Troubleshooting menu), Oracle Fail Safe checks the group configuration and attempts to fix any problems that it finds. If the Verify Group command cannot fix the problem, it returns an error message that should help you to resolve the problem manually.

    If the Verify Group command finds a problem, it will prompt you on how to proceed.

  • Make sure that the Pending Timeout value is sufficient.

    If a group containing an internal Oracle Applications concurrent manager fails to come online or frequently fails over, check that the Pending Timeout value is set correctly. Failure to come online and frequent failovers occur if the Pending Timeout value is set too low.

    The Pending Timeout value specifies how long the cluster software waits for the internal Oracle Applications concurrent manager to resolve an unstable state (for example, unavailable, offline, or pending) before the cluster software assumes that the resource is in a failed state. If, for example, the cluster system has a heavy workload, it can appear as though the internal Oracle Applications concurrent manager is unavailable. Consider adjusting the Pending Timeout value to a value greater than the default 180 seconds.

    You can set the Pending Timeout value by modifying the resource properties, as follows:

    1. In the Oracle Fail Safe Manager tree view, select the internal Oracle Applications concurrent manager name.

    2. Click the Policies tab.

    3. In the Pending Timeout box, modify the Pending Timeout value.

    Set the Pending Timeout value to specify the length of time you want the cluster software to allow for the resource to be brought online (or taken offline) before considering the operation to have failed. The goal is to set the value high enough to prevent a cluster system from mistaking slow response time for unavailability, yet low enough to minimize the failover response time when a failure does occur.

12.5.3 Windows Service for Concurrent Manager Accidently Deleted

If you accidently delete the Windows service for a concurrent manager from a cluster node that is a possible owner node for the concurrent manager, run the Verify Group operation to re-create the Windows service.

12.5.4 Concurrent Manager Will Not Come Online

If the concurrent manager will not come online, run the Verify Group operation. The Verify Group operation will determine if either of the following is causing the problem:

  • The concurrent manager cannot connect to the database from which it fetches requests because there is a problem with the database connect string.

  • The user account under which the concurrent manager runs does not have Administrator privileges.

If the Verify Group operation indicates either of these as the problem, select the concurrent manager from the tree view in Oracle Fail Safe Manager and select the Database tab to modify the database connect string or the Parameters tab to modify the user account for the concurrent manager.

If neither of these is the source of the problem, check the Windows Event Viewer for information on what is preventing the concurrent manager from coming online.


Previous Next
Oracle Logo
Copyright © 1996, 2002 Oracle Corporation

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