Re: Activate SQL logging

From: MCArch <spamfree_at_thankyou.net>
Date: Sun, 13 Feb 2005 05:03:08 GMT
Message-ID: <gcBPd.6855$hU7.6706@newssvr33.news.prodigy.com>

"Mark A" <nobody_at_nowhere.com> wrote in message news:SIKdncZBvonVXZPfRVn-2A_at_comcast.com...
> > > > How can I capture incoming SQL statements to a text file?
> > >
> > > AFAIK, there is no (simple?) way to do this.
> > >
> > > Why in the world do you even want to consider doing this?
> > >
> > > The contents of the "text file" would be subject to security/privacy
> > > compromises.
> >
> > Just trying to figure out what an application is doing to the database.
I
> > thought there would be some way to activate a log, that would capture
the
> > SQL.
> >
> This can easily be done in DB2, using either a statement monitor and
> snapshot (logs all SQL between when the monitor is turned on and then
turned
> off). Lots of information is provided such as number of executions,
average
> execution time, average CPU time, etc. This can be done globally, or for a
> specific application.
>
> You can also use the Event Monitor to track specific SQL events and notify
> you when they occur. If a more powerful tool is needed, the DB2 Query
> Patroller can be used.
>

I guess I deserve that answer for not indicating that the server is Oracle 8.1.7.4. Received on Sat Feb 12 2005 - 23:03:08 CST