Concurrent Manager Recovery Wizard – Oracle Applications Manager Troubleshooting and Diagnostics
Follow the below steps to use the Concurrent Manager Recovery Wizard:
1. To access the Concurrent Manager Recovery Wizard, use the following navigation path:
Navigation:
System Administrator -> Oracle Applications Manager -> Debug Workbench -> Site Map -> Diagnostics and Repair > Concurrent Manager Recovery (under Troubleshooting Wizards)
2. Click the Run Wizard button to start the recovery process. (Note: You cannot run this process if the Internal Concurrent Manager is currently running.)
3. Follow the below steps for troubleshooting any Concurrent Manager issues:
Step 1– Active Managers with a Database Session
This screen lists all managers that must be stopped before proceeding with the recovery.
Listed for each manager are:
CP ID – The Concurrent Program ID.
Manager – The manager name.
Node – The node on which the manager is running.
DB Session ID – Drills down to the Database Session Details screen.
Session Status
OS ID
Started At – The time at which the manager was started.
Running Request – Drills down to display the request in the Advanced Search for Requests page.
You may want to wait for any requests that are running to complete before you execute the shutdown. Drill down on the Running Request to view it.
Click Shutdown to shut down all the listed managers, and then click the Refresh icon to verify that they were shut down. If a manager fails to shut down from this page, you can drill down to the Database Session Details page and use the Terminate button to end the session from there. Return to the Concurrent Manager Recovery screen and refresh the page to verify all managers have been shut down before proceeding to the next step.
Step 2 – Managers Deemed Active but Without Database Session
Any processes listed here must be terminated before continuing. Because these processes have lost their database sessions, they must be manually terminated from the command line. Refer to your operating system documentation for instructions on terminating a process from the command line.
After terminating the processes, click Update to mark the processes as no longer active in the database table. Click the Refresh icon to verify that all processes have been terminated.
Listed for each process are:
CP ID
Manager
Node
OS PID
Started At
Step 3 – Reset Conflict Resolution
Click the Reset button to reset the listed requests for conflict resolution. This action changes requests that are in a Pending/Normal phase and status to Pending/Standby. Click the Refresh icon to verify that all requests have been reset.
You can drill down on the Request ID to view the request in the Advanced Search for Requests screen.
Listed for each request are:
Request ID
Program
User
Step 4 – Requests that are Orphaned
This page lists the requests that do not have a manager. If any requests have Active Sessions listed, drill down on the session ID and terminate the session from the Database Session Details screen. Return to the Concurrent Manager Recovery screen and click the Refresh icon to verify that the session is no longer active.
Listed for each request are:
Request ID – Drills down to display the request in the Advanced Search for Requests page.
Parent ID
Program
User
Phase
Status
Active Session
Step 5 – Concurrent Manager Recovery Summary
The summary page lists the information collected from the previous steps. After reaching this page, you should be able to restart your Internal Concurrent Manager.
If you cannot, retry starting the Internal Concurrent Manager with DIAG=Y, refresh the summary page, add it to the Support Cart with the log files, and send them to Oracle Support.
Log Files Collected – Click on the log file name to view it. The following log files can be added to the Support Cart:
Report Summary
Active Managers with a Database Session
Managers Deemed Active but Without a Database Session
Reset Conflict Resolution
Requests that are Orphaned
Reference:
Concurrent Manager Recovery Wizard – Oracle Applications Manager Troubleshooting and Diagnostics (Doc ID 2130545.1)
