This content has been marked as final. Show 3 replies
For the monitoring part, please see the following documents.
Note: 187504.1 - bde_request.sql - Process and Session info for one Concurrent Request (11.5)
Note: 735119.1 - How to Find Database Session & Process Associated with a Concurrent Program Which is Currently Running.
Note: 97810.1 - Scripts for Finding OS and ORACLE Information for Given Concurrent Request ID
Note: 280391.1 - How to Retrieve SID Information For a Running Request
Thanks for reply. All these scripts / notes appear to be guidance to an Oracle DBA/developer on how to trace/monitor concurrent requests using V$ views etc.
As I explained, that's not what I am trying to do. I am trying to find the Apps equivalent of monitoring long operations. Of course, I could (and probably wlll) use DBMS_APPLICATION_INFO and the DBA/developer will be able to monitor the progress of the master and slave requests - but the professional user who initiated the request won't have access to that from the EBS screens. I want to know whether there is any concurrent request field that I can populate using a supported API to be able to feedback progress information along the lines:
09:10: 1,000 employees processed out of 138,000 in 0:38 - expected finish 16:28
09:32: 2,000 employees processed out of 138,000 in 1:04 - expected finish 16:15
which the professional user would be able to query on. Currently the process takes > 100 hours; even reworked into a parallel master / slave it will take 8-12 hours.
Is anyone have scripts for history of long running forms/concurrent program , high logical IO , high physical IO , cost , users .