A
Components of Oracle Trace

The Oracle Trace components include files, images, processes, and interfaces. The relationships between these components are shown in Figure A-1.

Files

Oracle Trace uses several files to manage data collections. The formats of these files are internal. All access to files is performed by Oracle Trace on behalf of the user.

$ORACLE_HOME/otrace/admin/process.dat

describes which processes are available to participate in collections (process.dat has been renamed to facility.dat in Oracle8)

$ORACLE_HOME/otrace/admin/collect.dat

describes active collections

$ORACLE_HOME/otrace/admin/regid.dat

describes registration IDs associated with processes. See Chapter 4, Advanced Topics, for information on registration IDs.

$ORACLE_HOME/otrace/admin/fdf/<product >.fdf

product definition file that describes the data that can be collected for an application

$ORACLE_HOME/otrace/admin/<product>.phd

product hierarchy definition file that describes relationships between events

$ORACLE_HOME/otrace/admin/cdf/<collection name>.cdf

collection definition file that describes a collection

$ORACLE_HOME/otrace/admin/cdf/<collection name>.dat

data collection file that contains event data

Images

Oracle Trace installs the following images:

$ORACLE_HOME/bin/otrccol

command-line interface for managing collections

$ORACLE_HOME/bin/otrccref

creates Oracle Trace administrative files

process.dat
collect.dat
regid.dat

$ORACLE_HOME/bin/otrcfmt

formats collected data into an Oracle database

$ORACLE_HOME/bin/otrcrep

produces formatted text output of collected data

Processes

Oracle Trace does not have any dedicated processes. Any process running an application instrumented with the Oracle Trace API can participate in an Oracle Trace collection. The application uses the API to call the Oracle Trace collection services that perform all access to the Oracle Trace files.