The applicable Oracle versions are 9.2.0.8 and 10.2.x under Solaris. The
"why" is I am working in a development environment supporting a large number
of system builds with simultaneous testing across various builds. I use
10046 tracing along with the Hotsos Profiler and various internal tools to
examine how changes in upper tiers of our system are reflected in the
database. All tracing is controlled from a single privileged Oracle
account. Trace files may be generated during simultaneous testing of
multiple system builds. Our use of connection pooling means a given test
may generate 10 to 20 Oracle trace files. I need an efficient way to
distinguish which trace files match which system builds. I will investigate
DBMS_MONITOR and oradebug. If I find a clean solution, I will post a
follow-up. Thanks!
On 5/16/07, Niall Litchfield <niall.litchfield_at_gmail.com> wrote:
>
> I'd be asking the why and what version question at this point - it's
> entirely possible that a combination of DBMS_MONITOR and trcsess in 10g will
> help you.
>
> That all said using oradebug to attach to the process gives you the
> ability to determine (but not set I think) the current tracefile name.
>
> On 5/15/07, Andrew Zitelli <azitelli_at_gmail.com> wrote:
> >
> > Is there an easy way to set a tracefile identifier when tracing someone
> > else's session? To trace my own session I simply use something like:
> > alter session set tracefile_identifier='ANDY';
> >
> > The package DBMS_SYSTEM provides procedures SET_BOOL_PARAM_IN_SESSION
> > and SET_INT_PARAM_IN_SESSION but nothing like SET_VARCHAR_PARAM_IN_SESSION.
> > I have looked a bit on the web but have not found an answer for this. Is it
> > possible?
> >
> > Thanks and kind regards,
> >
> > Andy Zitelli
> >
>
>
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.orawin.info
--
http://www.freelists.org/webpage/oracle-l
Received on Wed May 16 2007 - 14:52:52 CDT
