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

It is advisable to copy the default scripts to a working directory before deploying
them into the ${ORACLE_BASE}/admin/<DBNAME>/scripts directory. Once
you are ready to deploy your custom scripts, simply move them into the
${ORACLE_BASE}/admin/<DBNAME>/scripts directory and the next probe
cycle will use the scripts—if the Virtual Oracle Service is already running. The
mxdb_probe.sql script is well documented with pointers on where to place any
desired custom probe actions.
Support of custom start/stop and probe scripts
Support for custom start/stop and probe scripts is limited to the infrastructure that
calls the custom scripts. Customers assume responsibility for custom start/stop and
probe actions since there is an endless amount of functionality that can be placed
into a custom script.
Security with custom start/stop and probe scripts
Care should be taken to ensure that modification privileges are limited on the custom
start/stop and probe scripts. Whereas the default scripts included with
MxDB-Oracle-HiAv reside in a directory writable only by root, custom scripts reside
under ${ORACLE_BASE}/admin. It is possible that DBA's without the intended level
of security may impact a Virtual Oracle Service that uses custom scripts—whether
intentionally or unintentionally—by modifying or deleting these scripts.
Custom probes and probe timeouts
If significant probe actions are added to a custom probe, it may be necessary to
increase the value of the MxDB_PROBE_CORE_TIMEOUT parameter (see
MxDB-Oracle-HiAv configuration file, page 23). This parameter is used by
MxDB-Oracle-HiAv to limit the tolerance for a long-running SQL*Plus session executing
as a part of the probe. It is, in essence, the amount of time allotted to your custom
probe actions before MxDB-Oracle-HiAv considers your probe actions stalled. The
default probe actions are very light so the default setting of this parameter is 20
seconds. If significant actions are added to a custom probe, this value must be set
to accommodate the extra processing time. Ultimately, the value assigned to this
parameter cannot exceed the total probe timeout, which is 190 seconds by default.
Because the probe core—the actions executed in the mxdb_probe.sql script—are
only a portion of the overall activity during a probe, it is not permissible to set
MxDB_PROBE_CORE_TIMEOUT to the total probe timeout associated with the Virtual
Oracle Service. The total probe timeout can be adjusted via the HP Scalable NAS
Configuration and Operations56