print Printer View e-mail E-mail this page Bookmark Bookmark
Oracle Fail Safe Release Notes Skip Headers

Oracle Fail Safe Release Notes
Release 3.2.1 for Windows NT and Windows 2000
Go To Product List
Product

Oracle® Fail Safe

Release Notes

Release 3.2.1 for Windows NT and Windows 2000

October 2001

How These Notes Are Organized

These release notes are divided into the following sections:

New Features for This Release

Oracle Fail Safe provides high availability on Microsoft clusters for a complete Internet business solution. This release of Oracle Fail Safe provides the following new features:

  • Support for the following products:

    • Oracle9i

    • Oracle Applications Release 11i (release 11.5.4)

    • Oracle9i Application Server (Oracle9iAS) release 1.0.2.2

  • More robust support for database authentication (implemented through changes in the Add Resource to Group Wizard)

  • Availability enhancements:

    • No downtime is required when database password changes are made to a highly available database.

    • Oracle Services for MSCS makes a single sustained connection to the database during Is Alive polling. In previous releases, the Oracle Fail Safe Server connected to, and then disconnected from, the database at each Is Alive polling interval.

  • Updates to Oracle Fail Safe Manager:

    • Oracle Fail Safe Manager release 3.2.1 can be used with Oracle Fail Safe Server release 3.1.1 or 3.1.2, in addition to Oracle Services for MSCS release 3.2.1. This support of multiple releases of the server components makes upgrading your existing clusters easier and does not force you to upgrade all clusters simultaneously to the latest release of Oracle Fail Safe.

    • New property pages display the location of the quorum resource and the resources configured on each cluster node.

    • The tutorial is now accessible outside the context of Oracle Fail Safe Manager.

  • Oracle Fail Safe Server is replaced by Oracle Services for MSCS.

    Oracle Services for MSCS is a server used by both Oracle Fail Safe and Oracle Real Application Clusters Guard. Oracle Services for MSCS is customized for use with Oracle Fail Safe with software called Oracle Fail Safe server components. When you install the server software for Oracle Fail Safe, you install both Oracle Services for MSCS and the Oracle Fail Safe server components.

Software Errors Fixed

This section describes the primary software errors fixed in Oracle Fail Safe release 3.2.1:

  • The FSCMD command-line interface now returns the correct exit code. Prior to this release, the behavior of the FSCMD command-line interface was not always correct. Although FSCMD correctly returned an exit code of 0 or 1 for success or failure under most conditions, success was sometimes reported even if the executed command failed. This has been fixed; the FSCMD command-line interface now returns the correct exit code.

  • The Verify Cluster operation no longer hangs when Oracle Fail Safe is used with Dell OpenManage Array Manager.

  • False failovers no longer occur when operating system authentication is used and the primary domain controller (PDC) or backup domain controller (BDC) is inaccessible.

Software Compatibility

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

Oracle Fail Safe Compatibility When Installed on Windows NT

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 5 or 6a), and Oracle Fail Safe Manager is installed on one of the following operating systems:

Oracle Fail Safe Compatibility When Installed on Windows 2000

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 2000 Advanced Server or Datacenter Server, and Oracle Fail Safe Manager is installed on one of the following:

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.

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.

Inappropriate Error Returned During Installation

When you install Oracle Fail Safe, the last page of the Oracle Universal Installer Wizard may display the following message in the "Details for Oracle Services for MSCS Security Setup" portion of the wizard page: 

Failed loading 
com.sun.java.accessibility.util.EventQueueMonitor.java.lang.CassNotFound
Exception:com.sun.jsave.accessibility.util.EventQueueMonitor

This error is due to an Oracle Universal Installer problem and does not affect the installation of Oracle Fail Safe.

Reboot Twice After Upgrading from Oracle Fail Safe Release 2.1.3 to Oracle Fail Safe Release 3.2.1

After a new installation is complete, the Oracle Universal Installer will instruct you to reboot the system. This reboot will update the system path to include the Oracle Fail Safe 3.2.1 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.

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 (and select the components that you want).

  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.

Silent Installation Is Case-Sensitive

The Oracle Fail Safe silent installation is case-sensitive. You must enter all command-line syntax exactly as shown in the Oracle Fail Safe Installation Guide (for example, the -responseFile parameter must be entered using all lowercase characters, except for the F, as shown). You must enter the file specification using the case shown in Windows Explorer (for example, C:\Ofs\Silent_Install\OfsProducts.rsp).

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

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.

