VERITAS Storage Foundation 4.1 Oracle Administrator's Guide

Chapter 13, Using the VxDBA Utility
Prerelease 8 September 2005, 8:55am Using VxDBA to Perform Administrative Operations
373
◆ Amount is either a percentage or a value in megabytes by which to grow file systems when the
Grow Threshold is reached or exceeded
The VxDBA Monitoring Agent operations are driven from the following files:
◆ /opt/VRTSdbed/lib/dbed_mon_config.base
◆ /etc/vx/vxdba/$ORACLE_SID/dbed_mon_config.$ORACLE_SID
◆ /etc/vx/vxdba/$ORACLE_SID/dbed_mon_fslist.$ORACLE_SID
◆ /etc/vx/vxdba/$ORACLE_SID/dbed_mon_oralist.$ORACLE_SID
◆ /etc/vx/vxdba/$ORACLE_SID/include
The /opt/VRTSdbed/lib/dbed_mon_config.base file contains the site-level
configuration settings for monitoring all file systems and databases recognized. This configuration
file specifies how often to check for file system and database configuration changes, how often to
check the file space usage, where space usage information gets logged, and the thresholds for
warning and automatically growing the file system. By default, the monitoring agent log file is
located under the /var/log/dbed_mon directory.
During file system and database configuration, the dbed_mon_config.base file gets copied
into each database-specific directory as the file /etc/vx/vxdba/ORACLE_SID
dbed_mon_config.$ORACLE_SID. For example, if you are monitoring a database named
PROD, the database-specific file would be
/etc/vx/vxdba/PROD/dbed_mon_config.PROD. This is the first file opened when the
agent is started and contains the default settings for monitoring file systems at the database level.
The VxDBA Monitoring Agent cannot start without this file. Modify this configuration file if you
want to change the preconfigured settings carried over from the dbed_mon_config.base file
to maintain a different set of settings at the database level.
The following two files:
◆ /etc/vx/vxdba/ORACLE_SID/dbed_mon_fslist.$ORACLE_SID
◆ /etc/vx/vxdba/$ORACLE_SID/dbed_mon_oralist.$ORACLE_SID
are created by the VxDBA utility and are used for restarting the VxDBA Monitoring Agent. These
files specify the status of the database. The files also specify the space monitoring and alarm
information for each file system, tablespace, and datafile. You can edit these files manually to
change settings, and then use VxDBA to restart the Monitoring Agent.
The VxDBA Monitoring Agent uses the /etc/vx/vxdba/$ORACLE_SID/include file to
check that all files are up-to-date and are being monitored. This file is created by the VxDBA utility
and should not be edited.
Occasionally, Monitoring Agents ignore Storage Checkpoints. This happens when a Storage
Checkpoint is not owned by the current Oracle instance. These Storage Checkpoints will not be
used to calculate thresholds and potential removal candidates. Storage Checkpoints that are not
considered part of the current Oracle database instance's data set are logged as such in the file
/var/log/dbed_mon/dbed_mon.prune_ckpt_log.$ORACLE_SID when the