Re: how to monitor the progress of inserts
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: Juan Carlos Reyes Pacheco <juancarlosreyesp@xxxxxxxxx>
- Date: Tue, 1 Feb 2005 16:45:26 +0000
On Tue, 1 Feb 2005 12:34:58 -0400, Juan Carlos Reyes Pacheco
<juancarlosreyesp@xxxxxxxxx> wrote:
> And about 10g, this is what I talk about, and I repeat, I didn't
> tested this features, but based on documentation it could help, maybe.
Did you read the docs and think about Sonia's request? Sonia wants to
monitor a specific job in a specific session for progress. You've
pointed her at a feature that tracks tables rather than sessions and
updates the data dictionary statistics with approximate figures only
every 3 hours. That seems to me to be monitoring the wrong thing too
infrequently for this purpose, this isn't really a surprise since
object monitoring is a feature aimed at determining when and on what
objects it is probably worth gathering stats. I stick by my suggestion
of V$SESSION_LONGOPS and suggest that you and she note what it
measures and what its purpose is to see if it is appropriate.
V$SESSION_LONGOPS
This view displays the status of various operations that run for
longer than 6 seconds (in absolute time). These operations currently
include many backup and recovery functions, statistics gathering, and
query execution, and more operations are added for every Oracle
release.
To monitor query execution progress, you must be using the cost-based
optimizer and you must:
*
Set the TIMED_STATISTICS or SQL_TRACE parameter to true
*
Gather statistics for your objects with the ANALYZE statement or
the DBMS_STATS package
You can add information to this view about application-specific
long-running operations by using the
DBMS_APPLICATION_INFO.SET_SESSION_LONGOPS procedure.
.
--
Niall Litchfield
Oracle DBA
http://www.niall.litchfield.dial.pipex.com
--
//www.freelists.org/webpage/oracle-l
Other related posts:
