This chapter provides general information to help you troubleshoot problems with Oracle Fail Safe installations and deinstallations. The following topics are covered in this chapter:
If you upgraded from Oracle Fail Safe release 2.1.3.0 to release 3.n and suddenly your FSCMD scripts do not work, then it is probably because you need to include the /Cluster parameter on the FSCMD command.
Beginning with release 2.1.3.1, the /Cluster parameter is required on the FSCMD command. If you upgraded from release 2.1.3.0, then 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 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, then the installer will open an error window to display an error that states that the Oracle Services for MSCS must be installed on a cluster running Microsoft Cluster Server. You must install Microsoft Cluster Server prior to installing Oracle Services for MSCS.
If such a message is displayed, do not continue with the installation. Click OK to back up through the installation windows and choose a Client Only installation. See Chapter 2 for more information about Client Only installation.
Chapter 4 warns against deinstalling the MSCS software before you deinstall Oracle Fail Safe. If you deinstall the MSCS software on all cluster nodes, then the cluster metadata information about Oracle Fail Safe will be removed.
If you deinstall MSCS from only one cluster node, then the cluster metadata information is still 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, then you can recover your 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 Oracle 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, then install Oracle Fail Safe on the PDC.
If the PDC is not part of the cluster, then 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 BDCby using the Server Manager administration tool.
Install Oracle Fail Safe on the BDC.