3.1.1 MxDB-Oracle-HiAv Installation and Administration Guide

Chapter 3: Operations 44

• Naming Convention. The naming convention for a supplemental

script is as follows:

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

of the Solution Pack (i.e., /opt/polyserve/mxdb_oracle_ha/etc).

– 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 the Solution

Pack.

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

After implementing these steps, the Intelligent Agent will be started each

time the PILOT database is started.

The sample script can be renamed to support starting the Intelligent

Agent for any database under Solution Pack control.

Add Code to the Supplemental Script

It is completely up to the administrator to determine any other

supplemental startup code that should be implemented in the script.

Provided the code can execute with the above listed caveats, the script

will perform satisfactorily.