Re: realising a "progressbar" for a long working package

From: ddf <oratune_at_msn.com>
Date: Tue, 10 Feb 2009 06:51:42 -0800 (PST)
Message-ID: <3646b201-65d0-4a5a-a311-cb724e0765d6_at_u1g2000vbb.googlegroups.com>



On Feb 10, 5:58 am, Norbert Winkler <norbert.winkl..._at_gmx.de> wrote:
> Hi,
>
> I've a package that generates some table records with some random chooses
> (2-5%).
> But the steps to generates the random sample need a little bit time.
> I've tried to optimize it by using all indexes (by separtating it in more
> steps with several new tables) and so far I think I couln't improve it in
> speed.
> Now I would like it that my application reports me the step it is working
> on.
> 1. The simplest way - but brute force - seems me to start the package work
> in a separated thread, and use a timer to start count-queries about the
> filled tables, a commit after each step wouldn't be a problem.
> 2. Or I split the work in more procedures that I call step by step in my
> application. But the the logic goes to the application.
> 3. To use a package report-variable isn't possible (I think) because my
> threads need different sessions.
>
> Any suggestions are welcome!
>
> --
> Norbert
> Oracle9i Enterprise Edition Release 9.2.0.8.0 64Bit

You should probably look into the possibility of using the V $SESSION_LONGOPS view.

David Fitzjarrell Received on Tue Feb 10 2009 - 08:51:42 CST

Original text of this message