Re: Activate SQL logging

From: DA Morgan <damorgan_at_x.washington.edu>
Date: Thu, 17 Feb 2005 09:47:21 -0800
Message-ID: <1108662268.659055@yasure>

MCArch wrote:

> "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.

Actually you didn't ... MarkA just needs a few years to mature.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace 'x' with 'u' to respond)

Received on Thu Feb 17 2005 - 11:47:21 CST