JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle SuperCluster M6-32

Owner's Guide: Administration

search filter icon
search icon

Document Information

Using This Documentation

Product Documentation Library

Feedback

Understanding SuperCluster Software

Identify the Version of SuperCluster Software

SuperCluster Tools

Controlling SuperCluster M6-32

Cautions

Power On SuperCluster M6-32

Powering Off SuperCluster M6-32 Gracefully

Shut Down the Oracle Solaris Cluster

Shut Down the Enterprise Controller (Ops Center)

Shut Down the Database

Shut Down the Storage Servers

Power Off the Storage Servers

Shut Down the LDoms

Shut Down the OS on the Compute Servers

Shut Down the ZFS Storage Appliance

Power Off the Switches and Racks

Power Off SuperCluster M6-32 in an Emergency

Monitoring SuperCluster M6-32 (OCM)

OCM Overview

Access OCM Documentation

Monitoring the System With ASR

ASR Overview

ASR Resources

ASR Installation Overview

Configure ASR on the Compute Servers (Oracle ILOM)

Configure SNMP Trap Destinations for Storage Servers

Configure ASR on the ZFS Storage Appliance

Configuring ASR on the Compute Servers (Oracle Solaris 11)

Enable the HTTP Receiver on the ASR Manager

Enable HTTPS on ASR Manager (Optional)

Register Compute Servers With Oracle Solaris 11 or Database Domains to ASR Manager

Approve and Verify ASR Asset Activation

Tuning SuperCluster M6-32

ssctuner Overview

Monitor ssctuner Activity

View Log Files

Change ssctuner Properties and Disable Features

Install ssctuner

Enable ssctuner

Configuring CPU and Memory Resources (osc-setcoremem)

osc-setcoremem Overview

Minimum and Maximum Resources (Dedicated Domains)

Supported Domain Configurations

Plan CPU and Memory Allocations

Display the Current Domain Configuration (osc-setcoremem)

Display the Current Domain Configuration (ldm)

Change CPU/Memory Allocations (Socket Granularity)

Change CPU/Memory Allocations (Core Granularity)

Park Cores and Memory

Access osc-setcoremem Log Files

View the SP Configuration

Revert to a Previous CPU/Memory Configuration

Remove a CPU/Memory Configuration

Obtaining the EM Exadata Plug-in

Confirm System Requirements

Known Issues With the EM Exadata Plug-in

Configuring the Exalogic Software

Exalogic Software Overview

Prepare to Configure the Exalogic Software

Enable Domain-Level Enhancements

Enable Cluster-Level Session Replication Enhancements

Configuring Grid Link Data Source for Dept1_Cluster1

Fast Connection Failover

Runtime Connection Load Balancing

XA Affinity

SCAN Addresses

Secure Communication With Oracle Wallet

Create a Grid Link Data Source on Dept1_Cluster1

Configuring SDP-Enabled JDBC Drivers for Dept1_Cluster1

Configure the Database to Support IB

Enable SDP Support for JDBC

Monitor SDP Sockets

Create an SDP Listener on the IB Network

Administering Oracle Solaris 11 Boot Environments

Advantages to Maintaining Multiple Boot Environments

Create a Boot Environment

Mount to a Different Build Environment

Reboot to the Original Boot Environment

Create a Snapshot of a Boot Environment

Remove Unwanted Boot Environments

Administering DISM

DISM Restrictions

Disable DISM

Administering Storage Servers

Monitor Write-through Caching Mode

Shut Down or Reboot a Storage Server

Drop a Storage Server

Glossary

Index

Change ssctuner Properties and Disable Features


Caution

Caution - Do not perform this procedure without Oracle Support approval. Changing properties or disabling ssctuner features can have unpredictable consequences.


