HP Serviceguard Toolkit for Oracle Version A.05.01.01 on Linux User Guide (December, 2012)

6. Apply the package configuration using the command:
# cmapplyconf -P pkg2.conf
7. Start the "oracle_pkg" package using the command:
#cmrunpkg oracle_pkg
Configuring legacy ASM instance and Database instance packages
To configure a legacy ASM instance package:
1. Setting up and configuring ASM multi-node package.
a. Create an ASM package directory under $SGCONF/<package dir>.
b. Copy the toolkit scripts from $SGROOT/oracletoolkit to the directory created in step
1a.
c. cd $SGCONF/<package dir>.
d. Edit the toolkit configuration file, haoracle.conf. Table 4 (page 23) lists the attributes
that you can edit.
Table 4 Lists the attributes that you can edit
ExampleDescriptionAttribute Name
ASMThis parameter determines whether
the instance is an ASM instance
INSTANCE_TYPE
or a database instance. Set this
parameter to ASM. The default
value is ASM.
/ORACLE_TEST0This is the base directory where
Oracle is installed.
ORACLE_HOME
ORACLE_TEST0The Oracle session name. It is also
called the session ID (SID). It
SID_NAME
SID_NAME uniquely identifies an
Oracle database instance. NOTE:
If you modify this attribute after the
# cmmakepkg -i -m -t
command is run, you must
reconfigure the
MONITOR_PROCESSES attribute
defined in this file to reflect the
same. Also, reconfigure PFILE
attribute defined in this file to
reflect this change, if PFILE is using
this attribute.
/ASM_TEST0The home directory where ASM is
installed.
ASM_HOME
oracleThe user name of the Oracle ASM
administrator. It is used to start or
ASM_USER
stop the ASM instance and
mounting or dismounting the ASM
disk groups. The default value is
oracle.
+ASMThe ASM session name. This
uniquely identifies an ASM
instance.
ASM_SID
Configuring legacy and modular Oracle ASM instance and Database instance toolkit packages 23