Oracle® Fail Safe Release Notes
Release 3.3.3 for Microsoft Windows (64-bit)
Part No. B14155-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.
Release 3.3.3 for Microsoft Windows (64-bit)
Part No. B14155-01
This document describes Oracle Fail Safe release 3.3.3 for Microsoft Windows (64-bit). It includes information about software compatibility, hardware compatibility, installation and deinstallation, and configuring Oracle databases for high availability.
These release notes are divided into the following sections:
This release of Oracle Fail Safe is a server-only release; it does not include Oracle Fail Safe Manager.
This release of Oracle Fail Safe is compatible with the software shown in the following table:
|Software||Release or Version|
|Microsoft Cluster Server (MSCS)||Version 5.0 or later|
|Oracle Database (Standard and Enterprise editions)||Oracle9i release 1 (9.2) 64-bit
Oracle Database 10g release 1 (10.1) 64-bit
|Oracle Intelligent Agent||Release 9.2.0 64-bit|
|Oracle Enterprise Manager||Release 9.2.0|
|Oracle Fail Safe Manager||Release 3.3.1
This 64-bit release of Oracle Fail Safe can be used with the 32-bit version of Oracle Fail Safe Manager release 3.3.1 or release 3.3.2. Oracle Fail Safe Manager can be found on the Oracle Fail Safe CD-ROM (32-bit) included with the Oracle Database kit and must be installed one of the following 32-bit Windows operating systems:
Microsoft Windows NT version 4.0 (Service Pack 6a)
Microsoft Windows 2000
Microsoft Windows Server 2003
Microsoft Windows XP
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.
This section includes topics about Oracle Fail Safe installations.
For complete installation and deinstallation instructions, see the Oracle Fail Safe Installation Guide.
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:
If you forgot to reboot the cluster nodes after installing Oracle Fail Safe, do so now.
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.
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.
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.
If you attempt to install Oracle Services for MSCS while the 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 Windows Event Viewer and then click Retry in the Oracle Fail Safe installation Error window.
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 account 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.
Be aware that 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.
This section includes information about Oracle databases.
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).
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.
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.
There are known limitations in using a sample database with a release other than the one for which it was originally created.
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.
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.
The default Intelligent Agent of a physical node is not automatically restarted during the Add Database to Group and Remove Database from Group operations. If you need an updated list of databases under the physical nodes, restart the default agent manually.
Only the Oracle Fail Safe Release Notes have been updated for this release. See the following documentation (updated for the 32-bit version of Oracle Fail Safe release 3.3.3) for additional information:
Oracle Fail Safe Concepts and Administration Guide (part number B12070-01)
Oracle Fail Safe Installation Guide (part number B12072-01)
Oracle Fail Safe Error Messages (part number B12071-01)
Oracle Fail Safe Tutorial
Oracle Fail Safe Help
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
Printed documentation is available for sale in the Oracle Store at
Refer to the following Web sites for more information about Oracle Fail Safe:
Oracle Fail Safe Corporate Web site
Oracle Fail Safe on the Oracle Technology Network
Provides updated software compatibility information, white papers, and so on.
Oracle Fail Safe Documentation
Provides links to Oracle Fail Safe documentation.
Oracle Support Services
Contact your Oracle support representative for technical assistance and additional information, or visit the Oracle Support Services Web site to find out about other available resources.
An eStudy class, Introduction to Oracle Fail Safe, which covers the basic concepts, features, and installation for MSCS and Oracle Fail Safe, is available on the Oracle University Web site. You will need to register to gain access to the course. To access the course after you register, click Go to My Online Courses, then enter the course title in the Search Catalog box and click Go.
This section corrects known omissions from the Oracle Fail Safe documentation set for release 3.3.3.
Some help topics refer to a "remote_login_password" database initialization parameter. This is not a valid database initialization parameter. The references should be to the remote_login_passwordfile database initialization parameter. The following Help topics contain the invalid reference:
Add Resource to Group: Database Identity
Verifying a Standalone Single-Instance Database
The following error message was omitted from Oracle Fail Safe Error Messages:
Stop the existing TNS listener.
Move the entries for the default listener in the existing listener.ora file to the listener.ora file in the Oracle Database 10g home.
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.
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 Oracle MetaLink and searching for note 259902.1 at
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
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.