2-2创建并编写程序包控制脚本 
   # cmmakepkg –s /etc/cmcluster/pkg1/pkg1.cntl 
#vi /etc/cmcluster/pkg1/pkg1.cntl 

 

脚本

 

# **********************************************************************

# *                                                                    *

# *        HIGH AVAILABILITY PACKAGE CONTROL SCRIPT (template)         *

# *                                                                    *

# *       Note: This file MUST be edited before it can be used.        *

# *                                                                    *

# **********************************************************************

 

# The PACKAGE and NODE environment variables are set by

# Serviceguard at the time the control script is executed.

# Do not set these environment variables yourself!

# The package may fail to start or halt if the values for

# these environment variables are altered.

 

. ${SGCONFFILE:=/etc/cmcluster.conf}

 

# UNCOMMENT the variables as you set them.

 

# Set PATH to reference the appropriate directories.

PATH=$SGSBIN:/usr/bin:/usr/sbin:/etc:/bin

#注意:按照默认数值就可以了,不要加ORACLE的环境变量

# VOLUME GROUP ACTIVATION:

# Specify the method of activation for volume groups.

# Leave the default ("VGCHANGE="vgchange -a e") if you want volume

# groups activated in exclusive mode. This assumes the volume groups have

# been initialized with 'vgchange -c y' at the time of creation.

#

# Uncomment the first line (VGCHANGE="vgchange -a e -q n"), and comment

# out the default, if your disks are mirrored on separate physical paths,

#

# Uncomment the second line (VGCHANGE="vgchange -a e -q n -s"), and comment

# out the default, if your disks are mirrored on separate physical paths,

# and you want the mirror resynchronization to ocurr in parallel with

# the package startup.

#

# Uncomment the third line (VGCHANGE="vgchange -a y") if you wish to

# use non-exclusive activation mode. Single node cluster configurations

# must use non-exclusive activation.

#

# VGCHANGE="vgchange -a e -q n"

# VGCHANGE="vgchange -a e -q n -s"

# VGCHANGE="vgchange -a y"

VGCHANGE="vgchange -a e"                # Default

#如果是OPS，RAC，那么这里要改动为vgchange -a s,不过需要安装不同的MC版本

# CVM DISK GROUP ACTIVATION:

# Specify the method of activation for CVM disk groups.

# Leave the default

# (CVM_ACTIVATION_CMD="vxdg -g \$DiskGroup set activation=exclusivewrite")

# if you want disk groups activated in the exclusive write mode.

#

# Uncomment the first line

# (CVM_ACTIVATION_CMD="vxdg -g \$DiskGroup set activation=readonly"),

# and comment out the default, if you want disk groups activated in

# the readonly mode.

#

# Uncomment the second line

# (CVM_ACTIVATION_CMD="vxdg -g \$DiskGroup set activation=sharedread"),

# and comment out the default, if you want disk groups activated in the

# shared read mode.

#

# Uncomment the third line

# (CVM_ACTIVATION_CMD="vxdg -g \$DiskGroup set activation=sharedwrite"),

# and comment out the default, if you want disk groups activated in the

# shared write mode.

#

# CVM_ACTIVATION_CMD="vxdg -g \$DiskGroup set activation=readonly"

# CVM_ACTIVATION_CMD="vxdg -g \$DiskGroup set activation=sharedread"

# CVM_ACTIVATION_CMD="vxdg -g \$DiskGroup set activation=sharedwrite"

CVM_ACTIVATION_CMD="vxdg -g \$DiskGroup set activation=exclusivewrite"

 

# VOLUME GROUPS

# Specify which volume groups are used by this package. Uncomment VG[0]=""

# and fill in the name of your first volume group. You must begin with

# VG[0], and increment the list in sequence.

#

# For example, if this package uses your volume groups vg01 and vg02, enter:

#         VG[0]=vg01

#         VG[1]=vg02

#

# The volume group activation method is defined above. The filesystems

# associated with these volume groups are specified below.

#

VG[0]=vgdata1

VG[1]=vgdata2

注意:程序包需要几个vg,就加几个vg（数据VG。LOCK VG不用加入）

# CVM DISK GROUPS

# Specify which cvm disk groups are used by this package. Uncomment

# CVM_DG[0]="" and fill in the name of your first disk group. You must

# begin with CVM_DG[0], and increment the list in sequence.

#

