Oracle Enterprise Manager Oracle Trace Developer's Guide
Release 1.4.0
A53697_01

Library

Product

Contents

Index


Prev Next

D
Oracle Trace Format Database

This appendix describes the format database that Oracle Trace creates. To generate reports of the information in the database, you can use Developer/2000, Oracle Rally, or any other tool capable of accessing Oracle databases.

Oracle Server

The following sections describe the datatypes that the Oracle Server uses to represent the datatypes supported by Oracle Trace. Also described are the tables in the database. The tables hold two types of data:

These tables are created using the vobsh command.

Oracle Trace Supported Datatypes

Table D-1 shows the Oracle representations of datatypes supported by Oracle Trace.

Table D-1 Oracle Representations of Datatypes Supported by Oracle Trace
Datatype Supported by Oracle Trace   Oracle Datatype  

UNSIGNED BYTE  

NUMBER  

UNSIGNED 2 BYTES  

NUMBER  

UNSIGNED 4 BYTES  

NUMBER  

UNSIGNED 8 BYTES  

NUMBER  

ASCIC  

VARCHAR2  

FIXED_ASCIC  

VARCHAR2  

ASCIW  

VARCHAR2 if less than 2000 characters. Otherwise, the datatype is LONG. There can only be one item per table with a datatype of LONG.  

ASCIL  

VARCHAR2 if less than 2000 characters. Otherwise, the datatype is LONG. There can only be one item per table with a datatype of LONG.  

Tables for Control Information

The tables described in this section show hold control information. Table D-2 maps the table names with their respective table number.

Note:

In previous versions of Oracle Trace, `product' was called `facility.'  

Table D-2 List of Tables Holding Control Information
Table Name   Described in...  

epc_collection  

Table D-3  

epc_process  

Table D-4  

epc_facility  

Table D-5  

epc_event  

Table D-6  

epc_item  

Table D-7  

epc_event_item  

Table D-8  

epc_facility_registration  

Table D-9  

For each table, the datatype and size (if appropriate) of each column is provided, as well as a brief description of the column. Primary keys are in italics.

Table D-3 shows the Collection table (epc_collection).

Table D-3 Collection Table
Column Name   Datatype (Size)   Description  

collection_id  

NUMBER (4)  

The collection ID number, incremented by 1 each time the collection is formatted  

coll_name  

VARCHAR2 (255)  

Collection name  

start_time  

DATE  

Collection start time  

end_time  

DATE  

Collection end time  

scheduled_by  

VARCHAR2 (8)  

Name of the user who scheduled the collection  

Table D-4 shows the Process table (epc_process).

Table D-4 Process Table
Column Name   Datatype (Size)   Description  

collection_id  

NUMBER (4)  

The collection ID number, incremented by 1 each time the collection is formatted  

epid  

NUMBER (9)  

Process ID for the collection  

username  

VARCHAR2 (8)  

Username attached to the process  

cpu_type  

VARCHAR2 (32)  

CPU type on which the process is running  

os_ver  

VARCHAR2 (32)  

Operating system version  

nodename  

VARCHAR2 (64)  

Node on which the process is running  

time  

DATE  

The time at which the process became active  

time_nano  

NUMBER  

Nanoseconds of the time at which the process became active  

end_time  

DATE  

The time at which the process ended  

Table D-5 shows the Product table (epc_facility).

Table D-5 Product Table
Column Name   Datatype (Size)   Description  

facility_number  

NUMBER (4)  

The product number  

facility_name  

VARCHAR2 (20)  

The product name  

facility_version  

VARCHAR2 (11)  

The product version  

class_name  

VARCHAR2 (20)  

The class name  

vendor  

NUMBER  

The vendor ID  

Table D-6 shows the Event table (epc_event).

Table D-6 Event Table
Column Name   Datatype (Size)   Description  

facility_number  

NUMBER (4)  

The product number  

facility_version  

VARCHAR2 (11)  