Oracle Services for MSCS

This section includes topics about Oracle Services for MSCS.

DCOM Security Changes on 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 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 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.

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 Windows user account.

Oracle Services for MSCS runs as a 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 Windows account that Microsoft Cluster Server is running under, not the account under which Oracle Services for MSCS is running.

Oracle Fail Safe Manager

This section includes topics about Oracle Fail Safe Manager.

Oracle Fail Safe Manager Requires a User Name and Password When Run on Windows 2000

Due to a named pipe problem in Windows 2000, you must supply a user name and password when you log on to Oracle Fail Safe Manager running on a Windows 2000 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.

Oracle Database

This section includes information about Oracle databases.

Default Oracle Intelligent Agent Is Stopped and Restarted When 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.

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 3.2.1, 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 

The sample database files can be installed only on a node where the appropriate release of the Oracle database server is installed. For example, if Oracle database server release 8.1.7 is installed, then only the sample database 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 server 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.

Support for Archive Logs

In Oracle8i release 8.1.7 and later, you can define an archive log destination as a service name instead of a disk location.

For example: 

log_archive_dest_1='LOCATION=f:\<dir_name> MANDATORY REOPEN=5' 
log_archive_dest_2='SERVICE=standby OPTIONAL REOPEN=120'

The example shows typical entries that are allowed in Oracle8i release 8.1.7 for archive log support:

  • The first entry specifies a file system destination. Oracle Fail Safe will check this location to make sure that the disk used is a cluster disk and accessible to all cluster nodes.

  • The second entry specifies a TNS service name entry of "standby." Oracle Fail Safe will not automatically update the tnsnames.ora file on all cluster nodes. You must manually edit or add the service name entry to the tnsnames.ora file on all cluster nodes.

Standby Support

Oracle Fail Safe supports configuring only the primary standby database on a cluster. Remote standby databases configured in either recovery mode or read-only mode cannot be configured on clusters using Oracle Fail Safe; they must run as standalone databases.

Change in Database Listener Resource and Database Resource Dependencies

When the Oracle Fail Safe database resource DLL tries to connect to a database, it uses the Oracle Net listener. If this connection fails, the database resource DLL uses an Oracle Net bequeath connection, which bypasses the Oracle Net listener. Therefore, the database is no longer dependent on the database listener for Oracle Fail Safe to connect to the database.

If the Oracle Net listener resource fails, it will be restarted based on its resource restart policy. Due to the removal of the dependency between the database and the database listener, the database will not be taken offline if the listener fails.

Standalone Database Resources Are No Longer Restarted Unconditionally During a Verify Operation

Oracle Fail Safe no longer automatically starts and stops database instances during a Verify Standalone Database operation.

User Name for Database Must Be SYS

To ensure the success of all Oracle Fail Safe release 3.2.1 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 HTTP Server

This section includes information about Oracle HTTP Server.

Add Oracle HTTP Server to Group Operation Fails

If an Add Oracle HTTP Server to Group operation for Oracle 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"

Oracle Reports Services

This section includes information about Oracle Reports Services. Note that prior to Oracle9iAS, Oracle Reports Services was referred to as Oracle Reports Server. Because Oracle Fail Safe supports both Oracle Reports Server and Oracle Reports Services, both products are referred to as Oracle Reports Server in the Oracle Fail Safe documentation and Oracle Fail Safe Manager.

Inconsistent NAMES.DEFAULT_DOMAIN Parameter Might Cause Oracle Reports Server to Fail

The value for the NAMES.DEFAULT_DOMAIN parameter in the net.ora file must be the same across all Oracle homes in the cluster. If it is not, you may experience problems with Oracle Reports Server resources. For example, an Add Oracle Reports Server to Group operation might fail or a Verify Group operation might fail if the group contains an Oracle Reports Server.

Incorrect Message When You Verify a Group Containing an Oracle Reports Server

When you verify a group that contains an Oracle Reports Server, the following message may be displayed when the service name for the Oracle Reports Server exists and is correct: 

FS-10693: Oracle Reports Server <report-name> does not exist in <Oracle_
Home>\Network\Admin\Tnsnames.ora on node <node-name>.
Do you want to create it with default port 9100?

This message is displayed each time you verify the group that contains the Oracle Reports Server regardless of how you respond to the error message query.

