Skip Headers

Oracle® Fail Safe Release Notes
Release 3.3.3 for Windows
Part No. B12073-01
 

 

Copyright © 2004,  Oracle. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Oracle® Fail Safe

Release Notes

Release 3.3.3 for Windows

Part No. B12073-01

March 2004

This document describes the new features in this release, software errors fixed, software compatibility, hardware compatibility, notes about installation and deinstallation, and notes on configuring resources for high availability.

1 How These Notes Are Organized

These release notes are divided into the following sections:

2 New and Changed Features

This release of Oracle Fail Safe provides the new and changed features described in the following sections.

2.1 Support for Oracle Database Release 10.1.0.1

This release introduces support for Oracle Database release 10.1.0.1, excluding the Management Agent. It continues to provide support for the following Oracle resources:

  • Oracle Database

  • Oracle Intelligent Agent (release 9.2 and earlier)

In addition, you can continue to use Oracle Fail Safe Manager to manage Oracle HTTP Servers configured to be highly available with a prior release of Oracle Fail Safe.

See Software Compatibility for details about the supported version of each of these resources.

2.2 New fssvr /GETSECURITY Command Qualifier

This release introduces a new fssvr command qualifier, /GETSECURITY. The /GETSECURITY qualifier displays security information about the system where the command is run. Oracle recommends that you run the fssvr command with this qualifier (on each cluster node) to help diagnose FS-1075n errors (where n is a value between 0 and 7, inclusive).

The command and its associated output should be similar to the following:

fssvr /getsecurity

Looking up user account information for OracleMSCSServices.
The user account must be a domain user acount with local Administrator
privileges.  The user account must also have the 'Log on as batch job'
privilege. 

    User account specified for OracleMSCSServices is NEDCDOMAIN\cluadmin 
    User account specified has local Administrator privileges 
    User account has the 'Log on as batch job' privilege 

Looking up user account information for Cluster Service. The user account 
must be a domain user account with local Administrator privileges. The user
account must also have the 'Log on as batch job' privilege.

    User account specified for Cluster Service is NEDCDOMAIN\cluadmin
    User account specified has local Administrator privileges 
    User account has the 'Log on as batch job' privilege 

Checking to see if DCOM is enabled.  DCOM must be enabled.
    DCOM is enabled.

3 Software Errors Fixed

This section describes software errors that have been fixed in this release of Oracle Fail Safe.

3.1 Stalling of an isAlive Query Now Results in Failover

Previously, when an isAlive query stalled, Oracle Fail Safe did not fail over the database. This has been fixed.

3.2 FSCMD No Longer Exits Abnormally

Previously, under some circumstances, the FSCMD command-line interface would exit abnormally. This has been fixed.

3.3 Incorrect Display of Database Polling Information Fixed

In previous releases, in a Japanese environment only, the database polling information displayed on the property sheet was incorrect for a database resource. This has been fixed.

4 Software Compatibility

This section describes the software with which Oracle Fail Safe is compatible when installed on Microsoft Windows NT, Microsoft Windows XP, Microsoft Windows 2000, or Microsoft Windows Server 2003.

4.1 Oracle Fail Safe Compatibility When Installed on Microsoft Windows

This release of Oracle Fail Safe is compatible with the software shown in the following table when Oracle Services for MSCS is installed on Microsoft Windows NT Enterprise Edition version 4.0 (Service Pack 6a), or Microsoft Windows 2000 Advanced Server or Datacenter Server, and Oracle Fail Safe Manager is installed on one of the following operating systems:

  • Microsoft Windows NT version 4.0 (Service Pack 6a)

  • Microsoft Windows 2000

  • Microsoft Windows XP

  • Microsoft Windows Server 2003

Software Release or Version
Microsoft Cluster Server (MSCS) Version 1 or later
Oracle Database (Standard and Enterprise editions) Oracle8 8.0.6

Oracle8i 8.1.7

Oracle9i 9.0.1

Oracle9i 9.2.0.1

Oracle9i 9.2.0.2

Oracle 10g 10.1.0.1

Oracle Intelligent Agent Release 8.1.7

Release 9.0.1

Release 9.2.0.1

Release 9.2.0.2

Oracle Enterprise Manager Release 2.1

Release 2.2

Release 9.0.1

