test

Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS

Common Problems and Their Solutions

The subsections that follow describe problems that can affect Sun Cluster Support for Oracle Real Application Clusters. Each subsection provides information about the cause of the problem and a solution to the problem.

Node Panic During Initialization of Sun Cluster Support for Oracle Real Application Clusters

If a fatal problem occurs during the initialization of Sun Cluster Support for Oracle Real Application Clusters, the node panics with an error message similar to the following error message:


panic[cpu0]/thread=40037e60: Failfast: Aborting because "ucmmd" died 30 seconds ago

Description:

To determine the cause of the problem, examine the system messages file. The most common causes of this problem are as follows:

  • The license for VERITAS Volume Manager (VxVM) is missing or has expired.

  • The ORCLudlm package that contains the Oracle UDLM is not installed.

  • The amount of shared memory is insufficient to enable the Oracle UDLM to start.

  • The version of the Oracle UDLM is incompatible with the version of Sun Cluster Support for Oracle Real Application Clusters.

For instructions to correct the problem, see How to Recover From a Node Panic During Initialization.

A node might also panic during the initialization of Sun Cluster Support for Oracle Real Application Clusters because a reconfiguration step has timed out. For more information, see Node Panic Caused by a Timeout.

ProcedureHow to Recover From a Node Panic During Initialization

Steps

  1. Boot into maintenance mode the node that panicked.

    For more information, see Sun Cluster System Administration Guide for Solaris OS.

  2. Verify that you have correctly installed your volume manager packages.

    If you are using VxVM, check that you have installed the software and check that the license for the VxVM cluster feature is valid.

  3. Ensure that you have completed all the procedures that precede installing and configuring the Oracle UDLM software.

    The procedures that you must complete are listed in Table 1–1.

  4. Ensure that the Oracle UDLM software is correctly installed and configured.

    For more information, see SPARC: Installing the Oracle UDLM.

  5. Reboot the node that panicked.

    For more information, see Sun Cluster System Administration Guide for Solaris OS.

Node Panic Caused by a Timeout

The timing out of any step in the reconfiguration of Sun Cluster Support for Oracle Real Application Clusters causes the node on which the timeout occurred to panic.

To prevent reconfiguration steps from timing out, tune the timeouts that depend on your cluster configuration. For more information, see Guidelines for Setting Timeouts.

If a reconfiguration step times out, use the scrgadm utility to increase the value of the extension property that specifies the timeout for the step. For more information, see Appendix A, Sun Cluster Support for Oracle Real Application Clusters Extension Properties.

After you have increased the value of the extension property, reboot the node that panicked.

Failure of a Node

Recovering from the failure of a node involves the following tasks:

  1. Booting into maintenance mode the node that panicked

  2. Performing the appropriate recovery action for the cause of the problem

  3. Rebooting the node that panicked

For more information, see Sun Cluster System Administration Guide for Solaris OS.

Note –

In an Oracle Real Application Clusters environment, multiple Oracle instances cooperate to provide access to the same shared database. The Oracle clients can use any of the instances to access the database. Thus, if one or more instances have failed, clients can connect to a surviving instance and continue to access the database.

Failure of the ucmmd Daemon to Start

The UCMM daemon, ucmmd, manages the reconfiguration of Sun Cluster Support for Oracle Real Application Clusters. When a cluster is booted or rebooted, this daemon is started only after all components of Sun Cluster Support for Oracle Real Application Clusters are validated. If the validation of a component on a node fails, the ucmmd fails to start on the node.

To determine the cause of the problem, examine the following files:

The most common causes of this problem are as follows:

To correct the problem, perform the appropriate recovery action for the cause of the problem and reboot the node on which ucmmd failed to start.

Failure of a SUNW.rac_framework Resource to Start

If a SUNW.rac_framework resource fails to start, verify the status of the resource to determine the cause of the failure. For more information, see How to Verify the Status of Sun Cluster Support for Oracle Real Application Clusters.

The state of a resource that failed to start is shown as Start failed. The associated status message indicates the cause of the failure to start as follows:


Faulted - ucmmd is not running

Description:

The ucmmd daemon is not running on the node where the resource resides. For information about how to correct this problem, see Failure of the ucmmd Daemon to Start.


Degraded - reconfiguration in progress

Description:

A configuration error occurred in one or more components of Sun Cluster Support for Oracle Real Application Clusters.

To determine the cause of the configuration error, examine the following files:

  • The UCMM reconfiguration log file /var/cluster/ucmm/ucmm_reconf.log

  • The system messages file

For more information about error messages that might indicate the cause of the configuration error, see Sun Cluster Error Messages Guide for Solaris OS.

To correct the problem, correct the configuration error that caused the problem. Then reboot the node on which the erroneous component resides.


Online

Description:

Reconfiguration of Oracle Real Application Clusters was not completed until after the START method of the SUNW.rac_framework resource timed out.

For instructions to correct the problem, see How to Recover From the Timing Out of the START Method.

ProcedureHow to Recover From the Timing Out of the START Method

Steps

  1. Become superuser.

  2. On the node where the START method timed out, take offline the RAC framework resource group.

    To perform this operation, switch the primary nodes of the resource group to the other nodes where this group is online.


    # scswitch -z -g resource-group -h nodelist
    -g resource-group

    Specifies the name of the RAC framework resource group. If this resource group was created by using the scsetup utility, the name of the resource group is rac-framework-rg.

    -h nodelist

    Specifies a comma-separated list of other cluster nodes on which resource-group is online. Omit from this list the node where the START method timed out.

  3. On all cluster nodes that can run Sun Cluster Support for Oracle Real Application Clusters, bring the RAC framework resource group online.


    # scswitch -Z -g resource-group
    -Z

    Enables the resource and monitor, moves the resource group to the MANAGED state, and brings the resource group online

    -g resource-group

    Specifies that the resource group that you brought offline in Step 2 is to be moved to the MANAGED state and brought online

Failure of a Resource to Stop

If a resource fails to stop, correct this problem as explained in Clearing the STOP_FAILED Error Flag on Resources in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.