Oracle Forms Services

Prior to Oracle9iAS, Oracle Forms Services was referred to as Oracle Forms Server. Because Oracle Fail Safe supports both Oracle Forms Server and Oracle Forms Services, both products are referred to as Oracle Forms Server in the Oracle Fail Safe documentation and Oracle Fail Safe Manager.

Oracle Forms Load Balancer Server

This section includes information about Oracle Forms Load Balancer Server.

Validate the formsweb.cfg file After Adding an Oracle Forms Load Balancer Server Resource

After adding an Oracle Forms Load Balancer Server resource to a group, validate the MetricServerPort and ServerPort parameters in the formsweb.cfg file, which is used by the Forms CGI executable file. The file is located at <Oracle_Home>\Forms60\formsweb.cfg. The MetricServerPort parameter that you specified should have the same value as the RequestPort startup parameter specified when you added the Oracle Forms Load Balancer Server resource. The ServerPort parameter should have the same value as the startup parameter for Oracle Forms Server.

Oracle MTS Service

This section includes information about Oracle MTS Service.

Add Oracle MTS to Group Operation Fails

If the Add Oracle MTS Service to Group operation fails, it may be due to a problem with the value for LAST_HOME in the Windows registry. If you attempt to add an Oracle MTS Service to a group and the LAST_HOME entry for HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/ALL_HOMES is not equal to the highest Oracle home number on your system, then the Add Oracle MTS Service to Group operation will fail and you will receive the following messages: 

FS-10778: The Oracle MTS Service resource provider failed to 
configure the cluster resource <resource-name>
FS-10618: Failed to change the configuration for NT service 
<service-name>
0x424: The specified service does not exist as an installed service

For example, if you have HOME0, HOME1, and HOME2 on your system, the value for LAST_HOME must be 2 for the Add Oracle MTS Service to Group operation to work. To fix the problem, change the value of LAST_HOME to match the highest Oracle home number on the local system and rerun the Add MTS Service to Group Wizard.

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-10202 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.

Oracle Enterprise Manager Integration

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

Discovery of Virtual Hosts with Oracle Intelligent Agent 8.1.7

To discover an Oracle Fail Safe virtual host using Oracle Intelligent Agent 8.1.7:

  1. In Oracle Enterprise Manager, right-click on Nodes.

  2. Select Discover Nodes.

  3. Enter the virtual host name without the domain name.

If you enter the virtual hostname with the domain name, you will get an error. This restriction applies only to the first time you discover a virtual host. Subsequent times, entering the virtual host name with or without the domain name will not return an error.

Oracle Intelligent Agent Release 8.1.7 and 9.0.1 Are the Only Supported Releases

Oracle Fail Safe 3.2.1 supports Oracle Intelligent Agent release 8.1.7 and 9.0.1 only. Oracle Intelligent Agent release 8.1.7 and 9.0.1 support all Oracle database releases that Oracle Fail Safe 3.2.1 supports.

Oracle Intelligent Agent release 8.1.7 is available with the Oracle 8.1.7 database or as a standalone product in the Oracle 8.1.7 CD pack. As with all 8.1.7 products, Oracle Intelligent Agent can be installed in an Oracle home that contains only other 8.1.7 products, or in its own Oracle home.

Oracle Intelligent Agent release 9.0.1 is available with the Oracle 9.0.1 database or as a standalone product in the Oracle 9.0.1 CD pack. As with all 9.0.1 products, Oracle Intelligent Agent can be installed in an Oracle home that contains only other 9.0.1 products, or in its own Oracle home.

When you add an Intelligent Agent resource to a group, you select the agent from the 8.1.7 or 9.0.1 home.

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 release 3.2.1 creates the JobOut subdirectory on the cluster disk. However, when verifying a group with a highly available Intelligent Agent in it, Oracle Fail Safe release 3.2.1 does not verify that the JobOut subdirectory exists. In addition, when changing a highly available Intelligent Agent's cluster disk, Oracle Fail Safe release 3.2.1 does not create a JobOut subdirectory on the new disk, nor does it remove the JobOut subdirectory on the old disk.

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 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.

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

Prior to Oracle Fail Safe release 3.1, the default Intelligent Agent of a physical node was restarted during the Create Sample Database, Delete Sample Database, 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.

Documentation Updated for This Release

