3.7.0 HP StorageWorks MxDB-Oracle-HiAv installation and administration guide HP MxDB-Oracle-HiAv for Linux (AG513-96009, June 2009)

CLI or Management Console as described in the HP Scalable NAS File Serving

Software administration guide.

Supplemental startup scripts

MxDB-Oracle-HiAv supports supplemental startup and shutdown scripts that are

customized at your site. MxDB-Oracle-HiAv ensures that the database instance and

SQL*Net listener processes are available in the cluster. You might also want

supplemental processes to be started and stopped each time the database is restarted

or failed over to another node. For example, if you want the Intelligent Agent to start

each time the database instance is started, a supplemental script is required.

Configuring a supplemental startup script is a simple administrative task. However,

the functionality of the script is the responsibility of the administrator. That is,

MxDB-Oracle-HiAv will call the script, but it cannot ensure that the script will succeed

because the code is site-customized. To that end, MxDB-Oracle-HiAv treats the

execution of the supplemental script with the following caveats:

• Return Codes. The supplemental script can return success or failure codes; however,

MxDB-Oracle-HiAv ignores them. This ensures that the database instance and

SQL*Net listeners start even if the supplemental script fails.

• Timeout. The supplemental startup script is allocated a maximum of 20 seconds

execution. If the supplemental script is still executing code after 20 seconds, it

will be terminated by MxDB-Oracle-HiAv. This 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 Intelli-

gent 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 command is not invoked with the full

/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 /opt/hpcfs/mxdb_or-

acle_ha/etc). You may need to create this subdirectory.

• Script Name. There is only one supplemental script per database. The script

is named custom_${ORACLE_SID}.sh.

MxDB-Oracle-HiAv installation and administration guide 57