Home › Discussions › Questions & Answers › Creating a custom concurrent manager in Oracle EBS
Creating a custom concurrent manager in Oracle EBS
Customer · · Questions & Answers · 11 replies
We need to create a dedicated custom concurrent manager in Oracle EBS to handle specific, high-priority reports and processes, isolating their workload from the standard managers. Where can we find comprehensive guidance on the necessary steps to set this up?
11 replies
The process for Creating a custom concurrent manager in Oracle EBS is a standard DBA task. This involves defining the new Concurrent Manager, assigning it a Service Instance, setting up its Workshifts, and associating specific Concurrent Programs with it to control workload execution.
After implementation, how can we efficiently monitor the workload and queue status of this new custom manager, specifically looking for backlog or long-running requests?
You should utilize the Oracle E-Business Suite – Concurrent Request Monitoring and Alert Reporting tool provided by Blitz Report. This diagnostic report allows filtering by the specific Manager Name.
What technical parameters can we monitor using the Blitz Report tool to assess the health of the custom manager’s workload?
The report parameters are granular. You can monitor key metrics such as `Scheduled or Running` requests, and filter based on elapsed time criteria like `Waiting for x Minutes` or `Running longer than x Minutes` to identify bottlenecks within the new manager’s workload and clear any potential backlog.
We need the monitoring report to capture the parameters passed to the concurrent programs to troubleshoot failures.
You can enable the `Show Parameters Display Values` setting in the alert report. However, note that setting this option to ‘Yes’ could significantly slow down the report execution, so use it judiciously for critical debugging rather than routine monitoring.
If we discover an issue, can the tool also output the BI Publisher template or delivery options used by the failed request?
Yes, the report includes a parameter to Show BI Pub & Delivery Options. When enabled, this shows information such as the publisher template, output file, post-processor result, and delivery details (email or FTP information).
We need to ensure that the managers are correctly defined in the database before starting the custom service. What tables should a DBA confirm?
The DBA would typically query standard FND tables to verify the setup. For instance, diagnostic queries confirming the configuration of nodes and managers rely on details from tables accessed via the APPS user (e.g., querying `apps.fnd_nodes`) to confirm service mappings and node information.
- You must be logged in to reply to this post.
Sign in with LinkedIn or Google to take part.