6
Troubleshooting Tools

6.1.1 Verify Cluster

The Verify Cluster operation validates the installation and network configuration of the cluster. You can perform a cluster verification at any time by choosing:

Troubleshooting -> Verify Cluster

The first time you connect to a cluster after installing or upgrading the Oracle Fail Safe software, you are prompted to run Verify Cluster. You can run Verify Cluster at any time, however, and you should run it whenever the cluster configuration changes. The Verify Cluster operation verifies that:

• Each Oracle home name into which Oracle software is installed is the same on all cluster nodes

  If, for example, OFS is the Oracle home name for the Oracle Fail Safe software on one cluster node, then OFS must be the Oracle home name on all nodes in the cluster where Oracle Fail Safe is installed. Similarly, if OfsDb is the Oracle home name for the Oracle database server software on one cluster node, then it must be the Oracle home name on all nodes in the cluster where the Oracle database server software is installed.

• The Oracle Services for MSCS release is identical on all nodes

• The resource providers (components) are configured identically on at least two of the nodes that are possible owners for each resource

• The Host Name/IP Address mappings resolve consistently across all nodes in the cluster

  If there is a problem with inconsistent mapping, the Verify Cluster command returns errors indicating that the order of network adapters may be incorrect. See Appendix B for details.

Verify Cluster also registers Oracle resource DLLs with Microsoft Cluster Server (MSCS).

Figure 6-2 shows the output from a typical Verify Cluster operation.

Description of the illustration cwo_vc.gif

If you run the Verify Cluster operation and it does not complete successfully, it might indicate one or more of the following problems:

• A problem exists in the configuration of the hardware, network, or the MSCS software.

• A problem exists in the symmetry of the Oracle homes and versions.

• A problems exists with the Oracle Fail Safe installation (for example, with the symmetry of the resource providers).

If the operation completes successfully, but you are having problems with Oracle Fail Safe, the problem is based in the Oracle Fail Safe configuration.

6.1.2 Verify Group

The Verify Group operation does the following to ensure that a group will perform correctly:

• Checks all resources in a group and confirms that they have been configured correctly on all nodes that are possible owners for the group.

• Updates the dependencies among resources in the group.

• After prompting you, repairs a group that is misconfigured.

You can run the Verify Group operation at any time. However, you should run it when any of the following occurs:

• A group or resource in a group does not come online.

• Failover or failback do not perform as you expected.

• You add a node to the cluster.

You can verify a group by selecting the group from the Oracle Fail Safe Manager tree view and then choosing:

Troubleshooting -> Verify Group

Or, you can run a Verify Group operation using the FSCMD command VERIFYGROUP (see Chapter 5). The FSCMD command also provides a VERIFYALLGROUPS command that allows you to verify all groups configured by Oracle Fail Safe on a given cluster. You can run the VERIFYGROUP and VERIFYALLGROUPS commands in scripts as batch jobs.

You can watch the progress of the Verify Group operation and view the status of the individual resources in the group as Oracle Fail Safe verifies the group.

Figure 6-3 shows the output from a Verify Group operation.

Description of the illustration cwo_vg.gif

6.1.3 Verify Standalone Database

You can validate a standalone database at any time using the Verify Standalone Database operation. To issue the Verify Standalone Database command, select the database from the Oracle Fail Safe Manager tree view, and then choose:

Troubleshooting -> Verify Standalone Database

The Verify Standalone Database operation performs validation checks to ensure that the standalone database is configured correctly on the node where it resides and to remove any references to the database that might exist on other cluster nodes. (References to the database might exist on other cluster nodes if the database was once added to a group and then later removed.) This ensures that the database can be made highly available using Oracle Fail Safe.

Oracle Corporation recommends that you use the Verify Standalone Database command on a standalone database before you add it to a group. You can also use it whenever you have trouble accessing a standalone database. However, note that Oracle Fail Safe stops and restarts the database during the verify operation.

For example, you might perform a verification:

• In response to a failure when you try to add a database to a group.

• If you used an administrator tool other than Oracle Fail Safe Manager to perform an operation on the database and the database now is inaccessible.

• If you removed or deinstalled the MSCS software from the cluster nodes without first removing the Oracle Fail Safe software (for example, during a software upgrade). This is described in more detail in the Oracle Fail Safe Installation Guide.

Figure 6-4 shows the Verify Standalone Database dialog box in which you enter valid database information and account information for a standalone database.

Description of the illustration ofsman_verifystandalone.gif

To use the Verify Standalone Database dialog box, you specify:

• The service name of the standalone database, in the Service Name field

• The instance name of the standalone database, in the Instance Name field

• The database name of the standalone database, in the Database Name field

• The parameter file disk, path name, and file name for the initialization parameter file for the standalone database, in the Parameter File field

• The account that Oracle Fail Safe should use to attach to the database, in the Account area.

Oracle Fail Safe uses this information to:

• Fix clusterwide problems with Oracle Net

• Check that the standalone database is on a cluster disk

• Make sure that Oracle Fail Safe can attach to the database

If a standalone database is open and you run a Verify Standalone Database operation, the operation does not restart the database.

If a standalone database is not open or if the database is stopped, Oracle Fail Safe will ask your permission to stop and restart the database instance. Subsequently, Oracle Fail Safe will open the database for access.

Figure 6-5 shows the output from a typical Verify Standalone Database operation in a Clusterwide Operation window.

Description of the illustration cwo_verifystandalonedb.gif

If any problems are found during verification, the Verify Standalone Database operation prompts you before it attempts to fix them. For example, imagine that you try to add a database to a group, but the operation fails because of an Oracle Net problem. You can run the Verify Standalone Database command to fix the network problem and subsequently add the database to a group.