天行健，君子以自强不息

1. SPARC: If your cluster is running Oracle Parallel Server or Real Application
Clusters, shut down all instances of the database.
Refer to the Oracle Parallel Server or Oracle Real Application Clusters product
documentation for shutdown procedures.
2. Become superuser on any node in the cluster.
3. Shut down the cluster immediately.
From a single node in the cluster, type the following command.
# scshutdown -g0 -y
4. Verify that all nodes are showing the ok prompt on a SPARC based system or a
Boot Subsystem on an x86 based system.
Do not power off any nodes until all cluster nodes are at the ok prompt on a
SPARC based system or in a Boot Subsystem on an x86 based system.
5. If necessary, power off the nodes.

SPARC: Example—Shutting Down a Cluster
The following example shows the console output when stopping normal cluster
operation and bringing down all nodes so that the ok prompt is shown. The -g 0
option sets the shutdown grace period to zero, -y provides an automatic yes response
to the confirmation question. Shutdown messages also appear on the consoles of the
other nodes in the cluster.
# scshutdown -g0 -y
Wed Mar 10 13:47:32 phys-schost-1 cl_runtime:
WARNING: CMM monitoring disabled.
phys-schost-1#
INIT: New run level: 0
The system is coming down. Please wait.
System services are now being stopped.
/etc/rc0.d/K05initrgm: Calling scswitch -S (evacuate)
The system is down.
syncing file systems… done
Program terminated
ok

x86: Example—Shutting Down a Cluster
The following example shows the console output when stopping normal cluster
operation and bringing down all nodes. The -g 0 option sets the shutdown grace
period to zero, -y provides an automatic yes response to the confirmation question.
Shutdown messages also appear on the consoles of the other nodes in the cluster.
# scshutdown -g0 -y
May 2 10:32:57 phys-schost-1 cl_runtime:
WARNING: CMM: Monitoring disabled.
root@phys-schost-1#
INIT: New run level: 0
The system is coming down. Please wait.
System services are now being stopped.
/etc/rc0.d/K05initrgm: Calling scswitch -S (evacuate)
failfasts already disabled on node 1
Print services already stopped.
May 2 10:33:13 phys-schost-1 syslogd: going down on signal 15
The system is down.
syncing file systems… done
Type any key to continue

1. To start a cluster whose nodes have been shut down and are at the ok prompt or
at the Select (b)oot or (i)nterpreter prompt on the Current Boot
Parameters screen, boot(1M) each node.
If you make configuration changes between shutdowns, start the node with the
most current configuration first. Except in this situation, the boot order of the
nodes does not matter.
 SPARC:
ok boot
 x86:
< << Current Boot Parameters >>>
Boot path: /pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/
sd@0,0:a
Boot args:
Type b [file-name] [boot-flags] to boot with options
or i to enter boot interpreter
or to boot with defaults
< << timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b

