Oracle® Fail Safe Installation Guide
Release 3.3.1 for Windows
Part No. A96685-01
This chapter provides general information and helpful tips to help you troubleshoot problems with Oracle Fail Safe installations and deinstallations. The following table shows the information provided in this chapter:
|Problems with the FSCMD Command After an Upgrade||Section 5.1|
|Error Creating a Sample Database||Section 5.2|
|Problems Installing Oracle Services for MSCS||Section 5.3|
|Problems Deinstalling Oracle Fail Safe and MSCS Software||Section 5.4|
|Problems with the User Rights Policy||Section 5.5|
|Network Configuration Problems||Section 5.6|
If you upgraded from Oracle Fail Safe release 184.108.40.206 to release 3.n and suddenly your FSCMD scripts do not work, it is probably because you need to include the /Cluster parameter on the FSCMD command.
Beginning with release 220.127.116.11, the /Cluster parameter is required on the FSCMD command. If you upgraded from release 18.104.22.168, your FSCMD scripts will not work and you might get an "invalid number of parameters" error message on the FSCMD command.
Also, the FSCMD command is now located in <Oracle_Home>\fs\fsmgr\bin directory, where <Oracle_Home> is the Oracle Fail Safe home directory. If you have not set your directory to <Oracle_Home>\fs\fsmgr\bin, you must specify the full path when running the FSCMD command.
If you install a database server after installing Oracle Fail Safe and then you try to create a sample database, the following error message appears:
FS-10270 Oracle Fail Safe sample database files not found in installation directory or CD-ROM.
You can install the sample databases when you want to create a sample database. When Oracle8i, Oracle8, or Oracle9i software is installed and you issue the Create Sample Database command, Oracle Fail Safe checks to see if all necessary sample files are located in the Oracle home where you installed Oracle Fail Safe. If the sample database files are not in the Oracle home, Oracle Fail Safe checks to see if the Oracle Fail Safe release 3.3.1 CD-ROM is online. If Oracle Fail Safe finds the sample files in either the Oracle home or on the CD-ROM, the Create Sample Database operation will succeed. Otherwise, it will return an error message. You can install the sample database files in the same Oracle home where you install Oracle Fail Safe, or save disk space by leaving the sample database files on the CD-ROM.
See Chapter 2 for more information about installing sample database files.
If you are running Oracle Universal Installer on a system that does not have MSCS installed (such as a client system) and you try to install Oracle Services for MSCS, the installer will display an error such as that shown in Figure 5-1.
Figure 5-1 Error Window for Improper Server Installation
If a message such as that shown in Figure 5-1 appears, do not continue with the installation. Click OK to back up through the installation windows and choose a Client Only installation (as described in Chapter 2).
Chapter 4 warns against deinstalling the MSCS software before you deinstall Oracle Fail Safe. If you deinstall the MSCS software on all cluster nodes, the cluster metadata information about Oracle Fail Safe will be removed.
If you deinstall MSCS from only one cluster node, the cluster metadata information still is available on the other node or nodes. To prevent the loss of the cluster metadata, do not deinstall MSCS from the other nodes; reinstall MSCS on the first node and click Join an Existing Cluster when prompted by the installation procedure to add the node back to the cluster and recover the cluster metadata.
If you accidentally deinstall MSCS software on all cluster nodes before you deinstall Oracle Fail Safe, you can recover your Oracle databases (after you reinstall MSCS on all cluster nodes) by performing the following steps using Oracle Fail Safe Manager:
Select the standalone resource in the Oracle Fail Safe Manager tree view.
Select the Verify Standalone Database operation from the Resources menu.
Enter the standalone database information in the Verify Standalone Database window.
When the verification completes successfully, add the standalone resource to a group using the Add Resource to Group Wizard.
Note:It might be necessary to manually restore the configuration of other non-database resources, such as your Web server or application server.
For Oracle Services for MSCS to run, the "Log on as batch job" and "Log on as a service" user rights policy must be enabled for the user account under which Oracle Services for MSCS runs. Typically, the Oracle Fail Safe installation enables this policy for the user account during the security setup. However, in some situations, the user rights policy might not be enabled correctly on a backup domain controller (BDC), because the account database on the BDC is read-only and cannot be changed directly.
To solve the problem, perform these steps:
Perform one of the following operations:
If the primary domain controller (PDC) is part of the cluster, install Oracle Fail Safe on the PDC.
If the PDC is not part of the cluster, grant "Log on as batch job" and "Log on as a service" rights to the Oracle Services for MSCS user account on the PDC.
Synchronize the account database with the BDC (using the Server Manager administration tool).
Install Oracle Fail Safe on the BDC.