【标题】：第一次blog，第一次cluster
【关键字】：blog,cluster
【来源】：http://www.cublog.cn/u/22422/showart.php?id=149409

第一次blog，第一次cluster

Solaris 9 disk suite cluster3.1 oracle9。2。0。1。0 双机安装文档

一、       硬件配置
Sun Fire V440 Server                2台
四口10/100/1000自适应以太网卡    2块
二、       软件配置
Solaris 9（9/05）
Sun Cluster 3.1（9/04）
Oracle 9 (9.2.0.1.0)
三、       操作系统安装
①系统盘（72GB）分区：
0 /                20000MB
1 swap             16000MB
2                   整个硬盘
3 /export/home 32853MB
4 /globaldevices   1024MB

5                   （未用分区）
6                   （未用分区）
7                   （未用分区）

剩余109÷÷÷÷注意：必须有剩余空间，装完操作系统后再使用format划分7号分区
②主机名命名、IP设置、子网掩码
JDSN-FIR 10.0.0.33 255.255.255.0

JDSN-ORA oracle 对外地址 10.0.0.39
JDSN-SEC 10.0.0.34 255.255.255.0
注：IPMP
JDSN-ORA oracle 对外地址 10.0.0.39
心跳网口 ce2 ce1

两台机器的主网卡都是ce0
③补丁安装
如果需要，安装solaris最新补丁下载地址：
④修改内核参数
在JDSN-FIR 和JDSN-SEC中的/etc/system文件中加入如下：
set shmsys:shminfo_shmmax=4294967295
set semsys:seminfo_semmap=1024
set semsys:seminfo_semmni=2048
set semsys:seminfo_semmns=2048
set semsys:seminfo_semmsl=2048
set semsys:seminfo_semmnu=2048
set semsys:seminfo_semume=200
set shmsys:shminfo_shmmin=200
set shmsys:shminfo_shmmni=200
set shmsys:shminfo_shmseg=200
set semsys:seminfo_semvmx=32767

Groupadd –g 8888 dba

Mkdir /oracle

User –m –c “oracle user” –g dba –u 8888 –d /oracle oracle

Chown – R oracle:dba /oracle

Su – oracle

Vi .profile

ORACLE_BASE=/oracle

ORACLE_HOME=$ORACLE_BASE/products/9.2.0.1.0

ORACLE_SID=JDSNWF

DISPLAY=127.0.0.0.1:0.0

PATH=$PATH:$ORACLE_HOME/BIN

Export ORACLE_BASE ORACLE_HOME ORACLE_SID PATH DISPLAY

设置OK下local-mac-address? True

  OK setenv local-mac-address? True
  OK reset-all
⑦编辑/etc/hosts文件
  在JDSN-FIR和JDSN-SEC上编辑成如下：
127.0.0.1
10.0.0.33        JDSN-FIR loghost
10.0.0.34        JDSN-SEC
10.0.0.39        JDSN-ORA

编译/etc/hostname.ce0

在JDSN-FIR 和 JDSN-SEC上编辑如下：

Hostname + netmask + broadcast + group ipmp1 up

(hostname= JDSN-FIR or JDSN-SEC )
③ 编辑/.profile
# cp /etc/skel/local.profile /.profile
# vi /.profile
加入：
PATH=$PATH:/usr/cluster/bin;

MANPATH=$MANPATH:/usr/cluster/man :/usr/share/man

EDITOR=vi
export PATH MANPATH

说明：必须加入默认网关，并且主机可以ping通网关，IPMP才可使用

以上操作在两个机器上进行

六、安装Sun Cluster 3.1软件

② 安装Sun Cluster3.1软件

以JDSN-FIR 建立第一个节点
（目录好象差一级）

#cd /cdrom/Solaris_sparc/Product/sun_cluster/Solaris_9/Tools
#./scinstaller
  *** Main Menu ***
Please select from one of the following (*) options:
   * 1) Install a cluster or cluster node
      2) Configure a cluster to be JumpStarted from this install server
      3) Add support for new data services to this cluster node
   * 4) Print release information for this cluster node
   * ?) Help with menu options
   * q) Quit
