"DA Morgan" <damorgan@x.washington.edu> wrote in message
news:41c8c7d3$1_3@127.0.0.1...
> Dave Griffen wrote:
>
> > One of
> > the things I use it for is to check the progress of batch jobs. If I
know a
> > program is going to insert 100,000 rows into a table, I can use dirty
read
> > to see how many rows it has inserted so far and can give a good estimate
of
> > when it will finish. If you are only allowed to see committed data, you
> > wouldn't have that monitoring option.
>
> In Oracle one would use the DBMS_APPLICATION_INFO built-in package as it
> not only tells you what percentage of a batch is done it uses the
> transaction rate to an estimate of the completion time. The information
> is available via OEM and by querying v$session_longops.
>

Sounds like a good substitute for gauging percent completion of a current
statement. But, the DBMS itself will only be able to estimate completion of
statements which it currently knows about. If the 100,000 records are being
inserted via 1000 different statements, I doubt this would give me a good
estimation of program completion time midstream. Does DBMS_APPLICATION_INFO
show an insert record count or anything else which would help a user or DBA
make their own estimation in such a case? Does Oracle offer any access
method which gives direct visibility to uncommitted data?

Dave Griffen