# For example, if this package uses your disk groups dg01 and dg02, enter:

#         CVM_DG[0]=dg01

#         CVM_DG[1]=dg02

#

# The cvm disk group activation method is defined above. The filesystems

# associated with these volume groups are specified below in the CVM_*

# variables.

#

#CVM_DG[0]=""

 

# VxVM DISK GROUPS

# Specify which VxVM disk groups are used by this package. Uncomment

# VXVM_DG[0]="" and fill in the name of your first disk group. You must

# begin with VXVM_DG[0], and increment the list in sequence.

#

# For example, if this package uses your disk groups dg01 and dg02, enter:

#         VXVM_DG[0]=dg01

#         VXVM_DG[1]=dg02

#

# The cvm disk group activation method is defined above.

#

#VXVM_DG[0]=""

 

#

# NOTE: A package could have LVM volume groups, CVM disk groups and VxVM

#       disk groups.

#

# NOTE: When VxVM is initialized it will store the hostname of the

#       local node in its volboot file in a variable called 'hostid'.

#       The Serviceguard package control scripts use both the values of

#       the hostname(1m) command and the VxVM hostid. As a result

#       the VxVM hostid should always match the value of the

#       hostname(1m) command.

#

#       If you modify the local host name after VxVM has been

#       initialized and such that hostname(1m) does not equal uname -n,

#       you need to use the vxdctl(1m) command to set the VxVM hostid

#       field to the value of hostname(1m). Failure to do so will

#       result in the package failing to start.

 

# VOLUME GROUP AND DISK GROUP DEACTIVATION RETRY COUNT

# Specify the number of deactivation retries for each disk group and volume

# group at package shutdown. The default is 0.

DEACTIVATION_RETRY_COUNT=0

 

 

# RAW DEVICES

# If you are using raw devices for your application, this parameter allows

# you to specify if you want to kill the processes that are accessing the

# raw devices at package halt time. If raw devices are still being accessed

# at package halt time, volume group or disk group deactivation can fail,

# causing the package halt to also fail. This problem usually happens when

# the application does not shut down properly.

# Note that if you are using Oracle's Cluster Ready Service, killing this

# service could cause the node to reboot.

# The legal values are "YES" and "NO". The default value is "NO".

# The value that is set for this parameter affects all raw devices associated

# with the LVM volume groups and CVM disk groups defined in the package.

KILL_PROCESSES_ACCESSING_RAW_DEVICES="NO"

 

 

# FILESYSTEMS

# Filesystems are defined as entries specifying the logical volume, the

# mount point, the mount, umount and fsck options and type of the file system.

# Each filesystem will be fsck'd prior to being mounted. The filesystems

# will be mounted in the order specified during package startup and will

# be unmounted in reverse order during package shutdown. Ensure that

# volume groups referenced by the logical volume definitions below are

# included in volume group definitions above.

#

# Specify the filesystems which are used by this package. Uncomment

# LV[0]=""; FS[0]=""; FS_MOUNT_OPT[0]=""; FS_UMOUNT_OPT[0]=""; FS_FSCK_OPT[0]=""

# FS_TYPE[0]="" and fill in the name of your first logical volume,

# filesystem, mount, umount and fsck options and filesystem type

# for the file system. You must begin with LV[0], FS[0],

# FS_MOUNT_OPT[0], FS_UMOUNT_OPT[0], FS_FSCK_OPT[0], FS_TYPE[0]

# and increment the list in sequence.

#

# Note: The FS_TYPE parameter lets you specify the type of filesystem to be

# mounted. Specifying a particular FS_TYPE will improve package failover time.

# The FSCK_OPT and FS_UMOUNT_OPT parameters can be used to include the

# -s option with the fsck and umount commands to improve performance for

# environments that use a large number of filesystems. (An example of a

# large environment is given below following the decription of the

# CONCURRENT_MOUNT_AND_UMOUNT_OPERATIONS parameter.)

#

# Example: If a package uses two JFS filesystems, pkg01a and pkg01b,

# which are mounted on LVM logical volumes lvol1 and lvol2 for read and

# write operation, you would enter the following:

#      LV[0]=/dev/vg01/lvol1; FS[0]=/pkg01a; FS_MOUNT_OPT[0]="-o rw";

#      FS_UMOUNT_OPT[0]=""; FS_FSCK_OPT[0]=""; FS_TYPE[0]="vxfs"