The product version  

event_number  

NUMBER (4)  

The event number  

event_name  

VARCHAR2 (16)  

The event name  

event_header  

VARCHAR2 (16)  

The name of the event as printed in the report header  

event_table_name  

VARCHAR2 (30)  

The name of the event table. See "Tables for Collected Event Data" for a description of how the name is derived.  

vendor  

NUMBER  

The vendor ID  

Table D-7 shows the Item table (epc_item).

Table D-7 Item Table
Column Name   Datatype (Size)   Description  

facility_number  

NUMBER (4)  

The product number  

facility_version  

VARCHAR2 (11)  

The product version  

item_number  

NUMBER (4)  

The item number  

item_name  

VARCHAR2 (16)  

The item name  

item_header  

VARCHAR2 (16)  

The name of the item as printed in the report header  

item_width  

NUMBER  

The width of the report column  

item_size  

NUMBER  

The maximum size of the item, in bytes  

item_char  

NUMBER  

Bit values. A value of 0 means that none of the bits are set (items are printed and CRLFs are interpreted).

A value of 1 means that items are not printed.

A value of 2 means that CRLFs are not interpreted.

A value of 3 means that items are not printed and CRLFs are not interpreted.  

vendor  

NUMBER  

The vendor ID  

Table D-8 shows the Event_Item table (epc_event_item).

Table D-8 Event_Item Table
Column Name   Datatype (Size)   Description  

facility_number  

NUMBER (4)  

The product number  

facility_version  

VARCHAR2 (11)  

The product version  

event_number  

NUMBER (4)  

The event number  

event_type  

NUMBER (2)  

The event type  

item_number  

NUMBER (4)  

The item number  

item_position  

NUMBER  

Position of the item in the user's data buffer  

vendor  

NUMBER  

The vendor ID  

Table D-9 shows the Product Registration table (epc_facility_registration).

Table D-9 Product_Registration Table
Column Name   Datatype (Size)   Description  

collection_id  

NUMBER (4)  

The collection ID number, incremented by 1 each time the collection is formatted  

epid  

NUMBER (8)  

The process ID  

timestamp  

DATE  

The time at which a record is written to the collection file  

timestamp_nano  

NUMBER  

Nanoseconds of timestamp  

reg_id_string  

VARCHAR2 (256)  

The registration string  

facility_version  

VARCHAR2 (11)  

The product version  

facility_number  

NUMBER  

The product version  

vendor  

NUMBER  

The vendor ID  

Tables for Collected Event Data

A table for event data is created only if data has been collected for the event. The name for an event data table is derived using the following formula: v_vendor#_f_product#_e_event#_facver. Any periods in the product version are replaced with underscores.

For a point event data table, the item name is used as the column name in the table.

For a duration event data table, the suffixes _START and _END are added to the item names for items that are collected at event start time and event end time, respectively.

For example, an item named cpu_time has a column name of cpu_time in a point event data table. A similar item has a column name of cpu_time_start for data collected at event start time. A similar item has a column name of cpu_time_end for data collected at event end time.

In addition to product-defined events and process items, all event tables also include the columns described in Table D-10.

Table D-10 Event Table Columns
Column Name   Datatype (Size)   Description  

collection_id  

NUMBER (4)  

The collection number, automatically assigned by the formatter  

timestamp  

DATE  

Point event logged time, for point events only  

timestamp_nano  

NUMBER  

Nanoseconds of point events  

timestamp_start  

DATE  

Duration event start time, for duration events only  

timestamp_start_nano  

NUMBER  

Nanoseconds of duration event start time  

timestamp_end  

DATE  

Duration event end time, for duration events only  

timestamp_end_nano  

NUMBER  

Nanoseconds of duration event end time  

epid  

NUMBER (8)  

The process ID number  




Prev

Next
Oracle
Copyright © 1997 Oracle Corporation.
All Rights Reserved.

Library

Product

Contents

Index