MBPP wrote:
> Another way is to execute your update in a job using DBMS_JOB, Then
> follow the execution using a join between V$SESSION and
> V$SESSION_LONGOPS. To identify the job's session ID you can use
> DBMS_APPLICATION_INFO. On the client side create a timer using
> JavaScript and query these views to get an estimate of how long it will
> take to finish. Concerns:
>
> - Not all operations are recorded through dynamic performance view,
> only "long" operations. I don't know the criteria Oracle uses to
> determine this, maybe someone else can clarify this.
> - Statistics in V$SESSION_LONGOPS are based on estimates so not always
> you will get 0-100%.
> - You need at least "select" access on these system views, maybe an
> area of conflict to your DBA.
>
> I never done this before, just an idea which came to my mind...
A full demo of LONGOPS implementation can be found at:
http://www.psoug.org
click on Morgan's Library
click on DBMS_APPLICATION_INFO
scroll down
--
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)
Received on Tue May 31 2005 - 15:17:26 CDT
