3.5.1 MxDB-Oracle-HiAv Installation and Administration Guide

Chapter 2: Operations 47

should not be a concern because any process spawned by the

supplemental script will likely be daemon in nature (e.g., Intelligent

Agents). That is, spawning daemon processes such as the Intelligent

Agent is a nearly immediate task.

•

SHELL. Supplemental scripts will be interpreted by the bash shell.

• Execution Environment. The supplemental script is executed with the

Linux su(1) command, switching user to the Oracle user that was

established at configuration time with the Configuration GUI. The

su(1) command is not invoked with the full login option. The

invocation method is as follows:

/bin/su - ${ORACLE_OWNER} -c "ORACLE_SID=${DBNAME};bash

${PRODHOME}/etc/custom_${DBNAME}.sh\ [start|stop]"

• Naming Convention. The naming convention for a supplemental

script is as follows:

– Path. Supplemental startup scripts are located in the etc directory

of MxDB-Oracle-HiAv (i.e., /opt/polyserve/mxdb_oracle_ha/etc). You

may have to create this subdirectory.

– Script Name. There is only one supplemental script per database.

The script is named custom_

${ORACLE_SID}.sh.

• Permissions. The execution bit must be set on supplemental scripts.

This can be done with the chmod command, such as:

# chmod 755 /opt/polyserve/mxdb_oracle_ha/etc/custom_PILOT.sh

To aid in implementing a supplemental script, MxDB-Oracle-HiAv ships

with a fully functional sample script that starts the Intelligent Agent. This

sample script is ready for the

PILOT database and is called

custom_

PILOT.sh.sample. It is located in the lib directory of

MxDB-Oracle-HiAv.

To test the supplemental startup of the Intelligent Agent for the

PILOT

database, simply copy this script into the etc directory of the product,

omitting the .sample suffix, and set the execution bit.

# cd /opt/polyserve/mxdb_oracle_ha/lib

# cp custom_PILOT.sh.sample /opt/polyserve/mxdb_oracle_ha/etc/custom_PILOT.sh

# chmod 755 /opt/polyserve/mxdb_oracle_ha/etc/custom_PILOT.sh