Home › Discussions › Questions & Answers › Oracle E-Business Suite – Concurrent Request Monitoring and Alert Reporting

Oracle E-Business Suite – Concurrent Request Monitoring and Alert Reporting

Avatar photoCustomer Questions & Answers 5 replies

We currently monitor critical concurrent requests using Oracle Alert, but the text-based emails limit useful analysis. How does the Blitz Report approach enhance concurrent request monitoring and alert reporting for our support teams?

5 replies

  • Support Enginatics

    Blitz Report addresses the limitations of standard Oracle Alert, where Excel exception files cannot be sent and emails are only in text format. Our standard exception reporting method delivers the output directly in an Excel file emailed to the relevant teams. This allows immediate, actionable analysis rather than just a simple text notification.

  • What detailed filtering mechanisms are available? We need to pinpoint specific types of issues quickly, like long-running or failed requests.

  • Support Enginatics

    The report parameters are highly granular, designed specifically to pinpoint problematic requests. You can filter based on status (e.g., `* Error;Warning, etc`), phase (e.g., `Completed, etc`), or execution time (e.g., `Running longer than x Minutes` or `Waiting for x Minutes`). Furthermore, you can include detailed metadata like the `Execution Method` or narrow down the selection by `Concurrent Program Short Name`.

  • Can we also capture the underlying SQL text for detailed diagnostics in these alert reports?

  • Support Enginatics

    Yes, there is an option to include an additional column displaying the active session SQL Text. However, be aware that setting this option may slow down report execution significantly, so it should be used judiciously for targeted monitoring.

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