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

Create a Grid Link Data Source on Dept1_Cluster1

Create a grid link data source for each of the Oracle database instances during the process of setting up the multidata source, both for these data sources and the global leasing multidata source.

  1. Prepare to create the data source.
    1. Ensure that this is a non-xa data source.
    2. Target these data sources to the Dept1_Cluster1 cluster.
    3. Set the data sources connection pool initial capacity to 0.
      1. In the Oracle WebLogic Server Administration Console, select Services, JDBC, and then Datasources.
      2. In the Datasources screen, click the Datasource Name, then click the Connection Pool tab, and enter 0 in the Initial capacity field.
    4. Ensure that an ONS daemon is running on your database servers at all times. Start the ONS daemon on a database server by running the onsctl command:

      start

  2. Log in to the Oracle WebLogic Server Administration Console.
  3. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit.
  4. In the Domain Structure tree, expand Services, then select Data Sources.
  5. On the Summary of Data Sources page, click New and select GridLink Data Source.

    The Create a New JDBC GridLink Data Source page is displayed.

  6. Enter the following information, then click Next.
    • Logical name for the datasource in the Name field. For example, gridlink.

    • Name for JNDI. For example, jdbc/gridlink.

  7. In the Transaction Options page, deselect Supports Global Transactions, and click Next.
  8. Select Enter individual listener information and click Next.
  9. Enter the following connection properties:
    • Service Name: Enter the name of the RAC service in the Service Name field. For example, enter myService in Service Name.


      Note - The Oracle RAC Service name is defined on the database, and it is not a fixed name.


    • Host Name: Enter the DNS name or IP address of the server that hosts the database. For an Oracle GridLink service-instance connection, this must be the same for each data source in a given multi data source.

    • Port: Enter the port on which the database server listens for connections requests.

    • Database User Name: Enter the database user name. For example, myDataBase.

    • Password: Enter the password. For example, myPassword1.

      Confirm password and click Next.


    Tip - For more information, refer to the Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help.


    The console automatically generates the complete JDBC URL. For example:

    jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=left)(PORT=1234))(ADDRESS=(PROTOCOL=TCP)(HOST=right)(PORT=1234))(ADDRESS=(PROTOCOL=TCP)(HOST=center)(PORT=1234)))(CONNECT_DATA=(SERVICE_NAME=myService)))

  10. On the Test GridLink Database Connection page, review the connection parameters and click Test All Listeners.

    Oracle WebLogic attempts to create a connection from the administration server to the database. Results from the connection test are displayed at the top of the page. If the test is unsuccessful, you should correct any configuration errors and retry the test.

    Click Next.

  11. In the ONS Client Configuration page, do the following:
    1. Select Fan Enabled to subscribe to and process FAN events.
    2. In the ONS host and port fields, enter a comma-separated list of ONS daemon listen addresses and ports for receiving ONS-based FAN events.

      You can use SCAN addresses to access FAN notifications.

    3. Click Next.
  12. On the Test ONS Client Configuration page, review the connection parameters and click Test All ONS Nodes.

    Click Next.

  13. In the Select Targets page, select Dept1_Cluster1 as the target and All Servers in the cluster.
  14. Click Finish.
  15. Click Activate Changes.
  16. Configure SDP-enabled JDBC drivers for the cluster.

    For instructions, see Configuring SDP-Enabled JDBC Drivers for Dept1_Cluster1.