Re: SQL TRACING FOR A PARTICULAR SESSION.

From: Jaffery <maulana1_at_hotmail.com>
Date: 2 Mar 2004 21:31:36 -0800
Message-ID: <3ff5ba5f.0403022131.f250f05@posting.google.com>

Hi

Thanks for your information.

But I like to say that, I wanted to store the text of these SQL TRACE files which belongs to different session, into my table SQL_TRACE (session_id, username, text).Because of Historical purpose

I know TKPROF is the utility via which we can read these sql trace files.
For Example:
C:\ tkprof c:\SQL_TRACE\ora012929.trc c:\SQL_text\oratext.txt

With regards to this, how should we read the trace files for the users who logon to the database using the feature of logon trigger and then store the text of these sqltrace files of different users into the table SQL_TRACE (session_id, username, text). Could you please give your suggestion about it?

Thanks

Jaffery.

---

Sybrand Bakker <gooiditweg_at_sybrandb.demon.nl> wrote in message news:<gm0a40dppnlqe3nlfvo6o2nhql02hgbprf_at_4ax.com>...
> On 1 Mar 2004 01:50:25 -0800, maulana1_at_hotmail.com (Jaffery) wrote:
>
> >Hi,
> >
> >I like to say that, I wanted to enable SQL Tracing for a particular
> >session implicitly, when it connects to database.
> >Is that possible?
>
> Yes, in 8i and higher, by means of an after logon trigger
>
> >When a session connects to database, its information will be stored in
> >a table &#8220;Session_Tracing (id, text)&#8221;.
>
> This is not possible. Why would it? You have a trace file and that
> should be sufficient.
>
>
>
> > And when the session log off, its information will be deleted from
> >the table &#8220;Session_Tracing&#8221;.
>
> So the whole operation is pretty useless
>
>
> >How should we do that?
> >
> >
> >Any ideas will be great.
> >
> >Jaffery
Received on Tue Mar 02 2004 - 23:31:36 CST