Home › Discussions › Questions & Answers › Tracking Progress of Extended Database Operations

Tracking Progress of Extended Database Operations

Avatar photoCustomer Questions & Answers 5 replies

We have batch processes that can run for hours, and we need a way to monitor their progress and estimate their time to completion without querying `GV$SESSION_LONGOPS` manually. Which Blitz Report displays this?

5 replies

  • Support Enginatics

    The DBA Session Longops report is what you need. It provides the estimated time to completion for long-running sessions, sourcing its data from `gv$session_longops`.

  • If I see a long-running session that is frequently waiting on I/O, how should I cross-reference that with the actual objects being read?

  • Support Enginatics

    You should note the SQL_ID from the session and check the DBA SGA Active Session History report to see the sequence of wait events and the module/action associated with the session. You can then use the SQL_ID with the SQL Performance Summary reports to analyze the IO impact.

  • If the long operation is triggered by a concurrent request, where can I find the process details?

  • Support Enginatics

    The FND Concurrent Requests report allows you to monitor running requests, providing the session ID and details of the current operation, which should correlate with the information found in DBA Session Longops.

  • You must be logged in to reply to this post.