JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Service for Oracle Grid Engine Guide
search filter icon
search icon

Document Information

Preface

1.  Installing and Configuring HA for Oracle Grid Engine

HA for Oracle Grid Engine Overview

Overview of Installing and Configuring HA for Oracle Grid Engine

Planning the HA for Oracle Grid Engine Installation and Configuration

Configuration Restrictions

Oracle Grid Engine Shadow Daemon

Oracle Grid Engine Berkley DB spooling server

Start at Boot Option

Configuration Requirements

Oracle Grid Engine Software Version Requirements

Operating System for the Oracle Grid Engine Management Tier

Memory Requirements

Disk Space Requirements

HA for Oracle Grid Engine Configuration Requirements

NFS Configuration for the Oracle Grid Engine File System

Oracle Solaris Cluster HA for NFS Configuration Requirements

Dependencies Between Oracle Grid Engine Components

Configuration Considerations

Location of the Oracle Grid Engine Binary Files

File Systems for Spool Directories and Binary Files

Configuration Planning Questions

Preparing the Nodes and Disks

How to Prepare the Nodes and Disks

Installing and Configuring Oracle Grid Engine

How to Install and Configure Oracle Grid Engine

How to Enable Oracle Grid Engine to Run in a Cluster

Verifying the Installation and Configuration of Oracle Grid Engine

How to Verify the Installation and Configuration of Oracle Grid Engine

Installing the HA for Oracle Grid Engine Packages

How to Install the HA for Oracle Grid Engine Packages

Configuring the HAStoragePlus Resource Type to Work With HA for Oracle Grid Engine

How to Register and Configure an HAStoragePlus Resource

Configuring Oracle Solaris Cluster HA for NFS for Use With HA for Oracle Grid Engine

How to Configure Oracle Solaris Cluster HA for NFS for Use With HA for Oracle Grid Engine

Registering and Configuring HA for Oracle Grid Engine

Specifying Configuration Parameters for HA for Oracle Grid Engine Resources

How to Create and Enable HA for Oracle Grid Engine Resources

Setting HA for Oracle Grid Engine Extension Properties

Verifying the HA for Oracle Grid Engine Installation and Configuration

How to Verify the HA for Oracle Grid Engine Installation and Configuration

Tuning the HA for Oracle Grid Engine Fault Monitors

Debugging HA for Oracle Grid Engine

How to Activate Debugging for HA for Oracle Grid Engine

A.  Files for Configuring and Removing HA for Oracle Grid Engine Resources

Index

Debugging HA for Oracle Grid Engine

The config file in the /opt/SUNWscsge/etc directory enables you to activate debugging for Oracle Grid Engine resources. This file enables you to activate debugging for all Oracle Grid Engine resources or for a specific Oracle Grid Engine resource on a particular node. If you require debugging for HA for Oracle Grid Engine to be enabled throughout the cluster, repeat this procedure on all nodes.

How to Activate Debugging for HA for Oracle Grid Engine

  1. Determine whether debugging for HA for Oracle Grid Engine is active.

    If debugging is inactive, daemon.notice is set in the file /etc/syslog.conf.

    # grep daemon /etc/syslog.conf
    *.err;kern.debug;daemon.notice;mail.crit        /var/adm/messages
    *.alert;kern.err;daemon.err                     operator
    #
  2. If debugging is inactive, edit the /etc/syslog.conf file to change daemon.notice to daemon.debug.
  3. Confirm that debugging for HA for Oracle Grid Engine is active.

    If debugging is active, daemon.debug is set in the file /etc/syslog.conf.

    # grep daemon /etc/syslog.conf
    *.err;kern.debug;daemon.debug;mail.crit        /var/adm/messages
    *.alert;kern.err;daemon.err                    operator
    #
  4. Restart the syslogd daemon.
    # svcadm restart system-log
  5. Edit the /opt/SUNWscsge/etc/config file to change DEBUG= to DEBUG=ALL or DEBUG=sge-rs.
    # cat /opt/SUNWscsge/etc/config
    #
    # Copyright 2006 Sun Microsystems, Inc.  All rights reserved.
    # Use is subject to license terms.
    #
    # ident "@(#)config     1.1     06/02/18 SMI"
    #
    # Usage:
    #       DEBUG=<RESOURCE_NAME> or ALL
    #
    DEBUG=ALL
    #

    Note - To deactivate debugging, reverse the preceding steps.