Messages are displayed on the booted nodes’ consoles as cluster components are
activated.
Note – Cluster nodes must have a working connection to the cluster interconnect to
attain cluster membership.
2. Verify that the nodes booted without error and are online.
The scstat(1M) command reports the nodes’ status.
# scstat -n
Note – If a cluster node’s /var file system fills up, Sun Cluster might not be able to
restart on that node. If this problem arises, see “How to Repair a Full /var File
System” on page 70.
SPARC: Example—Booting a Cluster
The following example shows the console output when booting node
phys-schost-1 into the cluster. Similar messages appear on the consoles of the other
nodes in the cluster.
ok boot
Rebooting with command: boot
…
Hostname: phys-schost-1
Booting as part of a cluster
NOTICE: Node phys-schost-1 with votecount = 1 added.
NOTICE: Node phys-schost-2 with votecount = 1 added.
NOTICE: Node phys-schost-3 with votecount = 1 added.
…
NOTICE: Node phys-schost-1: attempting to join cluster
…
NOTICE: Node phys-schost-2 (incarnation # 937690106) has become reachable.
NOTICE: Node phys-schost-3 (incarnation # 937690290) has become reachable.
NOTICE: cluster has reached quorum.
NOTICE: node phys-schost-1 is up; new incarnation number = 937846227.
NOTICE: node phys-schost-2 is up; new incarnation number = 937690106.
NOTICE: node phys-schost-3 is up; new incarnation number = 937690290.
NOTICE: Cluster members: phys-schost-1 phys-schost-2 phys-schost-3.
…

Run the scshutdown(1M) command to shut down the cluster, then boot the cluster
with the boot(1M) command on each node.
1. SPARC: If your cluster is running Oracle Parallel Server or Oracle Real
Application Clusters, shut down all instances of the database.
Refer to the Oracle Parallel Server or Oracle Real Application Clusters product
documentation for shutdown procedures.
2. Become superuser on any node in the cluster.
3. Shut down the cluster.
From a single node in the cluster, type the following command.
# scshutdown -g0 -y
Each node is shut down.
Note – Cluster nodes must have a working connection to the cluster interconnect to
attain cluster membership.
4. Boot each node.
The order in which the nodes are booted does not matter unless you make
configuration changes between shutdowns. If you make configuration changes
between shutdowns, start the node with the most current configuration first.
 SPARC:
ok boot
 x86:
< << Current Boot Parameters >>>
Boot path: /pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/
sd@0,0:a
Boot args:
Type b [file-name] [boot-flags] to boot with options
or i to enter boot interpreter
or to boot with defaults
< << timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b
Messages appear on the booted nodes’ consoles as cluster components are
activated.

Caution – Do not use send brk on a cluster console to shut down a cluster node. The
command is not supported within a cluster.
1. SPARC: If your cluster is running Oracle Parallel Server or Oracle Real
Application Clusters, shut down all instances of the database.
Refer to the Oracle Parallel Server or Oracle Real Application Clusters product
documentation for shutdown procedures.
2. Become superuser on the cluster node to be shut down.
3. Switch all resource groups, resources, and device groups from the node being
shut down to other cluster members.
On the node to be shut down, type the following command.
# scswitch -S -h node
-S Evacuates all device services and resource groups from the specified
node.
-h node Specifies the node from which you are switching resource groups and
device groups.
4. Shut down the cluster node.
On the node to be shut down, type the following command.
# shutdown -g0 -y -i0
5. Verify that the cluster node is showing the ok prompt or the Select (b)oot or
(i)nterpreter prompt on the Current Boot Parameters screen.
6. If necessary, power off the node.

If you intend to shut down or reboot other, active nodes in the cluster, wait until the
node you are booting has at least reached the login prompt. Otherwise, the node will
not be available to take over services from other nodes in the cluster that you shut
down or reboot.
Note – Starting a cluster node can be affected by the quorum configuration. In a
two-node cluster, you must have a quorum device configured so that the total quorum
count for the cluster is three. You should have one quorum count for each node and
one quorum count for the quorum device. In this situation, if the first node is shut
down, the second node continues to have quorum and runs as the sole cluster
member. For the first node to come back in the cluster as a cluster node, the second
node must be up and running. The required cluster quorum count (two) must be
present.
1. To start a cluster node that has been shut down, boot the node.
 SPARC:
ok boot
 x86:
< << Current Boot Parameters >>>
Boot path: /pci@0,0/pci8086,2545@3/pci8086,1460@1d/pci8086,341a@7,1/
sd@0,0:a
Boot args:
Type b [file-name] [boot-flags] to boot with options
or i to enter boot interpreter
or to boot with defaults
< << timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b

Messages appear on the booted nodes’ consoles as cluster components are
activated.
Note – A cluster node must have a working connection to the cluster interconnect to
attain cluster membership.
2. Verify that the node has booted without error, and is online.
The scstat command reports the status of a node.
# scstat -n

If you intend to shut down or reboot other, active nodes in the cluster, wait until the
node you are rebooting has at least reached the login prompt. Otherwise, the node will
not be available to take over services from other nodes in the cluster that you shut
down or reboot.
1. SPARC: If the cluster node is running Oracle Parallel Server or Oracle Real
Application Clusters, shut down all instances of the database.
Refer to the Oracle Parallel Server or Oracle Real Application Clusters product
documentation for shutdown procedures.
2. Become superuser on the cluster node to be shut down.
3. Shut down the cluster node by using the scswitch and shutdown commands.
Enter these commands on the node to be shut down. The -i 6 option with the
shutdown command causes the node to reboot after the node shuts down.
# scswitch -S -h node
# shutdown -g0 -y -i6
Note – Cluster nodes must have a working connection to the cluster interconnect to
attain cluster membership.
4. Verify that the node has booted without error, and is online.
# scstat -n

Share This