Option:  1
_[H_[J
  *** Install Menu ***

Please select from any one of the following options:

      1) Install all nodes of a new cluster
      2) Install just this machine as the first node of a new cluster
      3) Add this machine as a node in an existing cluster
      ?) Help with menu options
      q) Return to the Main Menu
Option:  2
_[H_[J
  *** Installing just the First Node of a New Cluster ***

This option is used to establish a new cluster using this machine as
the first node in that cluster.
Once the cluster framework software is installed, you will be asked
for the name of the cluster. Then, you will have the opportunity to
run sccheck(1M) to test this machine for basic Sun Cluster
pre-configuration requirements.

After sccheck(1M) passes, you will be asked for the names of the
other nodes which will initially be joining that cluster. In
addition, you will be asked to provide certain cluster transport
configuration information.

Press Control-d at any time to return to the Main Menu.

Do you want to continue (yes/no) [yes]?

_[H_[J_[H_[J
  >>> Software Patch Installation <<<

If there are any Solaris or Sun Cluster patches that need to be added
as part of this Sun Cluster installation, scinstall can add them for
you. All patches that need to be added must first be downloaded into
a common patch directory. Patches can be downloaded into the patch
directory either as individual patches or as patches grouped together
into one or more tar, jar, or zip files.

If a patch list file is provided in the patch directory, only those
patches listed in the patch list file are installed. Otherwise, all
patches found in the directory will be installed. Refer to the
patchadd(1M) man page for more information regarding patch list files.

Do you want scinstall to install patches for you (yes/no) [yes]?

What is the name of the patch directory?
/cdrom/Solaris_sparc/Product/sun_cluster/Solaris_9/Packages
If a patch list file is provided in the patch directory, only those
patches listed in the patch list file are installed. Otherwise, all
patches found in the directory will be installed. Refer to the
patchadd(1M) man page for more information regarding patch list files.

Do you want scinstall to use a patch list file (yes/no) [no]?

_[H_[J_[H_[J
  >>> Cluster Name <<<

Each cluster has a name assigned to it. The name can be made up of
any characters other than whitespace. Each cluster name should be
unique within the namespace of your enterprise.

What is the name of the cluster you want to establish?  ourcluster
_[H_[J_[H_[J
  >>> Check <<<

This step allows you to run sccheck(1M) to verify that certain basic
hardware and software pre-configuration requirements have been met.
If sccheck(1M) detects potential problems with configuring this
machine as a cluster node, a report of failed checks is prepared and
available for display on the screen. Data gathering and report
generation can take several minutes, depending on system
configuration.

Do you want to run sccheck (yes/no) [yes]?  no
_[H_[J_[H_[J
  >>> Cluster Nodes <<<

This Sun Cluster release supports a total of up to 16 nodes.

Please list the names of the other nodes planned for the initial
cluster configuration. List one node name per line. When finished,
type Control-D:

Node name:  JDSN-FIR
Node name:  JDSN-SEC
Node name (Control-D to finish):  ^D__

This is the complete list of nodes:

      JDSN-FIR

JDSN-SEC

it correct (yes/no) [yes]?

_[H_[J_[H_[J
  >>> Authenticating Requests to Add Nodes <<<

Once the first node establishes itself as a single node cluster,
other nodes attempting to add themselves to the cluster configuration
must be found on the list of nodes you just provided. You can modify
this list using scconf(1M) or other tools once the cluster has been
established.

By default, nodes are not securely authenticated as they attempt to
add themselves to the cluster configuration. This is generally
considered adequate, since nodes which are not physically connected
to the private cluster interconnect will never be able to actually
join the cluster. However, DES authentication is available. If DES
authentication is selected, you must configure all necessary
encryption keys before any node will be allowed to join the cluster
(see keyserv(1M), publickey(4)).

Do you need to use DES authentication (yes/no) [no]?

_[H_[J_[H_[J
  >>> Network Address for the Cluster Transport <<<

The private cluster transport uses a default network address of
172.16.0.0. But, if this network address is already in use elsewhere
within your enterprise, you may need to select another address from
the range of recommended private addresses (see RFC 1597 for details).

If you do select another network address, bear in mind that the Sun
Cluster software requires that the rightmost two octets always be
zero.

The default netmask is 255.255.0.0. You can select another netmask,
as long as it minimally masks all bits given in the network address.

Is it okay to accept the default network address (yes/no) [yes]?

Is it okay to accept the default netmask (yes/no) [yes]?

_[H_[J_[H_[J
  >>> Point-to-Point Cables <<<

The two nodes of a two-node cluster may use a directly-connected
interconnect. That is, no cluster transport junctions are configured.
However, when there are greater than two nodes, this interactive form
of scinstall assumes that there will be exactly two cluster transport
junctions.

Does this two-node cluster use transport junctions (yes/no) [yes]?

_[H_[J_[H_[J
  >>> Cluster Transport Junctions <<<

All cluster transport adapters in this cluster must be cabled to a
transport junction, or "switch". And, each adapter on a given node
must be cabled to a different junction. Interactive scinstall
requires that you identify two switches for use in the cluster and
the two transport adapters on each node to which they are cabled.

What is the name of the first junction in the cluster [switch1]?

What is the name of the second junction in the cluster [switch2]?

_[H_[J_[H_[J
  >>> Cluster Transport Adapters and Cables <<<

You must configure at least two cluster transport adapters for each
node in the cluster. These are the adapters which attach to the
private cluster interconnect.

Select the first cluster transport adapter:

      1 ce1
      2 ce2
      3 ce3
      4 ce4

Option:  1

Adapter "ce1 is an Ethernet adapter.

Searching for any unexpected network traffic on "ce1 ... done
Verification completed. No traffic was detected over a 10 second
sample period.

The "dlpi" transport type will be set for this cluster.

Name of the junction to which "ce1 is connected [switch1]?

Each adapter is cabled to a particular port on a transport junction.
And, each port is assigned a name. You can explicitly assign a name
to each port. Or, for Ethernet switches, you can choose to allow
scinstall to assign a default name for you. The default port name
assignment sets the name to the node number of the node hosting the
transport adapter at the other end of the cable.

For more information regarding port naming requirements, refer to the
scconf_transp_jct family of man pages (e.g.,
scconf_transp_jct_dolphinswitch(1M)).

Use the default port name for the "ce1 connection (yes/no) [yes]?

Select the second cluster transport adapter:

      1) ce1

2) ce2

3) ce3

4) ce4

6) ce5

Option:  2

Adapter "ce2 is an Ethernet adapter.

Searching for any unexpected network traffic on "ce2 ... done
Verification completed. No traffic was detected over a 10 second
sample period.

Name of the junction to which "ce2 is connected [switch2]?

Use the default port name for the "ce2 connection (yes/no) [yes]?

_[H_[J_[H_[J
  >>> Global Devices File System <<<

Each node in the cluster must have a local file system mounted on
/global/.devices/node@<nodeID> before it can successfully participate
as a cluster member. Since the "nodeID" is not assigned until
scinstall is run, scinstall will set this up for you.

You must supply the name of either an already-mounted file system or
raw disk partition which scinstall can use to create the global
devices file system. This file system or partition should be at least
512 MB in size.

If an already-mounted file system is used, the file system must be
empty. If a raw disk partition is used, a new file system will be
created for you.

The default is to use /globaldevices.

Is it okay to use this default (yes/no) [yes]?

_[H_[J_[H_[J
  >>> Automatic Reboot <<<

Once scinstall has successfully installed and initialized the Sun
Cluster software for this machine, it will be necessary to reboot.
After the reboot, this machine will be established as the first node
in the new cluster.

Do you want scinstall to reboot for you (yes/no) [yes]?

_[H_[J_[H_[J
  >>> Confirmation <<<

Your responses indicate the following options to scinstall:

   scinstall -ik \
         -C ourcluster    -F \
         -M patchdir=/cdrom/Solaris_sparc/Product/sun_cluster/Solaris_9/Packages \
         -T node=JDSN-FIR,JDSN-SEC,authtype=sys \
         -A trtype=dlpi,name=ce1 -A trtype=dlpi,name=ce2 \
         -B type=switch,name=switch1 -B type=switch,name=switch2 \
         -m endpoint=:ce1,endpoint=switch1 \
         -m endpoint=:ce2,endpoint=switch2 \


Are these the options you want to use (yes/no) [yes]?

Do you want to continue with the install (yes/no) [yes]?

Checking device to use for global devices file system ... done
Installing patches ... failed

scinstall:  Problems detected during extraction or installation of patches.

Initializing cluster name to "cluster" ... done
Initializing authentication options ... done
Initializing configuration for adapter "ce1" ... done
Initializing configuration for adapter "ce2" ... done
Initializing configuration for junction "switch1" ... done
Initializing configuration for junction "switch2" ... done
Initializing configuration for cable ... done
Initializing configuration for cable ... done

Setting the node ID for "JDSN-FIR" ... done (id=1)

Setting the major number for the "did" driver ... done
"did" driver major number set to 300

Checking for global devices global file system ... done
Updating vfstab ... done

Verifying that NTP is configured ... done
Installing a default NTP configuration ... done
Please complete the NTP configuration after scinstall has finished.

Verifying that "cluster" is set for "hosts" in nsswitch.conf ... done
Adding the "cluster" switch to "hosts" in nsswitch.conf ... done

Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done
Adding the "cluster" switch to "netmasks" in nsswitch.conf ... done

Verifying that power management is NOT configured ... done
Unconfiguring power management ... done
/etc/power.conf has been renamed to /etc/power.conf.042006154016
Power management is incompatible with the HA goals of the cluster.
Please do not attempt to re-configure power management.

Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ... done

Ensure network routing is disabled ... done
Network routing has been disabled on this node by creating /etc/notrouter.
Having a cluster node act as a router is not supported by Sun Cluster.
Please do not re-enable network routing.

Log file - /var/cluster/logs/install/scinstall.log.2140
②       将JDSN-SEC作为第二节点加入到cluster中
#cd /cdrom/Solaris_sparc/Product/sun_cluster/Solaris_9/Tools
#./scinstaller

*** Main Menu ***

Please select from one of the following (*) options:

   * 1) Install a cluster or cluster node
      2) Configure a cluster to be JumpStarted from this install server
      3) Add support for new data services to this cluster node
   * 4) Print release information for this cluster node

   * ?) Help with menu options
   * q) Quit

Option:  1
*** Install Menu ***

Please select from any one of the following options:

      1) Install all nodes of a new cluster
      2) Install just this machine as the first node of a new cluster
      3) Add this machine as a node in an existing cluster

      ?) Help with menu options
      q) Return to the Main Menu

Option:  3
*** Adding a Node to an Existing Cluster ***

This option is used to add this machine as a node in an already
established cluster. If this is an initial cluster install, there may
only be a single node which has established itself in the new cluster.

Once the cluster framework software is installed, you will be asked
to provide both the name of the cluster and the name of one of the
nodes already in the cluster. Then, sccheck(1M) is run to test this
machine for basic Sun Cluster pre-configuration requirements.

After sccheck(1M) passes, you may be asked to provide certain cluster
transport configuration information.

Press Control-d at any time to return to the Main Menu.

Do you want to continue (yes/no) [yes]?
  >>> Software Patch Installation <<<

If there are any Solaris or Sun Cluster patches that need to be added
as part of this Sun Cluster installation, scinstall can add them for
you. All patches that need to be added must first be downloaded into
a common patch directory. Patches can be downloaded into the patch
directory either as individual patches or as patches grouped together
into one or more tar, jar, or zip files.

If a patch list file is provided in the patch directory, only those
patches listed in the patch list file are installed. Otherwise, all
patches found in the directory will be installed. Refer to the
patchadd(1M) man page for more information regarding patch list files.

Do you want scinstall to install patches for you (yes/no) [yes]?

What is the name of the patch directory

/cdrom/Solaris_sparc/Product/sun_cluster/Solaris_9/Packages

If a patch list file is provided in the patch directory, only those
patches listed in the patch list file are installed. Otherwise, all
patches found in the directory will be installed. Refer to the
patchadd(1M) man page for more information regarding patch list files.

Do you want scinstall to use a patch list file (yes/no) [no]?
  >>> Sponsoring Node <<<

For any machine to join a cluster, it must identify a node in that
cluster willing to "sponsor" its membership in the cluster. When
configuring a new cluster, this "sponsor" node is typically the first
node used to build the new cluster. However, if the cluster is
already established, the "sponsoring" node can be any node in that
cluster.

Already established clusters can keep a list of hosts which are able
to configure themselves as new cluster members. This machine should
be in the join list of any cluster which it tries to join. If the
list does not include this machine, you may need to add it using
scconf(1M) or other tools.

And, if the target cluster uses DES to authenticate new machines
attempting to configure themselves as new cluster members, the
necessary encryption keys must be configured before any attempt to
join.

What is the name of the sponsoring node [JDSN-FIR]?
>>> Cluster Name <<<

Each cluster has a name assigned to it. When adding a node to the
cluster, you must identify the name of the cluster you are attempting
to join. A sanity check is performed to verify that the "sponsoring"
node is a member of that cluster.

What is the name of the cluster you want to join [ourcluster]?

Attempting to contact "JDSN-FIR" ... done

Cluster name "cluster" is correct.

Press Enter to continue:
>>> Check <<<

This step allows you to run sccheck(1M) to verify that certain basic
hardware and software pre-configuration requirements have been met.
If sccheck(1M) detects potential problems with configuring this
machine as a cluster node, a report of failed checks is prepared and
available for display on the screen. Data gathering and report
generation can take several minutes, depending on system
configuration.

Do you want to run sccheck (yes/no) [yes]?  No
  >>> Autodiscovery of Cluster Transport <<<

If you are using Ethernet adapters as your cluster transport
adapters, autodiscovery is the best method for configuring the
cluster transport.

However, it appears that scinstall has already been run at least once
before on this machine. You can either attempt to autodiscover or
continue with the answers that you gave the last time you ran
scinstall.

Do you want to use autodiscovery anyway (yes/no) [no]?  yes
Probing .....................

The following connection was discovered:

      JDSN-FIR:ce1  switch2  JDSN-SEC:ce1

// 以下部分没有
Probes were sent out from all transport adapters configured for
cluster node "JDSN-FIR". But, they were only received on one of the
network adapters on this machine ("JDSN-SEC"). This may be due to
any number of reasons, including improper cabling, an improper
configuration for "JDSN-FIR", or a switch which was confused by the
probes.

You can either attempt to correct the problem and try the probes
again or try to manually configure the transport. Correcting the
problem may involve re-cabling, changing the configuration for
"JDSN-FIR", or fixing hardware.

Do you want to try again (yes/no) [yes]?  no

[H [J [H [J
  >>> Point-to-Point Cables <<<

The two nodes of a two-node cluster may use a directly-connected
interconnect. That is, no cluster transport junctions are configured.
However, when there are greater than two nodes, this interactive form
of scinstall assumes that there will be exactly two cluster transport
junctions.

Is this a two-node cluster (yes/no) [yes]?

Does this two-node cluster use transport junctions (yes/no) [yes]?

[H [J [H [J
  >>> Cluster Transport Junctions <<<

All cluster transport adapters in this cluster must be cabled to a
transport junction, or "switch". And, each adapter on a given node
must be cabled to a different junction. Interactive scinstall
requires that you identify two switches for use in the cluster and
the two transport adapters on each node to which they are cabled.

What is the name of the first junction in the cluster [switch1]?

What is the name of the second junction in the cluster [switch2]?

[H [J [H [J
  >>> Cluster Transport Adapters and Cables <<<

You must configure at least two cluster transport adapters for each
node in the cluster. These are the adapters which attach to the
private cluster interconnect.

What is the name of the first cluster transport adapter (help) [ce0]?

Adapter "ce0" is an Ethernet adapter.

The "dlpi" transport type will be set for this cluster.

Name of the junction to which "ce0" is connected [switch1]?

Each adapter is cabled to a particular port on a transport junction.
And, each port is assigned a name. You can explicitly assign a name
to each port. Or, for Ethernet switches, you can choose to allow
scinstall to assign a default name for you. The default port name
assignment sets the name to the node number of the node hosting the
transport adapter at the other end of the cable.

For more information regarding port naming requirements, refer to the
scconf_transp_jct family of man pages (e.g.,
scconf_transp_jct_dolphinswitch(1M)).

Use the default port name for the "ce0" connection (yes/no) [yes]?

What is the name of the second cluster transport adapter (help) [ce1]?

Adapter "ce1" is an Ethernet adapter.

Name of the junction to which "ce1" is connected [switch2]?

Use the default port name for the "ce1" connection (yes/no) [yes]?

到此为止，以上部分没有
[H [J [H [J
  >>> Global Devices File System <<<

Each node in the cluster must have a local file system mounted on
/global/.devices/node@<nodeID> before it can successfully participate
as a cluster member. Since the "nodeID" is not assigned until
scinstall is run, scinstall will set this up for you.

You must supply the name of either an already-mounted file system or
raw disk partition which scinstall can use to create the global
devices file system. This file system or partition should be at least
512 MB in size.

If an already-mounted file system is used, the file system must be
empty. If a raw disk partition is used, a new file system will be
created for you.

The default is to use /globaldevices.

Is it okay to use this default (yes/no) [yes]?

[H [J [H [J
  >>> Automatic Reboot <<<

Once scinstall has successfully installed and initialized the Sun
Cluster software for this machine, it will be necessary to reboot.
The reboot will cause this machine to join the cluster for the first
time.

Do you want scinstall to reboot for you (yes/no) [yes]?

[H [J [H [J
  >>> Confirmation <<<

Your responses indicate the following options to scinstall:

   scinstall -ik \
         -C ourcluster \
         -N sjz-xxml-1 \
         -M patchdir=#cd /cdrom/Solaris_sparc/Product/sun_cluster/Solaris_9/Tools \
         -A trtype=dlpi,name=ce1 -A trtype=dlpi,name=ce2 \
         -m endpoint=:ce1,endpoint=switch1 \
         -m endpoint=:ce2,endpoint=switch2 \


Are these the options you want to use (yes/no) [yes]?

Do you want to continue with the install (yes/no) [yes]?

Checking device to use for global devices file system ... done
Installing patches ... failed

scinstall:  Problems detected during extraction or installation of patches.

Adding node "JDSN-SEC" to the cluster configuration ... done
Adding adapter "ce1" to the cluster configuration ... done
Adding adapter "ce2" to the cluster configuration ... done
Adding cable to the cluster configuration ... done
Adding cable to the cluster configuration ... done

Copying the config from "JDSN-FIR" ... done
Copying the cacao keys from "JDSN-SEC" ... done

Setting the node ID for "JDSN-SEC" ... done (id=2)

Setting the major number for the "did" driver ...
Obtaining the major number for the "did" driver from "JDSN-FIR" ... done
"did" driver major number set to 300

Checking for global devices global file system ... done
Updating vfstab ... done

Verifying that NTP is configured ... done
Installing a default NTP configuration ... done
Please complete the NTP configuration after scinstall has finished.

Verifying that "cluster" is set for "hosts" in nsswitch.conf ... done
Adding the "cluster" switch to "hosts" in nsswitch.conf ... done

Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done
Adding the "cluster" switch to "netmasks" in nsswitch.conf ... done

Verifying that power management is NOT configured ... done
Unconfiguring power management ... done
/etc/power.conf has been renamed to /etc/power.conf.042206104133
Power management is incompatible with the HA goals of the cluster.
Please do not attempt to re-configure power management.

自动重启
Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ...

注意：编辑/etc/inet/ntp.conf.cluster文件，删除其中多余的行节点

Peer clusternode1-priv prefer

Peer clusternode2-priv

安装完第二个节点吼用scshutdown –y –g 10 重新引导所有cluster节点

八、       建立共享磁盘集
①       查看DID设备
# scdidadm -L
1        JDSN-FIR:/dev/rdsk/c0t0d0      /dev/did/rdsk/d1

1 JDSN-SEC:/dev/rdsk/c0t0d0 /dev/did/rdsk/d1

2 JDSN-FIR:/dev/rdsk/c0t1d0 /dev/did/rdsk/d2

2 JDSN-SEC:/dev/rdsk/c0t1d0 /dev/did/rdsk/d2

3 JDSN-FIR:/dev/rdsk/c0t2d0 /dev/did/rdsk/d3

3 JDSN-SEC:/dev/rdsk/c0t2d0 /dev/did/rdsk/d3

4 JDSN-FIR:/dev/rdsk/c0t3d0 /dev/did/rdsk/d4

4 JDSN-SEC:/dev/rdsk/c0t3d0 /dev/did/rdsk/d4

5 JDSN-FIR:/dev/rdsk/c0t4d0 /dev/did/rdsk/d5

5 JDSN-SEC:/dev/rdsk/c0t4d0 /dev/did/rdsk/d5

6 JDSN-FIR:/dev/rdsk/c0t5d0 /dev/did/rdsk/d6

6 JDSN-SEC:/dev/rdsk/c0t5d0 /dev/did/rdsk/d6

7 JDSN-FIR:/dev/rdsk/c0t8d0 /dev/did/rdsk/d7

7 JDSN-SEC:/dev/rdsk/c0t8d0 /dev/did/rdsk/d7

8 JDSN-FIR:/dev/rdsk/c0t9d0 /dev/did/rdsk/d8

8 JDSN-SEC:/dev/rdsk/c0t9d0 /dev/did/rdsk/d8

9 JDSN-FIR:/dev/rdsk/c0t10d0 /dev/did/rdsk/d9

9 JDSN-SEC:/dev/rdsk/c0t10d0 /dev/did/rdsk/d9

10 JDSN-FIR:/dev/rdsk/c0t11d0 /dev/did/rdsk/d10

10 JDSN-SEC:/dev/rdsk/c0t11d0 /dev/did/rdsk/d10

11 JDSN-FIR:/dev/rdsk/c0t12d0 /dev/did/rdsk/d11

11 JDSN-SEC:/dev/rdsk/c0t12d0 /dev/did/rdsk/d11

12 JDSN-FIR:/dev/rdsk/c0t13d0 /dev/did/rdsk/d12

12 JDSN-SEC:/dev/rdsk/c0t13d0 /dev/did/rdsk/d12

13 JDSN-FIR:/dev/rdsk/c1t0d0 /dev/did/rdsk/d13

14 JDSN-FIR:/dev/rdsk/c2t0d0 /dev/did/rdsk/d14

15 JDSN-FIR:/dev/rdsk/c2t1d0 /dev/did/rdsk/d15

16 JDSN-SEC:/dev/rdsk/c1t0d0 /dev/did/rdsk/d16

17 JDSN-SEC:/dev/rdsk/c2t0d0 /dev/did/rdsk/d17

18 JDSN-SEC:/dev/rdsk/c2t1d0 /dev/did/rdsk/d18

② 建立metaset磁盘组

此处，要重新分出c2t0d0s7区，（format，p，p）

Newfs /dev/rdsk/c2t0d0s2
#metadb -a -f -c 3 c2t0d0s7 创建状态数据库副本

（注：以上需在两台主机上分别操作）

# metadb
flags first blk block count

a m p luo 16 8192 /dev/dsk/c2t0d0s7

a p luo 8208 8192 /dev/dsk/c2t0d0s7

a p luo 16400 8192 /dev/dsk/c2t0d0s7
# metaset -s oraset -a -h JDSN-FIR JDSN-SEC （建立设备组oraset）

# metaset –s oraset –a –m JDSN-FIR JDSN-SEC     确定oraset设备组的所属
# metaset –s oraset -t
# metaset

Set name = oraset, Set number = 1

Host             Owner
      JDSN-FIR       yes
      JDSN-SEC
#
③       将共享DID设备加入到oraset组中

# metaset –s oraset –a /dev/did/rdsk/d1 /dev/did/rdsk/2 /dev/did/rdsk/d3 /dev/did/rdsk/d4 /dev/did/rdsk/d5 /dev/did/rdsk/d6 /dev/did/rdsk/d7 /dev/did/rdsk/d8 /dev/did/rdsk/d9 /dev/did/rdsk/d10 /dev/did/rdsk/d11 /dev/did/rdsk/d12（确定oraset设备组包含的原始磁盘）

# metainit oraset/d101 –r /dev/did/rdsk/d1s0 /dev/did/rdsk/d2s0 /dev/did/rdsk/d3s0 /dev/did/rdsk/d4s0 /dev/did/rdsk/d5s0 /dev/did/rdsk/d6s0 /dev/did/rdsk/d7s0 /dev/did/rdsk/d8s0 /dev/did/rdsk/d9s0 /dev/did/rdsk/d10s0 /dev/did/rdsk/d11s0 /dev/did/rdsk/d12s0 (建立从属oraset设备组的raid5卷d101)

建立软分区d100

Metainit –s oraset d100 –p d101 750g
oraset/d100: Soft Partition is setup

编辑挂接文件 /etc/vfstab

/dev/md/oraset/dsk/d100 /dev/md/oraset/rdsk/d100 /oracle ufs 2 yes global

改变挂接点/oracle的所属组和用户

Chown –R oracle:dba /oracle
（注：以上需在两台主机上分别操作）

创建oracle数据库

省略

建立cluter软件监控表

Su – oracle

Sqlplus /nolog

Create user sc_fm/sc_fm

Create session,create table

Select on v_$sysstat

Tablespace users 1 M

Create table mytable (mykey varchar2(10),myval number(10));

Insert into mytable values(‘off’ ,0);

Insert into mytable values(‘on’,1);

注册资源，注册资源前，先使用agent盘，填加数据oracle数据资源（两个机器上做）
** Installing Sun Cluster HA for Oracle **
      SUNWscor....done
      SUNWcscor...done
      SUNWjscor...done
注册以下5种资源

scrgadm –a –t SUNW.HAStorage

scrgadm –a –t SUNW.HAStoragePlus:2

scrgadm –a –t SUNW.nfs:3.1

scrgadm –a –t SUNW.oracle_listener:4

scrgadm –a –t SUNW.oracle_server:4

十五、创建Quorum devices
注：只在JDSN-FIR上操作
# scconf -a -q globaldev=d1

建立资源

1、 scrgadm –a –g ha-ora –h JDSN-FIR,JDSN-SEC (建立资源组 ha-ora)

2、 scrgadm –a –L ha-ora –l JDSN-ORA （建立资源 JDSN-ORA）

3、 scrgadm –a –j hasp-ora –t HAStoragePlus –x FilesystemMountpoints=/oracle –x AffinityOn=true

4、建立服务资源

scrgadm –a –j ora-server-res –g ha-ora –t oracle_server –x Oracle_sid=JDSNWF –x Oracle_Home=/oracle/products/9.2.0.1.0 –x Alert_log_file=/oracle/admin/JDSNWF/bdump/alert_JDSNWF.log -x Parameter_file=/oracle/admin/JDSNWF/pfile/initJDSNWF.ora.24200615525 –x Connect_string=sc_fm/sc_fm

5、建立监听资源

Scrgadm –a –j ora-listener-res –g ha-ora –t oracle_listener –x Oracle_home=/oracle/products/9.2.0.1.0 Listener_name=LISTENER

测试资源组ha-ora切换

# scsetup

使资源启用，使资源组联机

测试资源组切换

Scswitch –z –g ha-ora –h JDSN-SEC

不知道好用不好用

cluster删除。需要先删除具体操作如下:
boot -x
scinstall –r
#rm –rf /etc/cluster/ccr (一定要删除)
rm –r /var/cluster /usr/cluster /etc/cluster
vi /etc/vfstab,将原来所有的dis参数恢复，重建/global/devices –就是将注释#去掉
rm /etc/ntp.conf
vi /etc/nsswitch.conf,除去cluster选项，恢复被注释的file
rm –r /dev/did
rm –f /devices/pseudo/did*