Release 9.2.0

Oracle HTTP Server Included with these Oracle Database releases:
  • 9.0.1

  • 9.2.0.1

  • 9.2.0.2

Included with these Oracle9iAS Release 1 releases:

  • 1.0.2.2.1

  • 1.0.2.2.2



Note:

Oracle Fail Safe does not support Oracle Enterprise Manager 10g Grid Control Agent.

4.2 Oracle Fail Safe Manager Backwards Compatibility

You can use Oracle Fail Safe Manager release 3.3.3 to connect to Oracle Services for MSCS release 3.3.3, 3.3.2, 3.3.1, and 3.2.1. Oracle Fail Safe Manager release 3.3.3 cannot connect to releases of the server prior to release 3.2.1.

Using Oracle Fail Safe Manager release 3.3.3 to configure resources that are no longer supported by Oracle Fail Safe (such as Oracle Forms and Reports) is not supported. If you attempt to access help for Oracle Fail Safe Manager dialog boxes and property sheets that correspond to resources that are no longer supported, no help is available and an error window opens with the following message: "The topic does not exist. Contact your application vendor for an updated Help file. (129)." This message is misleading. An updated Help file is not available.

You can install more than one Oracle Fail Safe Manager on a system. For example, you can install Oracle Fail Safe Manager release 3.3.3 to connect to server release 3.2.1 and later to configure databases, generic services, and Oracle HTTP Servers for high availability; install Oracle Fail Safe Manager release 3.3.2 in another Oracle home to configure Oracle Forms Server for high availability with server release 3.3.2, 3.3.1, or 3.2.1; and install Oracle Fail Safe Manager release 3.1 into another Oracle home to manage server release 3.1.

5 Hardware Compatibility

Consult your hardware vendor to ensure that the hardware you intend to use with Oracle Fail Safe is certified for use with Microsoft Cluster Server software.

6 Installation and Deinstallation

This section includes topics about Oracle Fail Safe installations.

For complete installation and deinstallation instructions, see the Oracle Fail Safe Installation Guide.

6.1 Reboot Twice After Upgrading from Oracle Fail Safe Release 2.1.3 to Oracle Fail Safe Release 3.3.2

After a new installation is complete, the installer will instruct you to reboot the system. This reboot will update the system path to include the Oracle Fail Safe release 3.3.2 directory.

If you are upgrading from Oracle Fail Safe release 2.1.3, then after the first reboot, run Verify Cluster in Oracle Fail Safe Manager to update the Oracle Fail Safe database resource DLL. Then reboot each cluster node a second time, so the cluster services can pick up the new resource DLL.

6.2 Do Not Run Microsoft Windows Event Viewer During Oracle Services for MSCS Installation

If you attempt to install Oracle Services for MSCS while the Microsoft Windows Event Viewer is running, the installation procedure may return an error indicating that it cannot copy the fsus.dll file (fsja.dll on Japanese systems) and asking if you want to retry, ignore, or cancel. You can continue the installation if you stop the Microsoft Windows Event Viewer and then click Retry in the Oracle Fail Safe installation Error window.

6.3 MSCS Cluster Administrator Displays Problems with Fail-Safe Resource Types

Sometimes, after completing an Oracle Fail Safe installation, you see problems with the fail-safe resource types (such as databases) in MSCS Cluster Administrator. MSCS Cluster Administrator denotes the problem by displaying an Oslash symbol (Ø) over the resource type name.

