HP OpenView Operations Administrator's Reference - filibeto.org

Maintaining a Database
Maintaining OVO
Maintaining a Database
To ensure that your OVO database runs efficiently, you should perform
the following tasks periodically:
❏ Download History Messages and Audit Information
Download history messages and audit information using the
Database Maintenance window. To restore previously backed up
history messages or audit information, see the man page
opchistupl(1m) or opcaudupl(1m).
❏ Back up the OVO Configuration
Back up the OVO configuration regularly. For details, see “Backing
up Data on the Management Server” on page 524.
❏ Move Messages into the History Database
If a very large number of messages have been produced (for example,
by an inappropriately configured template), operators may find that
their Message Browser takes a long time to open. In this case, as
user root, use the command-line utilities opcack or opcackmsg to
acknowledge these messages and move them to the history database.
For details, see the opcack(1m) and opcackmsg(1m) man pages.
❏ Add Disks
The OVO database files automatically consume the extra disk space
required to cope with any growth. If a disk runs out of space, you can
use other disks to add additional files for a tablespace. For details,
see the Oracle information.
❏ Review Audit Files
Every time a user runs the command connect internal, Oracle
adds an audit file to the directory $ORACLE_HOME/rdbms/audit.
Because the monitor template mondbfile runs the connect
internal command roughly every ten minute, you should review the
files in this directory regularly and, if necessary, remove them.
Chapter 13 537