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

shops vary widely in their usage of the product. To that end, it is nearly impossible
to provide a default set of start, stop and probe scripts that meet the needs of all
sites. For instance, it may be desirable to have probe actions that ensure access to
a specific application table or to send a message to a DBA based on certain criteria.
To address this issue, MxDB-Oracle-HiAv supports the concept of site-specific start,
stop and probe scripts. (See the section “Custom scripts” in Chapter 20, “Advanced
monitor topics,” in the HP Scalable NAS File Serving Software administration guide
for more information about these scripts.)
There is an existing framework into which custom start/stop and probe scripts must
integrate. The following rules apply:
• To implement custom start/stop and probe scripts, you must place a copy of the
four default scripts into the scripts subdirectory under the common OFA location
of ${ORACLE_BASE}/admin/<DBNAME>/scripts. Use these scripts as the
template to add your site-specific actions.
• The custom scripts must satisfy the high-level HP Scalable NAS high-availability
engine requirements pertaining to return values. (The requirements are defined
under “Custom scripts” in the HP Scalable NAS File Serving Software administra-
tion guide.)
To prepare for custom start/stop and probe script deployment, if necessary create
and then cd to the ${ORACLE_BASE}/admin/<DBNAME>/scripts directory.
Next, copy the default scripts from the product as follows:
$ cd ${ORACLE_BASE}/admin/${ORACLE_SID}/scripts
$ cp /opt/hpcfs/mxdb_oracle_ha/lib/mxdb_*.sql .
$ ls -l mxdb*
-rwxr-xr-x 1 oracle oinstall 93 Apr 13 11:43 mxdb_abort.sql
-rwxr-xr-x 1 oracle oinstall 97 Apr 13 11:43 mxdb_immediate.sql
-rwxr-xr-x 1 oracle oinstall 690 Apr 13 11:43 mxdb_probe.sql
-rwxr-xr-x 1 oracle oinstall 124 Apr 13 11:43 mxdb_start.sql
$ pwd
/u01/app/oracle/admin/PROD/scripts
The probe script is the most sensitive to this framework. Custom probe scripts must
return the proper textual feedback to the higher-level HP Scalable NAS high
availability engine. A successful probe must return two critical tokens indicating the
database role and state. The tokens are either “PRIMARY” and “OPEN” or
“STANDBY” and “MOUNTED.” These text values are naturally returned from select
statements executed against the internal V$ views of the database. The default probe
script (mxdb_probe.sql) already includes this infrastructure.
Be advised that copying the mxdb_probe.sql script to the ${ORACLE_BASE}/
admin/<DBNAME>/scripts directory will cause the scripts to go into immediate
use if there is a Virtual Oracle Service for that database executing.
MxDB-Oracle-HiAv installation and administration guide 55