Changing certain ssctuner properties such as EMAIL_ADDRESS and disk or memory usage warning levels might be advantageous in some environments.

  1. List the ssctuner properties to identify the property you want to change.
    # svccfg -s ssctuner listprop 'ssctuner_vars/*'
    ssctuner_vars/CRIT_THREADS_FIX          boolean     true
    ssctuner_vars/CRIT_THREADS_NONEXA       boolean     false
    ssctuner_vars/DISK_SPACE_CHECK          boolean     true
    ssctuner_vars/DISK_USAGE_CRIT           integer     90
    ssctuner_vars/DISK_USAGE_WARN           integer     85
    ssctuner_vars/DISM_CHECK                boolean     true
    ssctuner_vars/EMAIL_ADDRESS             astring     root@localhost
    ssctuner_vars/EMAIL_MESSAGES            boolean     true
    ssctuner_vars/FORCELOAD_VDC             boolean     false
    ssctuner_vars/INTRD_DISABLE             boolean     true
    ssctuner_vars/ISCSI_TUNE                boolean     true
    ssctuner_vars/MAJOR_INTERVAL            integer     120
    ssctuner_vars/MEM_USAGE_CRIT            integer     97
    ssctuner_vars/MEM_USAGE_WARN            integer     94
    ssctuner_vars/MINOR_INTERVAL            integer     2
    ssctuner_vars/NDD_TUNE                  boolean     true
    ssctuner_vars/NFS_CHECK                 boolean     true
    ssctuner_vars/NFS_EXCLUDE               astring
    ssctuner_vars/NFS_INCLUDE               astring
    ssctuner_vars/NTPCONF_TUNE              boolean     true
    ssctuner_vars/POWERADM_DISABLE          boolean     true
    ssctuner_vars/SDCONF_TUNE               boolean     true
    ssctuner_vars/SERD_THRESHOLD_TUNE       boolean     true
    ssctuner_vars/SSDCONF_TUNE              boolean     true
    ssctuner_vars/SYSLOG_DUP_SUPPRESS_HOURS integer     8
    ssctuner_vars/SYSTEM_TUNE               boolean     true
    ssctuner_vars/ZPOOL_FIX                 boolean     true
    ssctuner_vars/ZPOOL_NAME_CUST           astring 
  2. Use the svccfg command to change property settings.

    These are examples of properties you might need to change:

    • Configure the system so that critical messages are sent to your email address.

      ~# svccfg -s ssctuner setprop ssctuner_vars/EMAIL_ADDRESS="my_name@mycorp.com"
    • Change the disk (/ and zone roots) usage warning level to 80%.

      ~# svccfg -s ssctuner setprop ssctuner_vars/DISK_USAGE_WARN=80
    • Enable thread priority changing for non-exa Oracle DB domains:.

      ~# svccfg -s ssctuner setprop ssctuner_vars/CRIT_THREADS_NONEXA=true
    • Enable zpool check and repair of vdisk zpools that are not generated by the SuperCluster installer.

      ~# svccfg -s ssctuner setprop ssctuner_vars/ZPOOL_NAME_CUST=my_vdisk_pool
    • Exclude NFS mounts from warning mechanisms.

      ~# svccfg -s ssctuner setprop ssctuner_vars/NFS_EXCLUDE='mount_name_or_device'
    • Include NFS mounts in warning mechanism (overrides exclude).

      ~# svccfg -s ssctuner setprop ssctuner_vars/NFS_INCLUDE='mount_name_or_device'
    • Disable all NFS mount warnings (not recommended).

      ~# svccfg -s ssctuner setprop ssctuner_vars/NFS_CHECK=false

    The NFS_EXCLUDE, NFS_INCLUDE and ZPOOL_NAME_CUST properties must be simple strings but you can use simple regular expressions.

    If you need the flexibility of regular expressions, be extremely careful to double quote the expressions. Also verify that the ssctuner service comes back after restarting and no errors are in the SMF log file.

  3. Restart the SMF service for changes to take effect.
    # svcadm restart ssctuner
  4. Ensure that the ssctuner service is enabled and no error messages are reported.

    If you changed a property using an incorrect syntax, the service does not come back. If this happens, identify the offending property that you must fix:

    # grep -i parameter /var/svc/log/site-application-sysadmin-ssctuner:default.log

    After making any corrections or changes, repeat Step 3.

Related Information