How to Manage Concurrent Process in Oracle EBS R12 An In Depth Guide

YouTube video

Concurrent processing is a crucial aspect of managing Oracle EBS R12, and understanding how to effectively manage concurrent managers and requests is essential for Oracle Apps DBAs. In this comprehensive guide, we will explore the process of managing concurrent processing in Oracle EBS R12, including a step-by-step walkthrough of the log files of concurrent managers and concurrent requests. We will also delve into the use of cpadmin.searchtool, a powerful tool that aids in monitoring and managing concurrent processing.

Understanding the Log Files of Concurrent Managers and Concurrent Requests

The log files of concurrent processing play a vital role in troubleshooting and monitoring the concurrent managers and requests. There are two types of log files: concurrent manager log files and concurrent request log files.

Viewing Concurrent Manager Log Files

To access the concurrent manager log files, you have two options: through the front end and the back end.

Front End:

  1. Log in to Oracle EBS R12 and navigate to the “Administer Concurrent Managers” form.
  2. Select a specific manager and click on “Processes.”
  3. From here, you can access the manager log file.

Back End:

  1. Log in to the backend using the “aplcsfapi” login.
  2. Go to the “aplcsfapi” log location. Here, you will find two types of files: dot mgr files (manager log files) and dot req files (concurrent request log files).

Understanding Concurrent Request Log Files

To view the concurrent request log files, you need to submit a concurrent request and then navigate to the log file location in the backend.

  1. Submit a concurrent request from the front end.
  2. Once the request is running, go to the Concurrent Manager Administrator form. Here, you can see the running request under the respective manager.
  3. Select the manager to access the internal manager log file.
  4. To view other manager log files, simply select the desired manager from the list.

Accessing Log Files and Output Files

To access the log files and output files of concurrent requests, you need to navigate to the log file location and the output file location in the backend.

  1. Set the run file system environment by running the command “echo $APPLCSF/APPLE_LOG” in the backend. This will display the log file location.
  2. Similarly, you can access the output file location using the command “echo $APPLCSF/APPLE_LOG/out.”

In the log file location, you will find various files with extensions such as dot mgr, dot txt, and dot req. The dot txt and dot mgr files contain information related to workflow and other requests. The dot req files represent the concurrent request log files. By matching the request ID from the front end with the log file, you can easily locate the relevant log file.

Similarly, you can navigate to the output file location to access the output file of a specific concurrent request.

Introducing cpadmin.searchtool – A Powerful Tool for Managing Concurrent Processing

In recent years, a new tool called cpadmin.searchtool has been introduced to help DBAs effectively monitor and manage concurrent processing. This tool offers various functionalities and options that aid in troubleshooting and optimizing the performance of concurrent managers. Let’s explore some of the key features of cpadmin.searchtool:

Manager Statuses and Management

With cpadmin.searchtool, DBAs can check the status of concurrent managers, start/stop individual managers, and verify the status of managers. This helps in ensuring that all managers are running smoothly and processing requests as intended.

Cleaning CP Tables

CP tables, which are the concurrent processing related tables, can sometimes encounter issues. With cpadmin.searchtool, DBAs can clean these tables, ensuring that the data related to concurrent processing is accurate and up-to-date. This process does not delete any data but rather resets the tables, allowing the concurrent managers to resume normal functioning.

Diagnostics and Troubleshooting

cpadmin.searchtool also offers diagnostic capabilities, allowing DBAs to troubleshoot any issues with concurrent managers or requests. It provides options to analyze specific requests, rebuild manager views, and perform various other diagnostic tasks.

Configuring Log File and Output File Locations

One of the essential capabilities of cpadmin.searchtool is the ability to configure the locations of log files and output files. DBAs can easily change the default locations to their preferred directories, ensuring easy access and management of log and output files.

Step-by-Step Process for Using cpadmin.searchtool

To utilize the functionalities of cpadmin.searchtool, follow these steps:

  1. Access the operating system level and run the command cpadmin.search.
  2. Provide the appropriate apps password to authenticate.
  3. From the menu, select the desired option based on your requirements. For example:
  4. Display all running concurrent managers to check their status.
  5. Clean concurrent processing tables to reset and optimize the tables.
  6. Diagnose specific requests or troubleshoot issues.
  7. Rebuild manager views if there are any inconsistencies.
  8. Configure log file and output file locations as per your preference.

By leveraging the capabilities of cpadmin.searchtool, DBAs can effectively manage concurrent processing, resolve issues promptly, and optimize the performance of concurrent managers.

Conclusion

Managing concurrent processing is a critical aspect of maintaining Oracle EBS R12. By understanding the log files of concurrent managers and concurrent requests and utilizing tools like cpadmin.searchtool, DBAs can efficiently monitor, troubleshoot, and optimize concurrent processing. Following the steps outlined in this guide, DBAs can ensure smooth and efficient concurrent processing in Oracle EBS R12.