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

probe logging information to a local directory. However, to aid in administration, it
also sends log messages to a central log in the PSFS cluster filesystem.
The system-level logs are placed in /var/log/hpcfs and are named
SPACK_ORACLE.<DBNAME>-<type>.log, where DBNAME is the name specified
when the Virtual Oracle Service is created. type is either start, stop, recovery, or
probe. Generally, these logs are used only by HP Support.
For 10g databases, the central log is placed in $ORACLE_BASE/admin under the
<DBNAME>/bdump subdirectory using the name MxDBHA_<DBNAME>.log. For 11g
databases, the dbump subdirectory has been replaced (unless directly specified). If
the bdump subdirectory does not exist, the central log for the 11g database will
located in $ORACLE_HOME/rdbms/admin using the same name. The DBA can
override this logging location by setting the log parameter in the MxDB-Oracle-HiAv
configuration file. For example:
$ cat $ORACLE_HOME/dbs/mxdbha_PROD.conf
log /u01/app/oracle/product/10.2.0/rdbms/log
The GUI will also log activity in /tmp/MxDB-Oracle-HiAv.log on the system fro
which the GUI is run.
Service loss
MxDB-Oracle-HiAv considers a Virtual Oracle Service to be in a down state if the
probe returns a failure or times out. If a database cannot satisfy the rudimentary
checks performed by the default MxDB-Oracle-HiAv probe script (mxdb_probe.sql),
there is likely something very wrong with the instance. The default action taken by
MxDB-Oracle-HiAv is to reboot the instance. If this action is not acceptable for your
application, there are two options: tune the probe timeout or change the probe
actions. (A customer-supplied mxdb probe SQL is allowed.) See Custom Virtual Oracle
Service start/stop and probe scripts, page 54 for more information.
SQL*Net security with Virtual Oracle Services
MxDB-Oracle-HiAv implements listener security. By default, the listener password is
taken from the /opt/hpcfs/mxdb_oracle_ha/lib/lsnr_passwd_def.txt
file in the product installation directory. The DBA can override this default by assigning
a legal value to the lsnr_password parameter in the MxDB-Oracle-HiAv configuration
file.
For example:
Configuration and Operations24