Re: SQL Trace
Date: Fri, 22 Aug 2003 21:17:11 +0100
Message-ID: <3f467a44$0$13637$cc9e4d1f_at_news.dial.pipex.com>
[Quoted] "Sha" <ssha53_at_singnet.com.sg> wrote in message
news:bi5j2i$4nn$1_at_mawar.singnet.com.sg...
> Hi again
>
> Is this resource intensive ?
In terms of response time no. In terms of disk space and dba troubleshooting
[Quoted] time absolutely yes. sql_trace=true implies you wish to capture every
statement issued by every session against the db while the instance is up
and save them to disk. I can think of very few instances in which this would
[Quoted] be either true or worthwhile. Most times you wish to capture problem
sessions for the duration of a problem. To effectively tune you need to
isolate and reproduce the problem. see my other answer for a suggested
approach. reading that elaborates further would be the Oracle Performance
Tuning 101 book
(http://www.amazon.com/exec/obidos/ASIN/0072131454/qid%3D1061583353/sr%3D11-
[Quoted] 1/ref%3Dsr%5F11%5F1/103-3520369-3405433)
or Christopher Lawsons excellent Art and Science of Oracle Performance Tuning.
(http://www.amazon.com/exec/obidos/tg/detail/-/1590591992/qid=1061583215/sr= [Quoted] 1-3/ref=sr_1_3/103-3520369-3405433?v=glance&s=books)
those links will likely wrap
NB you would also wish to set MAX_DUMPFILE_SIZE (or very similar name) to unlimited to get all information.
-- Niall Litchfield Oracle DBA Audit Commission UK ***************************************** Please include version and platform and SQL where applicable It makes life easier and increases the likelihood of a good answer ******************************************Received on Fri Aug 22 2003 - 22:17:11 CEST