Navigate:
Oracle Applications Manager > Concurrent Managers OR Concurrent Requests > Site Map > Diagnostics and Repair > Concurrent Manager Recovery
Follow steps and finish.
./adcmctl.sh stop
./adcmctl.sh start
TROUBLESHOOTING STEPS
Concurrent Processing Command-Line Utility
The command-line utility cpadmin consolidates various existing utilities for concurrent processing into a single menu-based utility. This adadmin-style utility can be used for multiple tasks, including:
• Manager Status: Use this option to display the statuses of all managers.
• Clean CP Tables: Use this option to clean up the concurrent processing tables. This utility replaces cmclean.sql.
• Set Manager Diagnostics: Turn diagnostics on or off for individual managers with this option.
• Manager Control: Use this option to send a request such as start, stop, or verify to an individual manager.
• Rebuild Manager Views: Use this option to rebuild the FND_CONCURRENT_WORKER_REQUEST and FND_CONCURRENT_CRM_REQUESTS views.
• Move Request Files: Change request log and output file locations with this option.
• Analyze Request: Use this option to analyze a concurrent request.
• Manager Status: Use this option to display the statuses of all managers.
• Clean CP Tables: Use this option to clean up the concurrent processing tables. This utility replaces cmclean.sql.
• Set Manager Diagnostics: Turn diagnostics on or off for individual managers with this option.
• Manager Control: Use this option to send a request such as start, stop, or verify to an individual manager.
• Rebuild Manager Views: Use this option to rebuild the FND_CONCURRENT_WORKER_REQUEST and FND_CONCURRENT_CRM_REQUESTS views.
• Move Request Files: Change request log and output file locations with this option.
• Analyze Request: Use this option to analyze a concurrent request.
Complete the steps below to run the command-line utility and its maintenance tasks.
1. Set the environment.
You must set the environment in order to apply the environment variables that define your system. This task is common to many utilities. See Setting the Environment, Oracle E-Business Suite Maintenance Guide for the preparatory steps.
2. From any directory, start cpadmin with this command:
$ cpadmin.sh
The utility starts and prompts you for the APPS password (required).
3. Respond to prompts.
Supply the information requested by cpadmin prompts. Prompts unique to an option are described with the option.
When you complete the prompts, the Main Menu appears.
4. Choose one of the tasks listed above.
5. Exit the cpadmin utility.
1. Set the environment.
You must set the environment in order to apply the environment variables that define your system. This task is common to many utilities. See Setting the Environment, Oracle E-Business Suite Maintenance Guide for the preparatory steps.
2. From any directory, start cpadmin with this command:
$ cpadmin.sh
The utility starts and prompts you for the APPS password (required).
3. Respond to prompts.
Supply the information requested by cpadmin prompts. Prompts unique to an option are described with the option.
When you complete the prompts, the Main Menu appears.
4. Choose one of the tasks listed above.
5. Exit the cpadmin utility.
This is documented here: http://docs.oracle.com/cd/E26401_01/doc.122/e22953/T174296T575591.htm#8159578
Concurrent Manager Recovery Wizard
NOTE: The Concurrent Managers have to be stopped before the Wizard is run.
Please run the Concurrent Manager Recovery wizard to address Concurrent Manager failures within the Oracle Applications Manager.
Using the Concurrent Manager Recovery wizard is the method to clear the errors upon bringing the Internal Manager back up.
For Concurrent Internal Manager failures, it is recommended to run the Concurrent Manager Recovery feature using the Oracle Applications Manager. This feature should be used for recovering from when the Internal Manager won't start. This is accessed from the Troubleshooting wizards available within Oracle Applications Manager logged in as the sysadmin userid.
Navigate:
Oracle Applications Manager > Concurrent Managers OR Concurrent Requests > Site Map > Diagnostics and Repair > Concurrent Manager Recovery
For information on the Concurrent Manager Recovery feature, please reference the Oracle Applications System Administrator's Guide - Maintenance provides information for frequent tasks such as monitoring your system with Oracle Applications Manager, administering Oracle E-Business Suite Secure Enterprise. Search, managing concurrent managers and reports, using diagnostic utilities including logging, managing profile options, and using alerts.
Using the Concurrent Manager Recovery wizard is the method to clear the errors upon bringing the Internal Manager back up.
For Concurrent Internal Manager failures, it is recommended to run the Concurrent Manager Recovery feature using the Oracle Applications Manager. This feature should be used for recovering from when the Internal Manager won't start. This is accessed from the Troubleshooting wizards available within Oracle Applications Manager logged in as the sysadmin userid.
Navigate:
Oracle Applications Manager > Concurrent Managers OR Concurrent Requests > Site Map > Diagnostics and Repair > Concurrent Manager Recovery
For information on the Concurrent Manager Recovery feature, please reference the Oracle Applications System Administrator's Guide - Maintenance provides information for frequent tasks such as monitoring your system with Oracle Applications Manager, administering Oracle E-Business Suite Secure Enterprise. Search, managing concurrent managers and reports, using diagnostic utilities including logging, managing profile options, and using alerts.
NOTE: The cmclean_query.sql was created to reflect the data updated by the original cmclean script for use as needed.
No comments:
Post a Comment