Oracle® Fail Safe Release Notes
Release 3.3.4 for Microsoft Windows (64-Bit X64)
Release 3.3.4 for Microsoft Windows (64-Bit X64)
This document describes Oracle Fail Safe release 3.3.4 for Microsoft Windows (64-bit X64). 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)||Oracle Database 10g release 2 (10.2.0.1.0) 64-bit|
|Oracle Fail Safe Manager (32-bit)||Release 3.3.1, 3.3.2, 3.3.3, 3.3.4|
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, 3.3.2, 3.3.3, or 3.3.4. 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 on 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
Note:Oracle Fail Safe does not support Automatic Storage Management.
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 Oracle Fail Safe Installation Guide.
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.
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.
This section includes topics about Oracle Services for MSCS.
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.
IsAlive 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 topics about Oracle Fail Safe Manager.
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.
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).
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 functions 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.
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.
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.
In addition to these release notes, the Oracle Fail Safe Help has been updated for this release. See the following documentation, which was not updated for this release, but which is included in the kit, for additional information:
Oracle Fail Safe Concepts and Administration Guide
Oracle Fail Safe Installation Guide
Oracle Fail Safe Error Messages
Oracle Fail Safe Tutorial
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 Documentation
Provides links to Oracle Fail Safe documentation.
Oracle Enterprise Manager on the Oracle Technology Network
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.
This section corrects known errors and omissions from the Oracle Fail Safe documentation set for release 3.3.3. This section contains these topics:
You can configure Oracle Enterprise Manager 10g Grid Control to monitor databases configured for high availability. In general, the steps required to do so are:
Install the Oracle Management Agent.
Create an Oracle Management Agent that listens on a virtual address.
Add the Oracle Management Agent created in Step 2 to the same group as the Oracle Database (or databases) configured for high availability.
Configure the Oracle Management Agent to monitor the database or databases.
The sections that follow describe, in detail, the prerequisites and steps required to configure Oracle Management Agent for high availability.
You must install the following software on the cluster system before you can configure an Oracle Management Agent for high availability:
Microsoft Cluster Server – version 1 or later
Oracle Database – any release supported by Oracle Enterprise Manager 10g Grid Control
Oracle Management Agent
You must install the Management Agent on each cluster node, using the same Oracle home on each node.
Oracle Fail Safe – Release 3.3.1 or later
In addition, the following components must be configured:
An Oracle database instance must be configured for high availability.
An Oracle Enterprise Manager Management Server must be configured and available for setup. The Management Server need not reside on the cluster system.
Use Oracle Fail Safe Manager to add the new Management Agent to the fail-safe group that contains the databases it will monitor. You add the Management Agent to the group as a generic service. Follow these steps:
From the Resources menu, click Add to Group. The Add Resource to Group Wizard opens.
In the Resource Type box, select Management Agent.
In the Group Name box, select the group to which you want to add the Management Agent. This must be the group that contains the database you want to monitor with the Management Agent.
Click Next. The Management Agent Oracle Home page opens.
In the Oracle Home box, select the Oracle Home that you want to add to the group.
Click Next. The Management Agent Virtual Address page opens.
In the Virtual Address box, select the desired virtual address.
In the Port box, enter an open port number.
Click Finish. The Finish Adding Management Agent window opens.
This window summarizes the properties you have set with the wizard. If the summary information is correct, click OK. Otherwise, click Cancel and then click Back to find the page or pages in the wizard on which you want to change entries.
When you click OK, a window opens to display the progress of this clusterwide operation. (A clusterwide operation is one that occurs on multiple cluster nodes.)
To configure the highly available database for monitoring through the highly available Management Agent, follow these steps:
Log in to the Oracle Enterprise Manager 10g Grid Control Console.
Click the Targets tab. The Hosts page opens.
Click the Databases secondary tab. The Databases page opens.
Click Add (in the upper right-hand section of the page). The Add Database Target: Specify Host page opens.
Click the flashlight icon. The Search and Select Host window opens.
Select the virtual host, and then click Select. The Search and Select Host window closes and the Host field in the Add Database to Target: Specify Host page contains the selected virtual host.
Click Continue. The Targets Discovered on Host page opens.
Select the highly available database or databases that you want to monitor, then click OK. The Database Configuration Results page opens.
To test that the Management Agent is highly available, run a job against the highly available database it is monitoring, and follow these steps:
Log in to the Oracle Enterprise Manager 10g Grid Control Console.
Create a SQL job and submit it against the highly available database, as follows:
Click the Jobs tab. The Job Activity page opens.
In the Create Job box, select SQL Script, and then click Go. The Create 'SQL Script' Job page opens.
In the Job Name box, enter
TEST JOB, and in the SQL Script field, enter
SELECT * FROM ts$.
In the Databases region of the page, click Add. The Add Targets page opens.
Select the highly available database host name (which matches the virtual host name), and then click Add. The Create 'SQL Script' Job page opens.
In the Host and Database Credentials portion of the page, specify the database credentials, and then click Submit.
Make sure that the submitted job completes successfully.
Create another job against the same database (by following Step 1 and Step 2 in this list), but schedule it for 10 minutes from the current time.
Using Oracle Fail Safe Manager, fail over the group.
After 10 minutes have passed, check to see that the second job scheduled ran successfully.
When you reach this step, the Oracle Enterprise Manager 10g Grid Control Console shows three targets for the same database. During the Management Agent installation, the installer automatically discovers Oracle components, including highly available databases, and adds the discovered components as targets.
Because the highly available database instance exists on each cluster node, there are two targets for the database – each monitored by a different Management Agent. In addition, you create a third target when you add the database as a target for the highly available Management Agent listening on the virtual server (in Section 13.1.3).
You can safely remove the database targets that were discovered when the Management Agent was installed by following these steps:
Log in to the Oracle Enterprise Manager 10g Grid Control Console.
Click the Targets tab. The Hosts page opens.
Click the physical (as opposed to virtual) host name for one of the cluster nodes. The Host page for that physical host opens.
Click the Targets locator link.
Select the database on this host, and then click Remove.
Repeat Step 2 though Step 5 for each cluster node.
If you decide you no longer want to have an Oracle Management Agent configured for high availability, remove it from the group that contains it. When you do so, the Oracle Management Agent is deleted from the cluster.
To remove an Oracle Management Agent from a group, follow these steps:
Open Oracle Fail Safe Manager.
In the tree view, select the Oracle Management Agent that you want to remove and then, on the Resources menu, select Remove from Group.
The Confirm Remove from Group box opens. Click Yes in the Confirm Remove from Group box.
The description of transparent application failover in Oracle Fail Safe Concepts and Administration Guide includes a note that states: "The transparent application failover feature is supported for Oracle Database Enterprise Edition only."
Beginning with Oracle Database 10g Release 10.1.0.3, the transparent application failover feature is also supported for Oracle Database 10g Standard Edition.
Oracle Fail Safe provides the 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.
The following error messages are 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.
Section 126.96.36.199.1 of Oracle Fail Safe Concepts and Administration Guide contains a reference to a REMOTE_LOGIN_PASSWORD parameter for the database parameter file. There is no such parameter. The reference should be to the REMOTE_LOGIN_PASSWORDFILE parameter.
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. Accessibility 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 more information, visit the Oracle Accessibility Program Web site at
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
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.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
Oracle Fail Safe Release Notes, Release 3.3.4 for Microsoft Windows (64-Bit X64)
Copyright © 1996, 2005 Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.