#

#      LV[1]=/dev/vg01/lvol2; FS[1]=/pkg01b; FS_MOUNT_OPT[1]="-o rw"

#      FS_UMOUNT_OPT[1]=""; FS_FSCK_OPT[1]=""; FS_TYPE[1]="vxfs"

#

LV[0]=/dev/vgdata1/lvdata1; FS[0]=/oradata1; FS_MOUNT_OPT[0]="-o rw,largefiles";

FS_UMOUNT_OPT[0]=""; FS_FSCK_OPT[0]=""; FS_TYPE[0]="vxfs"

LV[1]=/dev/vgdata2/lvdata1; FS[1]=/oralog1; FS_MOUNT_OPT[1]="-o rw,largefiles";

FS_UMOUNT_OPT[1]=""; FS_FSCK_OPT[1]=""; FS_TYPE[1]="vxfs"

请注意：LV是名字 ，FS是卷名字 FS_MOUNT_OPT 如果没有大于2GB的大文件，则不用加largefiles，FS_TYPE 文件系统类型。

#:如果是裸设备安装的ORACLE,不需要有上面lv, mount点的设置.这个情况说明ORACLE是建立在HP-UX文件系统上的,

# VOLUME RECOVERY

#

# When mirrored VxVM volumes are started during the package control

# bring up, if recovery is required the default behavior is for

# the package control script to wait until recovery has been

# completed.

#

# To allow mirror resynchronization to ocurr in parallel with

# the package startup, uncomment the line

# VXVOL="vxvol -g \$DiskGroup -o bg startall" and comment out the default.

#

# VXVOL="vxvol -g \$DiskGroup -o bg startall"

VXVOL="vxvol -g \$DiskGroup startall"      # Default

 

# FILESYSTEM UNMOUNT COUNT

# Specify the number of unmount attempts for each filesystem during package

# shutdown.  The default is set to 1.

FS_UMOUNT_COUNT=1

#注意:按照默认数值

# FILESYSTEM MOUNT RETRY COUNT.

# Specify the number of mount retrys for each filesystem.

# The default is 0. During startup, if a mount point is busy

# and FS_MOUNT_RETRY_COUNT is 0, package startup will fail and

# the script will exit with 1.  If a mount point is busy and

# FS_MOUNT_RETRY_COUNT is greater than 0, the script will attempt

# to kill the user responsible for the busy mount point

# and then mount the file system.  It will attempt to kill user and

# retry mount, for the number of times specified in FS_MOUNT_RETRY_COUNT.

# If the mount still fails after this number of attempts, the script

# will exit with 1.

# NOTE: If the FS_MOUNT_RETRY_COUNT > 0, the script will execute

# "fuser -ku" to freeup busy mount point.

FS_MOUNT_RETRY_COUNT=0

 

#

# Configuring the concurrent operations below can be used to improve the

# performance for starting up or halting a package.  The maximum value for

# each concurrent operation parameter is 1024.  Set these values carefully.

# The performance could actually decrease if the values are set too high

# for the system resources available on your cluster nodes.  Some examples

# of system resources that can affect the optimum number of concurrent

# operations are: number of CPUs, amount of available memory, the kernel

# configuration for nfile and nproc. In some cases, if you set the number

# of concurrent operations too high, the package may not be able to start

# or to halt.  For example, if you set CONCURRENT_VGCHANGE_OPERATIONS=5

# and the node where the package is started has only one processor, then

# running concurrent volume group activations will not be beneficial.

# It is suggested that the number of concurrent operations be tuned

# carefully, increasing the values a little at a time and observing the

# effect on the performance, and the values should never be set to a value

# where the performance levels off or declines.  Additionally, the values

# used should take into account the node with the least resources in the

# cluster, and how many other packages may be running on the node.

# For instance, if you tune the concurrent operations for a package so

# that it provides optimum performance for the package on a node while

# no other packages are running on that node, the package performance

# may be significantly reduced, or may even fail when other packages are

# already running on that node.

#

# CONCURRENT VGCHANGE OPERATIONS

# Specify the number of concurrent volume group activations or

# deactivations to allow during package startup or shutdown.

# Setting this value to an appropriate number may improve the performance

# while activating or deactivating a large number of volume groups in the

# package. If the specified value is less than 1, the script defaults it

# to 1 and proceeds with a warning message in the package control script

# logfile.