If this occurs, do the following:

  1. If you forgot to reboot the cluster nodes after installing Oracle Fail Safe, do so now.

  2. Make sure that the PATH environment variable includes the Oracle Services for MSCS path. (In the Command Prompt window, enter PATH. The Oracle Services for MSCS path (<Oracle_Home>\fs\fssvr\bin) should be included. If it is not included, add it, and then reboot the nodes on which the Oracle Services for MSCS path is missing.

  3. Make sure that the Oracle Fail Safe resource DLL, FsResOdbs.dll, is installed in <Oracle_Home>\fs\fssvr\bin.

    If the resource DLL is not there, reinstall Oracle Fail Safe.

  4. Use Oracle Fail Safe Manager to verify the cluster (on the Troubleshooting menu, select Verify Cluster), then reboot each cluster node, one at a time. The Verify Cluster command automatically verifies registration of Oracle resource DLLs. You may not need to reboot all cluster nodes. After you reboot one node, check MSCS Cluster Administrator to see if the Oslash symbol has been removed from the resource type names. If the Oslash symbol is gone, you do not need to reboot all cluster nodes.

7 Oracle Services for MSCS

This section includes topics about Oracle Services for MSCS.

7.1 DCOM Security Changes on Microsoft Windows 2000

If the list of Access permissions for the default setting of DCOM is empty, the SYSTEM and INTERACTIVE accounts have implicit access rights. In Microsoft Windows 2000, if a user or group is added to the list, the implicit rights no longer apply; rights are granted only to explicitly named users or groups. In Microsoft Windows NT, the SYSTEM and INTERACTIVE accounts retain their implicit rights.

During the installation of Oracle Services for MSCS, the Oracle Fail Safe user account is added to the default access permissions list. If the access list is empty, the SYSTEM account is automatically added, but not the INTERACTIVE account.

After installing Oracle Services for MSCS, if there are problems opening hyperlinks in an HTML file or problems using Microsoft Outlook or Outlook Express, use the dcomcnfg.exe tool to add the necessary users to the default access permissions list.

See Microsoft Support article Q274696 for more information.

7.2 Oracle Services for MSCS and Microsoft Cluster Server Can Run Under Different Accounts

When your cluster was first configured and Microsoft Cluster Server was first installed, it was installed under a Microsoft Windows user account.

Oracle Services for MSCS runs as a Microsoft Windows service under a domain user account (not the system account) that has Administrator privileges on all cluster nodes. When you install Oracle Services for MSCS, you are instructed to provide a user name and password combination for a user account that has the required privileges. This account does not have to be the same account under which Microsoft Cluster Server was installed.

Is Alive polling of Oracle Fail Safe resources is performed using the Microsoft Windows account under which Microsoft Cluster Server is running, not the account under which Oracle Services for MSCS is running.

8 Oracle Fail Safe Manager

This section includes topics about Oracle Fail Safe Manager.

8.1 Oracle Fail Safe Manager Requires a User Name and Password When Run on Microsoft Windows 2000, Microsoft Windows XP, or Microsoft Windows Server 2003

You must supply a user name and password when you log on to Oracle Fail Safe Manager running on a Microsoft Windows 2000, Microsoft Windows XP, or Microsoft Windows Server 2003 system.

If you log on to Oracle Fail Safe Manager running on any other operating system, you are not required to specify the user name and password if your user account has appropriate privileges.

9 Oracle Database

This section includes information about Oracle databases.

9.1 Errors During Execution of Verify Standalone Database Command

In some cases (perhaps due to another program updating the file) Microsoft Windows may determine that the initialization parameter file for the database is locked by another user and will not allow the file to be temporarily renamed or opened for read/write access. This can cause problems when the Verify Standalone Database command is executed and may result in somewhat cryptic error messages being reported. If you encounter error messages that are similar to the following when executing Verify Standalone Database, check to see if you can temporarily rename the initialization parameter file for the database without getting an operating system error message:

FS-10890: Oracle Services for MSCS failed during the Verify Standalone operation

FS-10818: The Oracle Database resource provider failed during preparation for configuration processing for resource TESTDB1.US.ORACLE.COM

FS-10160: Failed to verify standalone Oracle database TESTDB1.US.ORACLE.COM

FS-10611: Failed to open file d:\oracle\database\initestdb1.ora for read

0xB: An attempt was made to load a program with an incorrect format

If another application appears to have control of the file, you can resolve the problem by rebooting the cluster node that owns the disk where the file resides (be sure to move any cluster disks that contain database files back to the node that hosts the database after you reboot).

9.2 Default Oracle Intelligent Agent Is Stopped and Restarted When the Database Is Shut Down

The default Oracle Intelligent Agent incorrectly discovers fail-safe databases on the node where the default Oracle Intelligent Agent is running and maintains a connection to the database. (The default Oracle Intelligent Agent listens on the node's host address and therefore should not discover fail-safe databases because they use a virtual address.) Therefore, when a fail-safe database is taken offline in normal or transactional mode using Oracle Fail Safe Manager, Oracle Fail Safe shuts down the default Oracle Intelligent Agent prior to shutting down the database. Oracle Fail Safe restarts the default Oracle Intelligent Agent after the database shutdown operation is complete.

9.3 Create Sample Database

Oracle Fail Safe includes a Create Sample Database command that installs a preconfigured sample database on a cluster disk specified by the user. The sample database has limited functionality and is intended only for testing purposes and for use with the online Oracle Fail Safe Tutorial; it should not be used for production.

The following table shows the releases of the sample databases included with Oracle Fail Safe release 3.3.3, and the releases of the Oracle database that can be tested with the sample database.

Sample Database Release Used with Database Release
8.0.5 8.0.6
8.1.5 8.1.7
9.0.1 9.0.1
9.2.0 9.2.0
10.1.0 10.1.0

The sample database files can be installed only on a node where the appropriate release of the Oracle database is installed. For example, if Oracle database release 8.1.7 is installed, then only the sample database files for 8.1.5 will be installed during the Oracle Fail Safe installation.

There are known limitations in using the sample databases with releases other than the release for which they were originally created. When an 8.1.5 sample database is installed for use with Oracle database release 8.1.7, the following errors are returned when attaching to the database:

ERROR:
ORA-06533: PLS-908: The stored format of SYS.STANDARD is not supported by this release.

Error accessing packing DBMS_APPLICATION_INFO
ERROR:
ORA-06533: PLS-908: The stored format of SYS.STANDARD is not supported by this release.

The sample database feature provided by Oracle Fail Safe is to be used for testing only; to create a database for production, use the Oracle Database Configuration Assistant or create the database manually.

9.4 User Name for Database Must Be SYS

To ensure the success of all Oracle Fail Safe release 3.2.1, 3.3.1, 3.3.2, and 3.3.3 operations, the database user name must be "SYS" unless operating system authentication is used. If operating system authentication is used, then Oracle Fail Safe does not use the SYS account.

10 Oracle HTTP Server

This section includes information about Oracle HTTP Server.

10.1 Add Oracle HTTP Server to Group Operation Fails

If an Add Oracle HTTP Server to Group operation for Oracle database release 8.1.7 fails due to a problem with the default httpd.conf file, the following errors are returned during the clusterwide operation:

FS-10382: NTCLU-221 : Bringing resource <Oracle-HTTP-Server-name> online
** ERROR : FS-10726: Resource <Oracle-HTTP-Server-name> is in a failed state
** ERROR : FS-10012: Failed to bring the cluster resource <Oracle-HTTP-Server-name> online. Check the Windows NT event log for messages
** ERROR : FS-10782: The Oracle HTTP Server resource provider failed to bring resource <Oracle-HTTP-Server-name> online
** ERROR : FS-10497: Starting clusterwide rollback of the operation

To fix this problem, open the default httpd.conf file located in <Oracle_Home>/apache/apache/conf/httpd.conf and insert a comment character (#) in front of the commands that include the configuration for Apache JServ 1.1 and the Oracle configuration file for custom settings. After you insert the comment characters, the httpd.conf file will include lines similar to the following:

# Include the configuration for Apache JServ 1.1

# include "C:\Oracle\Ora81\Apache\Jserv\conf\jserv.conf"

# Include the Oracle configuration file for custom settings

# include "C:\Oracle\Ora81\Apache\Apache\conf\oracle_apache.conf"

11 Disk Resources

Oracle Fail Safe allows the use of EMC GeoSpan disks. However, if you attempt to add a resource to a group and an EMC GeoSpan disk used by the resource is not already in that group, then Oracle Fail Safe returns the error FS-10203 and rolls back the operation.

If this occurs, add the resource to the group that already contains the EMC GeoSpan disk that the resource requires.

12 Virtual Addresses

If an MSCS network name contains trailing spaces and you attempt to have Oracle Fail Safe Manager add a virtual address to a group, the operation fails and the following error is returned:

NT-5045: The cluster network was not found

The workaround to this problem is to rename the network name using MSCS Cluster Administrator to remove the trailing spaces.

13 Oracle Enterprise Manager Integration

This section includes information about integrating Oracle Fail Safe with Oracle Enterprise Manager.

13.1 Partial Support of JobOut Subdirectory

Oracle Intelligent Agent release 8.1.7 deposits its jobs output files into a directory called JobOut. For highly available Intelligent Agents, the JobOut directory is a subdirectory under the agent's ConfigPath directory on the cluster disk. The Intelligent Agent requires the JobOut subdirectory to run jobs.

When creating an Oracle Intelligent Agent and adding it to a group, Oracle Fail Safe creates the JobOut subdirectory on the cluster disk. However, when verifying a group with a highly available Intelligent Agent in it, Oracle Fail Safe does not verify that the JobOut subdirectory exists. In addition, when changing a highly available Intelligent Agent's cluster disk, Oracle Fail Safe does not create a JobOut subdirectory on the new disk, nor does it remove the JobOut subdirectory on the old disk.

13.2 Fail-Safe Database Discovered as Standalone Database on Physical Nodes

When you view standalone databases on physical nodes, you may see fail-safe databases that are online on the physical node being discovered. This problem appears on systems running Microsoft Windows NT version 4.0 Service Pack 5 or 6a.

If there is an Intelligent Agent resource in the group, then databases in the group will not be discovered under the physical nodes. The exception to this case is when the database uses more than one virtual address. If the first virtual address used in the listener.ora and tnsnames.ora files for the database is not selected for use by the agent, then the databases in the group will be discovered under the physical nodes.

13.3 Default Intelligent Agent of Physical Node Is No Longer Restarted by Oracle Fail Safe

Prior to Oracle Fail Safe release 3.1, the default Intelligent Agent of a physical node was restarted during the Add Database to Group and Remove Database from Group operations. Starting with Oracle Fail Safe 3.1, the default Intelligent Agent of a physical node is no longer automatically restarted. If you need an updated list of databases under the physical nodes, restart the default agent manually.

14 Documentation Updated for This Release

The following documentation has been updated for this release:

The documentation that comes with the kit is provided in HTML and PDF online formats. Viewing the PDF files requires Adobe Acrobat Reader 3.0 or later. You can download the newest version from the Adobe Web site at

http://www.adobe.com/prodindex/acrobat/readstep.html

Printed documentation is available for sale in the Oracle Store at

http://oraclestore.oracle.com/

15 Additional Information

Refer to the following Web sites for more information about Oracle Fail Safe:

16 Documentation Errors and Omissions

This section corrects known omissions from the Oracle Fail Safe documentation set for release 3.3.3.

16.1 FS-10254 Omitted from Oracle Fail Safe Error Messages

The following error message was omitted from Oracle Fail Safe Error Messages:

FS-10254 Unable to configure the Oracle Database 10g TNS listener due to an old listener on system.
Cause: The Oracle Database 10g TNS listener could not be configured because there is a TNS listener from a prior release of Oracle Database on the system.
Action: Upgrade the existing TNS listener to the Oracle Database 10g TNS listener, as follows:
  1. Stop the existing TNS listener.

  2. Move the entries for the default listener in the existing listener.ora file to the listener.ora file in the Oracle 10g home.

16.2 References to Microsoft Cluster Server (MSCS)

Prior to the introduction of Microsoft Windows 2000, Microsoft Corporation referred to Microsoft Cluster Service as Microsoft Cluster Server. Because Oracle Fail Safe works with both Microsoft Cluster Service and Microsoft Cluster Server, both products are referred to as Microsoft Cluster Server in the Oracle Fail Safe documentation.

16.3 Using Highly Available Databases with Oracle Data Guard

While Oracle Fail Safe provides high availability to single-instance Oracle databases, Oracle Data Guard provides disaster tolerance. For example, Oracle Fail Safe can ensure nearly continuous high availability for a given system, but does not protect against a disaster that incapacitates the site where that system resides. Similarly, while Oracle Data Guard provides excellent disaster recovery features, the time required to switch operations from the primary site to a physically separate site can range from several minutes to hours. By combining Oracle Fail Safe with Oracle Data Guard, your databases can be highly available and disaster tolerant.

If you have an Oracle Support contract, you can find information about using Oracle Data Guard with Oracle Fail Safe, by logging into OracleMetaLink and searching for note 259902.1 at

http://metalink.oracle.com

17 Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at

http://www.oracle.com/accessibility/
Accessibility of Links to External Web Sites in Documentation  This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.