24
DBMS_ORACLE_TRACE_AGENT

The DBMS_ORACLE_TRACE_AGENT package provides some system level utilities.

Security

This package is only accessible to user SYS by default. You can control access to these routines by only granting execute to privileged users.

Summary of Subprograms

This package contains only one subprogram: SET_ORACLE_TRACE_IN_SESSION.

SET_ORACLE_TRACE_IN_SESSION procedure

This procedure collects Oracle Trace data for a database session other than your own. It enables Oracle TRACE in the session identified by (sid, serial#). These value are taken from v$session.

Syntax

DBMS_ORACLE_TRACE_AGENT.SET_ORACLE_TRACE_IN_SESSION ( 
   sid                NUMBER   DEFAULT 0,
   serial#            NUMBER   DEFAULT 0,
   on_off IN          BOOLEAN  DEFAULT false,
   collection_name IN VARCHAR2 DEFAULT '',
   facility_name   IN VARCHAR2 DEFAULT '');

Parameters

Table 24-1 SET_ORACLE_TRACE_IN_SESSION Procedure Parameters

sid

serial#

on_off

collection_name

facility_name

Usage Notes

If the collection does not occur, then check the following:

• Be sure that the server event set file identified by <facility_name> exists. If there is no full file specification on this field, then the file should be located in the directory identified by ORACLE_TRACE_FACILITY_PATH in the initialization file.

• The following files should exist in your Oracle Trace admin directory: REGID.DAT, PROCESS.DAT, and COLLECT.DAT. If they do not, then you must run the OTRCCREF executable to create them.

  Note: PROCESS.DAT was changed to FACILITY.DAT with Oracle8.

• The stored procedure packages should exist in the database. If the packages do not exist, then run the OTRCSVR.SQL file (in your Oracle Trace or RDBMS admin directories) to create the packages.

• The user has the EXECUTE privilege on the stored procedure.

Example

EXECUTE DBMS_ORACLE_TRACE_AGENT.SET_ORACLE_TRACE_IN_SESSION 
(8,12,TRUE,'NEWCOLL','oracled');