The following documentation has been updated for this release.

  • Oracle Fail Safe Concepts and Administration Guide (part number A95194-01)

  • Oracle Fail Safe Installation Guide (part number A95195-01)

  • Oracle Services for MSCS Error Messages (part number A95196-01)

  • Oracle Fail Safe Release Notes

  • Oracle Fail Safe Tutorial

  • Oracle Fail Safe Help

  • Oracle Fail Safe Quick Tour

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

In North America, printed documentation is available for sale in the Oracle Store at:

http://oraclestore.oracle.com/

Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from:

http://www.oraclebookshop.com/

Customers outside of North America and EMEA can contact their Oracle representative to purchase printed documentation.

Additional Information

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

  • Oracle Fail Safe Corporate Web site:
    http://www.oracle.com/database/features/failsafe

  • Oracle Fail Safe on Oracle Technology Network:
    /tech/nt/failsafe/

    Updated software compatibility information, white papers, and so on are posted on the Oracle Technology Network Web site.

  • Oracle Support Services
    http://www.oracle.com/support/

    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.

  • Oracle Learning Network (OLN)
    http://www.oracle.com/education/oln/index.html

    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 Learning Network. You will need an OLN subscription to gain access to the course. To access the course after you register, search for the course title in Self-Paced Learning.

Documentation Errors and Omissions

This section corrects known errors in the Oracle Fail Safe documentation set for release 3.2.1.

In several manuals, references are made to Oracle release 8.1.5 and Oracle release 8.1.6. These references are misleading. Oracle Fail Safe release 3.2.1 does not support Oracle release 8.1.5 or Oracle release 8.1.6.

Oracle Fail Safe Tutorial

Lesson 12 of the Oracle Fail Safe Tutorial demonstrates how to add an Oracle Reports Server and Oracle HTTP Server to a group. You may find when you run the report in a Web browser, that the image associated with the Report does not load. This is a known problem for which there is no workaround. However, it does not affect failover for the Oracle Reports Server or Oracle HTTP Server.

Oracle Fail Safe Help

The help entry for the "Parameters Tab - TNS Listener" topic, includes the following description of the Use Listener Control Utility for Is Alive Polling option:

When the Oracle Net Listener Control Utility is used to perform Is Alive polling and logging is enabled (in the listener.ora file), three logs are written to the listener.log file every time Is Alive polling is performed (by default, once every minute). When the Oracle Net Listener Control Utility is not used, no logging is performed.

This description contains an inaccuracy; it should state that one log (not three) is written to the listener.log file every time Is Alive polling is performed.

Oracle Fail Safe Concepts and Administration Guide

The Oracle Fail Safe Concepts and Administration Guide describes how to implement transparent application failover with a highly available database server. However, it fails to mention that the transparent application failover feature is supported for Oracle database server Enterprise Edition only.

Moving the init.ora File

Currently, Oracle Fail Safe Manager does not provide the means to move an init.ora file. However, you can perform this task manually, by doing the one of the following:

For a database created by the Oracle Fail Safe Create Sample Database command:

  1. Copy the init.ora file to a cluster disk.

  2. Remove the sample database from the group.

  3. On the Troubleshooting menu, select Verify Standalone Database, and specify the new parameter file location in the Parameter File field.

  4. On the Resources menu, select Add Resource to Group, and on the Database Identity page, specify the new parameter file location in the Parameter File field.

For a database not created by the Oracle Fail Safe Create Sample Database command:

  1. Copy the init.ora file to a disk that is not being used by a resource in another group.

  2. Use MSCS Cluster Administrator to change the database resource private properties to specify the new init.ora file location.

  3. Run the Oracle Fail Safe Verify Group command on the group. This will ensure, for example, that if the parameter file is on a disk not already in the group containing the database, the disk will be added to that group.

  4. Using Oracle Fail Safe Manager, place the database offline and bring it back online to verify that there are no problems created by the new parameter file location.

Oracle is a registered trademark, and Oracle8i and Oracle9i are trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.

Copyright © 2001, Oracle Corporation.

All Rights Reserved.

Oracle
Copyright © 2001 Oracle Corporation.
All Rights Reserved.
Go To Product List
Product
E-mail this page
Printer View Printer View
Oracle Is The Information Company About Oracle | Oracle RSS Feeds | Careers | Contact Us | Site Maps | Legal Notices | Terms of Use | Privacy