Re: query log

Depending on why this information is wanted I do not think the archived redo logs will prove all that useful since, while DML statements are logged, normal select statements are not written to the redo logs. However, most recent SQL should still be loaded in the shared pool. If all that is desired is to look at the SQL with high IO or resouce counts you should be able to scan the v$sql views periodically to find the heavy hitters.

Statspack records the heavy hitters and you can dump the statements to a report using the higher level options.

Version 10g automatically stores relatively high resource SQL statement statistics in its AWR.

But the AWR and sampling the v$ views will not give you eveything nor the order the statements ran in.

But then tracking everything all the time is neither practical nor is it useful.

Depending on what you really need auditing and trace files are potential options.

HTH -- Mark D Powell -- Received on Thu Apr 06 2006 - 14:29:17 CDT