This action might not be possible to undo. Are you sure you want to continue?
1] -------------------------------------------------------------------------------Modified 31-MAR-2010 Type FAQ Status PUBLISHED
Checked for relevance on 31-Mar-2010 PURPOSE ------To deliver a set of frequently asked questions against AOL FND Concurrent Manager. SCOPE & APPLICATION ------------------This reference would be most useful for one who is seeking additional information regarding AOL FND Concurrent Manager issues.
FND Concurrent Manager FAQ's ----------------------------When would one be required to bounce (stop and restart) the Concurrent Manager? When you modify the Printer Driver you have to restart the Manager whic h runs the request which is attached to that Printer Driver, however,if y ou do not know which manager then you have to restart the Internal manager be cause the printer driver can be used by multiple managers and multiple reques ts. If only a concurrent program definition is modified, running a verify o n the Internal Manager will pick up the changes without the need for bouncing the manager.
Does the Internal manager schedule requests to be run or does it put requests into queues to be run by other managers? This is a very common misconception. The ICM really does not have any such scheduling responsibilities. It has NOTHING to do with scheduling requests, or deciding which manager will run a particular request. Its function is only to run 'queue control' requests, which are requests to startup or shutdown other managers. It is responsible for startup and shutdown of the whole concurrent processing facility, and it also monitors the other managers periodically, and restarts them if they should go down. It can also take over the Conflict Resolution
then the manager processes have either failed to start up. and the other two are directory names. i. You can also search for OS processes using the 'ps' command. The Target colu mn lists the number of processes that should be running for each manager for this particular workshift. You will see two columns labeled 'Actual' and 'Target'. On NT. then either a workshift has not been assigned to this manager. and resolve incompatibilities. absolute path. you can check to see if the Concurren t Manager service is running using the Services control panel. When in doubt. Where do concurrent request or manager logfiles and output files go? The concurrent manager first looks for the environment variable $APPLCSF. How can I check to see if a concurrent manager is running? One way to see if a manager is running is to use the 'Administer Concurrent Managers' form. or gone down. it may show actual processes even though they are not really running. a PO report would go under $PO_TOP/$APPLLOG and $PO_TOP/$APPLOUT Logfiles go to: /u01/appl/po/9. except for 'queue control' requests. If this is set. it places the files under the product top of the application associated with the request. Navigate to Concurrent->Managers->Administer . If the target column is not zero. You should check the manager's logfile and the ICM logfile. it creates a path using two other environment variables: $APPLLOG and $APPLOUT It places log files in $APPLCSF/$APPLLOG. and output files in /u01/appl/common/out Note that $APPLCSF must be a full. If the ICM itself should go down.0/out . or the c urrent workshift does not specify any target processes. If $APPLCSF is not set. if $APPLCSF = $APPLLOG = $APPLOUT = you have this environment set: /u01/appl/common log out The concurrent manager will place log files in /u01/appl/common/log. If the Actual column is zero. For example. If the Target column is zero .0/log Output files to: /u01/appl/po/9. check for processes at the OS level. you do not need to kill the other managers first.e. The Actual column lists the number of processes that are actually running. ther e are no processes running for this manager. You can restart it with 'startmgr'. output files go in $APPLCSF/$APPLOUT So for example. requests will continue to run normally. It is possible for the form to be inaccurate.manager's job.
out Where: = The request id of the concurrent request And: = The id of the user that submitted the request Manager logfiles: ICM logfile: Default is std. Concurrent manager logfiles follow the same convention. . then the Conflict Resolution M anager prevents the concurrent managers from starting other programs in the sa me conflict domain. If a program is identified as Run Alone.mgr Conflict Resolution manager log: c. The Conflict Resolution Manager checks concurrent program definitions for incompatibility rules. can be changed with the mgrname startup parameter Concurrent manager log: w. but not necessari ly an output file. and delete the row.out If $APPCPNAM = USER: .req Output files: If $APPCPNAM is not set: . If $APPCPNAM = REQID: o.All these directories must exist and have the correct permissions.mgr Transaction manager log: t. (It is recommended that you DO NOT do this) What is the function of the 'Conflict Resolution Manager'? Concurrent managers read requests to start concurrent programs running. and will be found in the $APPLLOG directory What are the logfile and output file naming conventions? Request logfiles: l. Note that all concurrent requests produce a log file.mgr. you can query the manager in the 'Define Manager' form.mgr Where: is the concurrent process id of the manager Can I delete a concurrent manager? You can disable the manager by checking the 'Enabled' checkbox. or you can simply Terminate the manager and it will not run again unless you reactivate it. If it is really necessary.
You do not need to run this manager/service unless you are using Distri buted Concurrent Processing. What is the 'Internal Monitor' manager/service? This manager/service is used to implement Distributed Concurrent Proces sing.When a program lists other programs as being incompatible with it. General Ledger uses FNDSCH for financial schedules based on different calendars and period types. This manager is intended to implement Advanced Schedules. Its job is to determine when a scheduled request is ready to run. What is the 'Internal Scheduler/Prereleaser' manager? The short name for this manager is FNDSCH. they are implemented in Release 11. Budget Formulas. To 1) 2) 3) set the PMON method: first shut the concurrent managers down cd $FND_TOP/sql sqlplus apps/apps @afimpmon. It monitors whether the ICM is still running. Advanced Schedules were not fully implemented in Release 11. See the Installation manual and Sysadmin Guide for more info on DCP. and where the log file is. and if the ICM crashes.5. what the PMON method is. It is also known as the Advanced Scheduler/Prereleaser Manager. Setting this to 'No' (which is the default) allows the CRM to be starte . MassAllocations. it will restart it on another node. It is then possible to schedule AutoAllocation sets.sql LOCK (or RDBMS) How do I enable/disable the Conflict Resolution Manager? Use the system profile option 'Concurrent: Use ICM'. If financial schedules in GL are not being used then it is not a problem to deactivate this manager. and MassBudgets to run according to the General Ledger schedules that have been defined. How do I check/set the PMON method? To check the PMON method: 1) cd $FND_TOP/sql 2) sqlplus apps/apps @afimchk.0. the Conflict Resolution Manager prevents the program from starting until an y incompatible programs in the same domain have completed running. but are not widely used by the various Apps products. Recurring Journals.sql This will tell whether the internal manager is running.
Setting it to 'Yes' causes the CRM to be shutdown and the Internal Manager (ICM) will take over the conflict resolution duties. like ARLIBR or INVLIBR: $ ps -ef grep ARLIBR .sql. If the CRM will not start (it is started automatically by the ICM).SQL . Notice that the ICM process is the parent process of the Standard managers. while the ICM has other functions to perform as well. not to mention losing all of the request information. check this profile option. (processes 24936 and 24938) Other managers will have the name of the executable. this has been done by truncating fnd_concurrent_processes and/or fnd_concurrent_requests. Notice that it gives some of the parameters it was started with.Non Destructive Script to Clean Concurrent Manager Tables It will make sure the relevant status codes are valid without deleting any information. How do I clean out the Concurrent Manager tables? Cleaning out the tables is a useful method of making sure that there are no invalid statuses that can prevent the managers from starting. shows 'FNDLIBR FND CPMGR'. The CRM's sole purpose is to resolve conflicts. #24927. Previously. Note that using the ICM to resolve conflicts is not recommended. article note 134007.d. Only set this option to 'YES' if you have a good reason to do so.1 CMCLEAN. cmclean. this one is the Internal Manager (ICM). and can cause problems later when trying to purge requests. the other processes showing 'Concurrent_Processor' are Standard manager processes. How do I tell concurrent manager processes apart at the OS level? Use: pf -ef grep FNDLIBR This will produce output like: vd11 13703 13660 0 May 11 ? 0:01 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS/94A491A1000000000000000000 n1070161 24936 24927 0 Apr 29 ? 0:05 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS_APPDEMO/94C4B1C10000000000 n1070161 24938 24927 0 Apr 29 ? 0:06 FNDLIBR FND Concurrent_Processor MANAGE OLOGIN="APPS_APPDEMO/94C4B1C10000000000 n1070161 24927 24922 0 Apr 29 ? 2:03 FNDLIBR FND CPMGR FNDCPMBR sysmgr ="" sleep=60 pmon=20 diag=N logfile=/u16/app The last process. Run the script. Truncation of the tables is a little drastic.
See pg.0.75. or activate it manually. the concurrent manager is run as an NT service.2: icmp_seq=0 ttl=255 time=0.0.0): 56 data bytes 64 bytes from 192. you will need to set it to Restart.91.91. 5-9 of this manual for instructions on creating the concurrent manager service.2: icmp_seq=1 ttl=255 time=1. the ICM will not restart it. you start and stop the managers using the Services control panel.2: icmp_seq=3 ttl=255 time=1.985 ms 64 bytes from 192. How many rows are in FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROCESSES tables? Depending on the specification of the system it has been seen that when . The ICM will start it the next process monitor session or the next time the ICM starts. Set APPLDCP to OFF and restart the managers. Why am I seeing pinging entries like this in the ICM logfile? PING (0.91. Use Activate to start a manager immediately.91. This means you have DCP turned on.705 ms 64 bytes from 192.vd11 13683 13660 0 May 11 ? 0:20 ARLIBR APPS/82A2A4940000000000000 000000000000000000000000000000000000000 AR ART The Conflict Resolution manager will look like: $ ps -ef grep FNDCRM n1070161 24941 24927 0 Apr 29 ? 1:17 FNDCRM APPS_APPDEMO/84BFBEB900000 0000000000000000000000000000000000000000000000 What is the syntax for controlling the concurrent manager using startmgr and concsub in NT? On NT.120 ms Process monitor session ended : 29-FEB-2000 10:38:43 64 bytes from 192. but it still did not start? Telling a manager to restart just sets the status to Restart. See the Applications Installation manual for NT. When a manager is deactivated manually. using the environment variable APPLDCP.75.2: icmp_seq=2 ttl=255 time=0. Appendix A for details.75.006 ms Pinging other machines is used in Distributed Concurrent Processing.75. I hit the Restart button to start the Standard manager.
then select the entries from the table. How do I turn on transaction manager diagnostics? Set the profile option 'Concurrent:Debug Flags' to 'TCTM1' at the site level. Use the following options: Enter = All.SYNCHRONOUS function. The program will be of type 'Immediate'. however. This will cause transactions to make debug entries in the FND_CONCURRENT_DEBUG_INFO table. 5) The manager sees the message in the pipe. and the manager packs its return status into the return pipe. Mode = AGE. and All requests depending on what is chosen.mgr log continuously grows where it may good to archive it regularly. 6) The manager runs the program with the specified parameters. the performance begins to diminish. You may want to run the Purge Concurrent Request and/or Manager Data on a regular basis. 2) A client program (usually a form) calls the FND_TRANSACTION. dependant on the amount of requests being run. Mode Value = 15 The std. there could be 30000-40000 rows in the tale before the performance begi ns to degrade. retrieves the program id and parameters. Starting the managers with diag=Y will also produce more information in the transaction manager logfile. The Purge Concurrent Requests job can be used to purge: Requests. 3) This function writes a message into the pipe containing the program to be run and its parameters. 7) The program completes.SYNCHRONOUS begins reading a return pipe for the return status. so there will not be a separate concurrent request run. Truncate this table before running a tranasction.tables reach above 3000-4000 rows. How do transaction managers work? Briefly: (See the server documentation for details on the DBMS_PIPE package) 1) A tranasction manager is started on the concurrent processing server. and periodically reads the pipe for incoming transactions. . Mgr logs. Any processes pending in Internal or Conflict Resolution Manager? Best course of action before starting the Concurrent Managers is to canc el any "Deactivate" or "Verify" jobs pending in the Internal Manager and pl ace any other pending jobs on hold. 4) FND_TRANSACTION.
the solution is to either increase the cache size for your Standard manger. (Query the concurrent manager by Login as Sysadmin. this regulates how many requests a manager will pick up for each sleep cycle. Basically. should be modified to handle more concurrent requests concurrently. or increase the actual number of Standard manager processes. Cache Size is set on the CONCURRENT/MANAGER/DEFINE form.. this can be done in two steps: (i) Increase the Number of Target processes for the manager (ii) Change the cache size of the concurrent manager as this determines how many requests will be evaluated by a manager at a time and should ma tch the target (process) value as set above. or times out waiting for it.. Solution. This is a synchronous transaction because the client waits for the server to return.. navigate -> Concurrent -> Manager -> Define and Query for the relevant concurrent manager).SYNCHRONOUS reads the return value and passes it back to its caller. When you try to submit a request like Active users or Active responsibilities. RELATED DOCUMENTS ----------------Note 1050938. you refresh-it gets completed.1 FND_CONC_PP_ACTIONS and FND_RUN_REQ_PP_ACTIONS Growing Exponen . Problem.. There is no specialization rules in any managers except the include program this source. you find that it is inactive / nomanager.the concurrent manager assigned is not picking up. Initially.6 What to Set $APPCPNAM for the Report Output File Naming Conven tion Format Note 149600. How do I process more concurrent requests concurrently? The Concurrent Manager parameters.8) FND_TRANSACTION. Within 12 to 15 seconds.. When we view the help requests. Most often when this occurs where a request goes "inactive/no manager" and is then processed a short time later.. you could find only inactive and we look at the diagnostic. Note that these events take place essentially simultaneously on the client and server. request gets submitted.
SQL .tially Note 134007.1 er Tables Related CMCLEAN. Important Note: this feedback is anonymously visible to other customers until pr ocessed by Oracle Support. Cancel .Non Destructive Script to Clean Concurrent Manag -------------------------------------------------------------------------------Products -------------------------------------------------------------------------------Oracle E-Business Suite > Applications Technology > Application Object Library > Oracle Application Object Library Back to top Rate this document Rate this document Excellent Good Poor Article Rating Did this document help you? Yes No Just browsing How easy was it to find this document? Very easy Somewhat easy Not easy Comments Provide feedback for this article. Please use 'Contact Us' for other feedback.
This action might not be possible to undo. Are you sure you want to continue?