Re: Trace files for a running process

svrgmrl
connect internal
oradebug setospid {o/s process id of shadow process} oradebug unlimit

--

Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk

Duncan Hodson wrote in message
<934892072.22556.0.nnrp-09.c2debfb5_at_news.demon.co.uk>...
>Greetings,
>
>I have been given the task of converting a company's data from their old
>system to our new system, and the main part of the processing to achieve
>this is written in PL/SQL (the process imports using SQL*LOADER, creates
>indexes, and then fills missing values and creates missing records in
>PL/SQL). The problem is that it runs slowly - too slow for our
>customer's liking. I can turn on oracle trace using TOAD (an essential
>application!), run tkprof on the trace file that is generated, and see
>which parts of the process are running slowly - i can then either modify
>the processing and tweak indexes in an attempt to speed things along.
>
>The problem is that i set the maximum dump file size to 10 meg in the
>database initialisation file, and that limit has been reached. Is there
>a way to increase the allowed size of a trace file whilst a session is
>running? Is there a way to specify a different log filename for a
>session which is still running?
>
>My alternative is to stop the process and restart it (it carries on from
>where it got to) but that takes a couple of hours which i can't afford
>at the mo.
>
>Cheers all
>
>Duncan
>
>=== Duncan Hodson
>=== Analyst Programmer
>=== Welcom Software
>
>
>
Received on Tue Aug 17 1999 - 09:40:32 CDT