Installing and Configuring Sun Cluster For Oracl 10g HA

Installing and Configuring
Sun™ Cluster 3.1 Software

for Oracle® Database 10g HA
Iris Zhu
May 2008
Sun Microsystems, Inc.
Copyright © 2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights
reserved.
U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc.
standard license agreement and applicable provisions of the FAR and its supplements. Use is subject to license terms.
This distribution may include materials developed by third parties.
Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is
a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.
X/Open is a registered trademark of X/Open Company, Ltd.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International,
Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture
developed by Sun Microsystems, Inc.
ORACLE is a registered trademark of Oracle Corporation.
Sun, Sun Microsystems, the Sun logo, Java, Solaris, Solstice DiskSuite, Sun BluePrints, Sun Cluster, Sun Fire,
SunPlex, and Sun StorEdge are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other
countries.
This product is covered and controlled by U.S. Export Control laws and may be subject to the export or import laws
in other countries. Nuclear, missile, chemical biological weapons or nuclear maritime end uses or end users, whether
direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities
identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated
nationals lists is strictly prohibited.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,

REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE
EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Installing and Configuring Sun Cluster 3.1 Software for Oracle Database 10g HA 2
Table of Contents
Introduction................................................................................................................................................4
Background................................................................................................................................................4
What Is a Cluster?.................................................................................................................................4
What Is a High Availability Cluster?....................................................................................................4
What Can Sun Cluster Software Do for HA Applications?..................................................................4
Physical Connections............................................................................................................................6
Cluster Node.....................................................................................................................................7
Cluster Interconnect..........................................................................................................................7
Public Network Interfaces................................................................................................................8
Multihost Devices.............................................................................................................................8
Key Concepts........................................................................................................................................8
Global Devices, Global Namespaces, and Cluster File System.......................................................8
Quorum and Quorum Device............................................................................................................9
Data Service....................................................................................................................................10
Resource, Resource Types, and Resource Groups.........................................................................10
Cluster Topologies..............................................................................................................................11
Installation and Configuration.................................................................................................................11
Installing the Solaris 10 OS for SPARC Platforms.............................................................................12
Configuring Sun StorEdge 3510 FC Array.........................................................................................13
Installing Sun Cluster 3.1 08/05 Software...........................................................................................14
Installing Sun Cluster HA Agent for Oracle Database 10g HA..........................................................14
Installing Oracle Database 10g HA.....................................................................................................15
Configuring Sun Cluster 3.1 08/05 Software......................................................................................15
Verifying Sun Cluster 3.1 08/05 Software..........................................................................................17
Summary..................................................................................................................................................17
Appendix..................................................................................................................................................17
For More Information..............................................................................................................................19
Introduction
This article is for those who have no experience with Sun™ Cluster software. After introducing some
basic concepts, this article provides a demonstration of how to set up Sun Cluster 3.1 08/05 software
(hereafter called Sun Cluster software) for Oracle® Database 10g HA with the Solaris™ 10 01/06
Operating System.
The procedures in this article were tested on the Solaris 10 1/06 release. However, the concepts in this
article should also work with the Solaris 10 5/08 OS, because the procedures use general functionality
of the OS.
Background
To understand the installation and configuration steps, you need to have some basic knowledge about
Sun Cluster software. This section provides some basic concepts. For more information, refer to the
Sun Cluster Concepts Guide for Solaris OS (http://docs.sun.com/app/docs/doc/819-0421) and
the Sun Cluster Overview for Solaris OS (http://docs.sun.com/app/docs/doc/819-0579).
What Is a Cluster?
A cluster is two or more systems or nodes that work together as a single, continuously available system
to provide applications, system resources, and data to users.
What Is a High Availability Cluster?

There are different types of cluster architectures:
• High-availability (HA) clusters
• High-performance computing clusters
• Grid computing
• Server farms
An HA cluster provides a computing environment that offers high levels of uptime. To understand
more about the other types of clusters, refer to the book SUN Cluster 3 Programming: Integrating
Applications into the SunPlex™ Environment by Joseph Bianco, Peter Lees, and Kevin Rabito (see
http://www.amazon.com/gp/product/0130479756/104-0560062-1750305?v=glance&n=283155).
What Can Sun Cluster Software Do for HA Applications?

With Sun Cluster software, a computing environment is available with redundancy at one or more
levels of the system stack, for example, the computer server, the database, the application, the
transaction broker, the file services, and so forth.
The computing environment is able to detect, isolate, and recover from a system (cluster node) failure
while continuing to provide application services. Of course, it maintains the highest levels of data
integrity at the same time.
The next section describes how to enable Oracle10g to be the HA application within the cluster
environment. A cluster environment named oraclecluster is set up with the following features:
• Oracle services can run only on one server.

• Only one instance of the Oracle database is active on the cluster.
• Oracle uses the global and failover file systems.
• Oracle services are temporarily unavailable until failover is complete.
• End users connect to a logical IP address to access the service.
• If necessary, users must reconnect to the service.
• Oracle services can be restarted or migrated to another node.
Physical Connections
Figure 1 shows a two-node cluster environment that has the following features:
• Two cluster nodes with local disks (unshared) provide the main computing platform of the
cluster.
• The cluster interconnect provides a channel for internode communication.
• Multihost storage provides disks that are shared between the nodes.
• The console access device enables access to the cluster environment from the administrative
console. Usually, the console access device is special hardware called a Terminal Concentrator,
which provides access to a headless cluster for hosted systems.
• The administrative console enables administration of the cluster environment. Sun workstations
on which this cluster administration tool is installed can monitor any cluster.
• The public network interfaces (multipathing group) provide the failover for the interfaces on
each node to connect with the public network.
• Client systems include workstations or other servers that access the cluster over the public
network.
Figure 1: Cluster Hardware Components
The cluster environment oraclecluster is set up according to Figure 1, so it is very important to

understand each component clearly.
Cluster Node
A cluster node is a machine that runs both the Solaris OS and Sun Cluster software. The Sun Cluster
3.1 08/05 software enables you to have from 2 to 16 nodes in a cluster. Each node has similar
processing, memory, and I/O capability to enable failover to occur without significant degradation in
performance.
oraclecluster has two Sun FireTM V480 servers with the same specification acting as the two
cluster nodes. The Solaris 10 01/06 OS, Sun Cluster 3.1 08/05 software, Sun Cluster HA for Oracle,
and Oracle Database 10g HA application are installed on each.
Cluster Interconnect
The cluster interconnect, shown in Figure 2, is the physical configuration of devices that are used to
transfer cluster-private communications and data service communications between cluster nodes. The
cluster interconnect is used to detect communication, repair communication, and automatically re-
initiate communication after communication is repaired.
Figure 2: Cluster Interconnect
There are three necessary components for the cluster interconnect:

• Adapters
• Junctions
• Cables
In the two-node cluster oraclecluster, the two Sun Fire V480 servers are connected directly by
cables between one pair of physical interfaces. Node configurations with more than two nodes
generally require junctions.
Public Network Interfaces

Clients connect to the cluster through the public network interfaces. Each cluster node is connected to
one or more public networks with at least one or more network adapters. With multiple public network
interface cards (NICs) organized into IP multipathing groups (IPMP), when one of the adapters fails,
Internet Protocol (IP) Network Multipathing software failovers the defective interface to another
adapter in the group. For more about IPMP, refer to System Administration Guide: IP Services
(http://docs.sun.com/app/docs/doc/816-4554).
Multihost Devices
Disks that can be connected to more than one node at a time are called multihost devices. Multihost
storage makes disks highly available. Sun Cluster software requires multihost storage for two-node
clusters to establish a quorum. Clusters with more than two nodes do not require quorum devices.
In oraclecluster, there are only three NICs on each node, and a Sun StorEdgeTM 3510 FC array is
used as multihost device. Two NICs are used for interconnection between the two Sun Fire V480
servers, and one is used to connect to the public network. If you have two or more NICs connecting to
the public network, refer to System Administration Guide: IP Services
Key Concepts
Whenever a Sun Cluster environment is mentioned, there are some other important concepts you might
encounter.
Global Devices, Global Namespaces, and Cluster File System

Sun Cluster systems use global devices to provide cluster-wide, highly available access to any device in
a cluster, from any node, without regard to where the device is physically attached. Disks are the only
multiported device that Sun Cluster software supports. In general, if a node fails while providing access
to a global device, the Sun Cluster software automatically discovers another path to the device and
redirects the access to that path.
The Sun Cluster software mechanism that enables global devices is global namespaces, which provides
multiple failover paths to the multihost disks. Each node that is physically connected to multihost disks
provides a path to the storage for any node in the cluster. In the Sun Cluster system, each device node
in the local volume manager namespace is replaced by a symbolic link to a device node in the
/global/.devices/node@nodeID file system, where nodeID is an integer that represents a
node in the cluster.
After you install Sun Cluster software successfully, you see the difference simply by using the mount
command. For example, one raw disk in a Sun StorEdge FC 3510 FC array is described as follows in
/etc/vfstab:
/dev/did/dsk/d2s3 /dev/did/rdsk/d2s3 /global/.device/node@1 ufs 2 no global
The cluster file system enables the same path to locate a file, no matter where it is in the cluster, and is
dependent on global devices. The cluster file system on a global device can be created by using the
newfs or mkfs commands.
For cluster oraclecluster, raw disks in Sun StorEdge 3510 FC array are configured to RAID-5
and used as the global device, which offers better availability over volume manager-based
configurations and the least overhead.
Quorum and Quorum Device

Because cluster nodes share data and resources, a cluster shouldn't be split into separate partitions that
are active at the same time, because doing so might cause data corruption. Sun Cluster software avoids
problems by:
• Assigning each node one vote
• Mandating a majority of votes for an operational cluster
In other words, a cluster can run only if a partition has the majority of votes. The majority number is
quorum. For example, in a six-node cluster, at least four (yes, four is the quorum for this cluster) nodes
should keep healthy providing service, and for a five-node cluster, at least three nodes are required.
In a two-node cluster, a majority is two, so how do you enable the healthy node to gain quorum? In this
case, an external vote by a quorum device is needed, as shown in Figure 3. A quorum device is a disk
shared by two or more nodes that contributes votes that are used to establish a quorum for the cluster to
run.
Quorum devices acquire quorum vote counts based on the number of node connections to the device.
Quorum devices acquire a maximum vote count of N-1, where N is the number of connected votes to
the quorum device.
The Sun StorEdge 3510 FC array is used as the quorum device for the two-node cluster
oraclecluster, which has a quorum count of one (two minus one). If interconnection between
node A and node B fails, only the node that can get the vote from the Sun StorEdge 3510 FC Array
forms a new cluster to keep running.
Figure 3: Quorum Device for Two-Node Cluster
Data Service
The term data service describes an application that has been configured to run on a cluster rather than
on a single server. Sun Cluster software manages the application with the following actions:
• Start
• Stop
• Monitor and take corrective measures
Figure 4 shows an application that runs on a single application server and the same application running
on a cluster. The latter is more highly available because whenever one instance fails, the other keeps
providing service.
Figure 4: Standard Versus Clustered Client-Server Configuration
In this document, Oracle10g is configured into cluster oraclecluster, so failover between two
independent instances on each Sun Fire V480 server is executed.
Resource, Resource Types, and Resource Groups

All the services configured to be managed within a Sun Cluster framework are called the data service.
The data service uses several resource types. Applications, such as Sun JavaTM System Web Server, use
network addresses on which the applications depend. A resource is an instantiation of a resource type
that is defined cluster-wide. Several types are defined. Resources are placed into resource groups, so
they can be managed as a unit. A resource group is migrated as a unit if a failover or switchover is
initiated on the resource group.
In cluster oraclecluster, you manage the following resources in the resource group
clustergroup:
• SUNW.oracle_server, for Oracle Server, is preregistered in the Sun Cluster software.
• SUNW.oracle_listener, for Oracle Listener, is preregistered in the Sun Cluster software.
• SUNW.HAStoragePlus, for failover of the cluster file system and to make the network
resource start up first, is also preregistered in the Sun Cluster software.
How about the necessary network resource? It is associated with a logical host name
(oracleserver). When one of the Sun Fire V480 servers fails, all the resources in the resource
group clustergroup migrate to the other node.
Cluster Topologies
A topology is the connection schema that connects the cluster nodes to the storage platforms that are
used in a Sun Cluster environment.
Since you can access the two nodes by connecting to the serial port or by using telnet from other
systems that have a screen, the topology shown in Figure 5, which is much simpler than the topology
in Figure 1 and contains only the core components (without the Administrative Console and the
console access device), is used for your first experience. However, in an actual deployment, you should
have all the components to simplify management.
Figure 5 is the topology used for oraclecluster, with two nodes that can be operated under a
single cluster administrative framework.
Figure 5: Topology for Cluster oraclecluster
Installation and Configuration

With basic knowledge from the concepts presented previously, you are ready to start installing and
configuring the Sun Cluster 3.1 08/05 software and other software listed in Table 1.
Table 1: Software Installed
Service
Hardware Software
Module
Sun Fire V480 ● Solaris 10 01/06 OS for SPARC® platforms
server ● Sun Cluster 3.1 08/05 software (SPARC)
Database
● Oracle Database 10g Release 2 (10.2.0.1.0) for Solaris
Server Sun Fire V480 Operating System (SPARC) (64-bit)
server ● Sun Cluster HA for Oracle (SPARC)
Sun StorEdge
Storage N/A
3510 FC array
● Solaris 10 01/06 OS for x86 platforms
Test Client Fujitsu LifeBook ● Oracle Database 10g Client Release 1 (10.1.0.3) for
Solaris Operating System (x86)
Installing the Solaris 10 OS for SPARC Platforms

Step 1: Install.
The Solaris 10 01/06 OS for SPARC platforms is installed on each node. To meet the Sun Cluster
software's needs, use the file-system allocation shown in Table 2 on each Sun Fire V480 server.
Table 2: Example File-System Allocation

Slice Contents Size Description
Allocation
0 / (according to This is used for the Solaris OS, Sun Cluster software, data-
your services software, Sun Cluster module agent packages, root file
demand) system, and database and application software.
1 swap 1024Mbytes 512 Mbytes is for the Solaris OS and 512 Mbytes is for the Sun
Cluster software.
2 /globaldevices 512Mbytes The Sun Cluster software later assigns this slice a different
mount point and mounts the slice as a cluster file system.
3 overlap (according to This is the entire disk.

the disk
capacity)
Step 2: Configure the IP address for each node.
Besides assigning IP addresses for the nodes as usual, a logical host name is necessary for the cluster.
Become superuser and confirm the host name determination order in the file
/etc/nsswitch.conf:
# vi /etc/nsswitch.conf
...
hosts: cluster files
...
Add the logical host name:

# vi /etc/hosts
127.0.0.1 localhost
#master node host name and IP
10.0.100.32 v480-1 loghost
#standby node host name and IP
10.0.100.33 v480-2
#logical host name and IP
10.0.100.1 oracleserver
For more information, refer to the Sun Cluster Software Installation Guide for Solaris OS
Step 3: Connect the machines according to the topology.

Three NICs are installed on each node. Two of them are used to interconnect and the rest are used for
connecting to the public network.
Connect the physical interfaces, for example:
Sun Fire V480 Server 1 Sun Fire V480 Server 2

hm0 ----- hm0 (interconnect)
hm1 ----- hm1 (interconnect)
ce0 ---- e0 (to the public network)
The Sun Cluster software recognizes the NIC that connects to the public network and automatically
configures the other two NICs into an IPMI group, sc_ipmi0.
Configuring Sun StorEdge 3510 FC Array

Refer to the Hardware Specification for help: Sun Cluster 3.1 - 3.2 With Sun StorEdge 3510 or 3511
FC RAID Array Manual for Solaris OS at http://docs.sun.com/app/docs/doc/819-
3016?l=en&q=3510&a=load. The Sun StorEdge 3510 FC array with hardware RAID-5 is used for
storing and for the redundancy of data. Raw disk on the storage is enough. Solaris Volume Manager
and Solstice DiskSuiteTM software are unnecessary.
Configure RAID-5, and then make a file system and mount it within the Sun Cluster global file system.
For example, locate your file system on /dev/rdsk/d4s2. The following operations can be
performed on either node.
#mkdir -p /global/u01
#newfs /dev/rdsk/d4s2
Installing Sun Cluster 3.1 08/05 Software
Step 1: Download and install.
The Sun Cluster software is contained in the Free Solaris Cluster/Java Availability Suite. You can
download the software from the Previous Release Download section of this web page:
http://www.sun.com/software/solaris/cluster/get.html. Sun Cluster Agents software is
available for free from the Sun Cluster Agents Download section of the same web page.
Copy the packages on each node, unpack them, and execute the installation on the primary node
(v480-1). Become superuser to perform all the commands.
# ./scinstall
Choose the right options during the installation:
...
1)Establish a new cluster using this machine as the first node
...
Option: 1
Cluster name:oraclecluster
Node name:v480-1
Transport junctions: No
first transport adapter:hm0
second transport adapter:hm1
The new file system to use is: /u01
……
Rebooting ...
Unpack the package and execute the installation on the secondary node, v480-2:
#./scinstall
...
• 2) Add this machine as a node in an established cluster
...
Option: 2
Step 2: Add PATH and MANPATH for the Sun Cluster software:
#vi /.profile
...
PATH=$PATH:/usr/cluster/bin
export PATH
MANPATH=$MANPATH:/usr/cluster/man/
export MANPATH
Installing Sun Cluster HA Agent for Oracle Database 10g HA

Unpack the Cluster Agent package on each node and install it:
#./install
Choose Sun Cluster highly available agent for Oracle.
On each node, you can add an entry in /etc/vfstab to mount the cluster file system:
#vi /etc/vfatab
/dev/global/dsk/d4s2 /dev/global/rdsk/d4s2 /u01 ufs 2 no logging
#mountall
In the previous command, /dev/global/dsk/d4s2 and /dev/global/rdsk/d4s2 stand for
the disks and raw disks acting as the global device on which the cluster file system is located.
Installing Oracle Database 10g HA

Step 1: Download and perform the pre-installation tasks.
Download Oracle 10g from www.oracle.com.
Note: Add user oracle to the environment variables in $HOME/.profile for each node. HOME for
user oracle is located in /u01/oraclehome.
Step 2: Install Oracle 10g.

Copy and unpack the package onto the two nodes. Install the Oracle 10g application on each node, but
don't create a database.
Place all the database-related files (data files, redo log files, and control files) on the cluster file system
/u01/oraclehome. Then create the instance clusterdb. An instance for general use is enough
for our purposes. Refer to the Oracle 10g installation guide for more information.
Note: Add the Solaris 10 OS to oraparam.ini as follows:
Solaris=5.6, 5.7, 5.8, 5.9, 5.10
Password for system:oracle

Instance name:clusterdb
Please remember these three environment variables for later use:
$ORACLE_BASE /u01/oraclehome
$ORACLE_HOME /u01/oraclehome/product/10.2.0/Db_1
$ORACLE_SID clusterdb
Step 3: Become the superuser and confirm the current state of the cluster:
#su – root
#scstat
The two groups on each node should be online.
Configuring Sun Cluster 3.1 08/05 Software

Step 1: Enable access for the user and password to be used for fault monitoring.
Grant to this user authority on the v_$sysstat view and the v_$archive_dest view.
$sqlplus “/ as sysdba”
sql > grant connect, resource to cluster identified by clusterpasswd;
sql >alter user cluster default tablespace system quota 1m on system;
sql >grant select on v_$sysstat to cluster;
sql >grant select on v_$archive_dest to cluster;
sql >grant create session to cluster;
sql >grant create table to cluster;
sql >exit;
Step 2: Use the logical host name for Oracle listener and name service.
Become user oracle and add path for Oracle10g in $HOME/.profile.
$su - oracle
$vi /u01/oraclehome/.profile
PATH=$PATH:/u01/oraclehome/product/10.2.0/Db_1/bin
export PATH
Start Oracle net service management:

$netmgr
Add a listener, according to your $SID, with the default name LISTENER and change the host name
to oracleserver.
Add clusterdb in the service naming, change the host name to oracleserver, and restart the
Oracle database to load the modified parameters for the listener.
Step 3: Configure Oracle NET8 for the Sun Cluster software.

Become superuser on a cluster node. Register resource types for the Oracle software.
#scrgadm -a -t SUNW.oracle_server
#scrgadm -a -t SUNW.oracle_listener
Create a failover resource group clustergroup to hold and manage all the resources. Register the
two nodes into the resource group:
#scrgadm -a -g clustergroup -h v480-1, v480-2
Add a network resource to the failover resource group:

#scrgadm -a -L -g clustergroup -l oracleserver sc_ipmp0@v480-1, sc_ipmp0@v480-2
Register the SUNW.HAStoragePlus resource type:
#scrgadm -a -t SUNW.HAStoragePlus
Create the resource oracle-hastp-rs of type SUNW.HAStoragePlus, and enable the highly
available cluster file system:
#scrgadm -a -j oracle-hastp-ra -g clustergroup -t SUNW.HAStoragePlus -x
FilesystemMountPoint=/u01, -x AffinityOn=True
Run the scswitch command to bring the resource group online:
#scswitch -Z -g clustergroup
Create Oracle application resources in the failover resource group:

#scrgadm -a -j oracle-server -g clustergroup -t SUNW.oracle_server -x
ORACLE_HOME=/u01/oraclehome/product/10.2.0/Db_1 -x Alert_log_file=/u01/oraclehome/message-
log -x ORACLE_SID=clusterdb -x Connect_string=cluster/clusterpasswd
#scrgadm -a -j oracle-listener -g clustergroup -t SUNW.oracle_listener -x

ORACLE_HOME=/u01/oraclehome/product/10.2.0/Db_1 -x LISTENER_NAME=LISTENER
Bring the resource online:

#scswitch -Z -g clustergroup
Verifying Sun Cluster 3.1 08/05 Software
Step 1: Become the superuser and determine which node is currently master of the Oracle resource:
#scstat -p
Step 2: Confirm that you can connect to the database:

# su – oracle
$ sqlplus /nolog
SQL> connect / as sysdba
SQL> select * from v$version;
Step 3: Shut down the master node.
Step 4: After a while (depending on the Oracle server starting time), connect remotely again on the
other node:
# su – oracle
$ sqlplus /nolog
SQL> connect / as sysdba
SQL> select * from v$version;
Summary
Sun Cluster software prevents unexpected downtime by failing over and providing highly available
database access in the computing environment. Sun Cluster software can also provide advanced
features, such as scalable services, global access to devices and networking, and cluster file systems.
As you have seen, the Solaris 10 OS also plays big role in the solution by enabling IPMP, global file
system configuration, and Sun Cluster services management within the Service Management Facility
(SMF) framework.
Appendix
Here is the output of the scstat command:
---------------------------------------------------------------------
-- Cluster Nodes --
Node name Status

--------- ------
Cluster node: v480-2 Online
Cluster node: v480-1 Online
------------------------------------------------------------------
-- Cluster Transport Paths --
Endpoint Endpoint Status

-------- -------- ------
Transport path: v480-2:hme1 v480-1:hme1 Path online
Transport path: v480-2:hme0 v480-1:hme0 Path online
------------------------------------------------------------------
-- Quorum Summary --
Quorum votes possible: 3
Quorum votes needed: 2
Quorum votes present: 3
-- Quorum Votes by Node --
Node Name Present Possible Status

--------- ------- -------- ------
Node votes: v480-2 1 1 Online
Node votes: v480-1 1 1 Online
-- Quorum Votes by Device --
Device Name Present Possible Status

----------- ------- -------- ------
Device votes: /dev/did/rdsk/d4s2 1 1 Online
------------------------------------------------------------------
-- Device Group Servers --
Device Group Primary Secondary

------------ ------- ---------
-- Device Group Status --
Device Group Status

------------ ------
-- Multi-owner Device Groups --
Device Group Online Status

------------ -------------
------------------------------------------------------------------
-- Resource Groups and Resources --
Group Name Resources

---------- ---------
Resources: clustergroup oracleserver oracle-hastp-rs oracle-listener oracle-server
-- Resource Groups --
Group Name Node Name State

---------- --------- -----
Group: clustergroup v480-1 Offline
Group: clustergroup v480-2 Online
-- Resources --
Resource Name Node Name State Status Message

------------- --------- ----- --------------
Resource: adccnet v480-1 Offline Offline - LogicalHostname offline.
Resource: adccnet v480-2 Online Online - LogicalHostname online.
Resource: oracle-hastp-rs v480-1 Offline Offline

Resource: oracle-hastp-rs v480-2 Online Online
Resource: oracle-listener v480-1 Offline Offline

Resource: oracle-listener v480-2 Online Online
Resource: oracle-server v480-1 Offline Offline
Resource: oracle-server v480-2 Online Online
------------------------------------------------------------------
-- IPMP Groups --
Node Name Group Status Adapter Status

--------- ----- ------ ------- ------
IPMP Group: v480-2 sc_ipmp0 Online ce0 Online
IPMP Group: v480-1 sc_ipmp0 Online ce0 Online
------------------------------------------------------------------
For More Information

Here are additional resources:
● Sun download pages:
● Solaris 10 OS: http://www.sun.com/software/solaris/get.jsp
● Sun Cluster software: http://www.sun.com/software/solaris/cluster/get.html
● Sun Cluster High Availability Agent: http://www.sun.com/software/cluster
● These Sun training courses at http://www.sun.com/training/:
● Sun Cluster 3.1 Administration (ES-338)
● Sun Cluster 3.1 Advanced Administration (ES-438)
● Sun Cluster course catalog: http://www.sun.com/training/catalog/cluster/index.xml
● Support:
● Register your Sun gear: https://inventory.sun.com/inventory/
● Services: http://www.sun.com/service/index.jsp
● SunSolve Online: http://sunsolve.sun.com
● Discussions such as the Clustering Forum:
http://forum.java.sun.com/forum.jspa?forumID=842&start=0
● The following documents at http://docs.sun.com:
● Sun Cluster Concepts Guide for Solaris OS
● Sun Cluster Overview for Solaris OS
● System Administration Guide: IP Services
● Sun Cluster Software Installation Guide for Solaris OS
● Sun Cluster Data Service for Oracle Guide for Solaris OS
● Sun Cluster System Administration Guide for Solaris OS
● Sun Cluster Data Service Planning and Administration Guide for Solaris OS
● SUN Cluster 3 Programming: Integrating Applications into the SunPlex Environment by Joseph
Bianco, Peter Lees, and Kevin Rabito:
http://www.amazon.com/gp/product/0130479756/104-0560062-
1750305?v=glance&n=283155
● Sun wikis at http://wikis.sun.com/dashboard.action, for example:
● Sun Cluster Wiki: http://wikis.sun.com/display/SunCluster/Home
● Sun BluePrints™ Wiki: http://wikis.sun.com/display/BluePrints/Main
● BigAdmin Wiki: http://wikis.sun.com/display/BigAdmin/Home
● Related resources on BigAdmin:

● Sun Cluster 3.1 8/05 for Solaris x86 Manuals on docs.sun.com:
http://www.sun.com/bigadmin/hubs/javaes/5/library/manuals-
sc31805x86.jsp
● Installing and Configuring Sun Cluster 3.1 09/04 Software for High-Availability
Applications:
http://www.sun.com/bigadmin/features/articles/install_cluster.html
● Installation Guide for Solaris Cluster 3.2 Software and Oracle 10g Release 2 Real
Application Clusters (pdf):
http://www.sun.com/bigadmin/features/articles/cluster_rac_install.pdf
● Best Practices for Running Oracle Databases in Solaris Containers:
http://www.sun.com/bigadmin/features/articles/db_in_containers.jsp
● Events of interest to users of Sun products:

● Worldwide developer events: http://developers.sun.com/events/
● Current events: http://www.sun.com/events/index.jsp
Licensing Information
Unless otherwise specified, the use of this software is authorized pursuant to the terms of the license
found at http://www.sun.com/bigadmin/common/berkeley_license.html.

Installing and Configuring Sun Cluster For Oracl 10g HA

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installing and Configuring Sun Cluster For Oracl 10g HA

Uploaded by

Copyright:

Available Formats

Installing and Configuring

Sun™ Cluster 3.1 Software

ORACLE is a registered trademark of Oracle Corporation.

DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,

What Is a High Availability Cluster?

What Can Sun Cluster Software Do for HA Applications?

• Oracle services can run only on one server.

The cluster environment oraclecluster is set up according to Figure 1, so it is very important to

There are three necessary components for the cluster interconnect:

Public Network Interfaces

Global Devices, Global Namespaces, and Cluster File System

Quorum and Quorum Device

Figure 4: Standard Versus Clustered Client-Server Configuration

Resource, Resource Types, and Resource Groups

Figure 5: Topology for Cluster oraclecluster

Installation and Configuration

Installing the Solaris 10 OS for SPARC Platforms

Table 2: Example File-System Allocation

3 overlap (according to This is the entire disk.

Step 2: Configure the IP address for each node.

Add the logical host name:

Step 3: Connect the machines according to the topology.

Connect the physical interfaces, for example:

Sun Fire V480 Server 1 Sun Fire V480 Server 2

Configuring Sun StorEdge 3510 FC Array

Installing Sun Cluster HA Agent for Oracle Database 10g HA

Choose Sun Cluster highly available agent for Oracle.

Installing Oracle Database 10g HA

Step 2: Install Oracle 10g.

Password for system:oracle

The two groups on each node should be online.

Configuring Sun Cluster 3.1 08/05 Software

Start Oracle net service management:

Step 3: Configure Oracle NET8 for the Sun Cluster software.

Add a network resource to the failover resource group:

Register the SUNW.HAStoragePlus resource type:

Run the scswitch command to bring the resource group online:

Create Oracle application resources in the failover resource group:

#scrgadm -a -j oracle-listener -g clustergroup -t SUNW.oracle_listener -x

Bring the resource online:

Step 2: Confirm that you can connect to the database:

Step 3: Shut down the master node.

Node name Status

-- Cluster Transport Paths --

Endpoint Endpoint Status

Quorum votes possible: 3

-- Quorum Votes by Node --

Node Name Present Possible Status

-- Quorum Votes by Device --

Device Name Present Possible Status

-- Device Group Servers --

Device Group Primary Secondary

-- Device Group Status --

Device Group Status

-- Multi-owner Device Groups --

Device Group Online Status

-- Resource Groups and Resources --

Group Name Resources

Group Name Node Name State

Resource Name Node Name State Status Message

Resource: oracle-hastp-rs v480-1 Offline Offline

Resource: oracle-listener v480-1 Offline Offline