HP OpenView Operations Administrator's Reference - filibeto.org

Tuning and Troubleshooting OVO
Solving Problems with the Embedded Performance Component
460
On DCE-based managed nodes, you can also use the opcragt command
to start and stop coda from remote, for example:
/opt/OV/bin/OpC/opcragt -start -id 12
In this instance, is the node on which the embedded
performance component process is to be started.
For more information about the commands ovc(1), opcagt(1M), and
opcragt(1M), see their corresponding man pages.
Database Storage
The collected values are stored in a proprietary persistent data store
from which they are retrieved and transformed into presentation values.
The presentation values can be used by extraction, visualization, and
analysis tools such as HP OpenView Reporter and HP OpenView
Performance Manager. See the documentation of these products for
details.
You cannot extract/export, view, or aggregate the data directly on the
managed node. The database has a fixed size, and cannot be controlled,
or configured. The database files on the managed nodes are stored in the
directories listed in Table 11-4:
❏ coda.db
The file coda.db contains database information. It is internal to the
embedded performance component and cannot be viewed directly by
users.
❏ coda
The file coda is the storage file which contains the raw
performance data. A new storage file is created weekly. For example,
coda00000 is the first storage file. coda00001 is the one created on
the following Sunday. The embedded performance component stores
a maximum of five (5) weeks data. The oldest storage file is deleted
every five (5) weeks.
Chapter 11