Hi Erman,
This post is for two abnormal behavior: 1- some requests are taking longs and finish with the follwoing error message: Post treatment of the request 1459987 failed at .... with error message: Post-treatment of the output is run but it was not selected. No other test of post-treatment will be done and the request is marqued with warning status. Definition of Option profile "Concurrent:OPP Response Timeout" with a higher value should be necessar. --> I checked Concurrent:OPP Reponse Timeout profile option is set to 20000 ?? 2. For the same requests: - Concurrent manager CM1 should run some type requests a - Concurrent manager CM2 should run some type requests b. The problem is that , CM1 ran b and CM2 ran a ... NB: One of them is the Standard Manager. I checkef the CMs rules specialisation, they are ok. Any Help please ? Regards, Latifa |
Administrator
|
Hi latifa,
For 1, send me the log For 2, send me the specialization rules (screenshot) |
Hi Erman, Here it's an example among similar other requests: l1459982.req NB: Error message is in frensh (generated like this) Screen Shot of the specialized Concurrent Manager rules specialization Specialization_Rules.docx Regards, Latifa |
Administrator
|
for 1) What is in OPP log file (for the request 1459987 ) ?
for 2) I only see one specialization rule screen, what about the other conc manager' specializations? Also check the specializations from the backend.. There is a query in note : "Concurrent Processing 11i - R12 : What To Do If A Concurrent Request Is Inactive With No Manager Status? (Doc ID 1311526.1)" - Step 2: Ex: select 'Concurrent program '||fcp.concurrent_program_name||' is ' ||decode(fcqc.include_flag,'I','included in ','E','excluded from ')||fcqv.user_concurrent_queue_name specialization_rule_details from fnd_concurrent_queues_vl fcqv,fnd_concurrent_queue_content fcqc,fnd_concurrent_programs fcp where fcqv.concurrent_queue_id=fcqc.concurrent_queue_id and fcqc.type_id=fcp.concurrent_program_id and fcp.concurrent_program_name='<PROGRAM_SHORT_NAME>'; Note: Program Short Name is visible when the program is queried in concurrent program definition form. Example: SQL> select 'Concurrent program '||fcp.concurrent_program_name||' is ' ||decode(fcqc.include_flag,'I','included in ','E','excluded from ')||fcqv.user_concurrent_queue_name specialization_rule_details from fnd_concurrent_queues_vl fcqv,fnd_concurrent_queue_content fcqc,fnd_concurrent_programs fcp where fcqv.concurrent_queue_id=fcqc.concurrent_queue_id and fcqc.type_id=fcp.concurrent_program_id and fcp.concurrent_program_name='OKCRAQE'; SPECIALIZATION_RULE_DETAILS ----------------------------------------------------------------------------- Concurrent program OKCRAQE is included in Contracts Core Concurrent Manager Concurrent program OKCRAQE is excluded from Standard Manager |
Hi Erman,
1) There is nothing for the request in the OPP log file 2) please find the specialization rules for the standard manager: specialization_rules_standard_manager.docx Regards, Latifa |
Administrator
|
According to your screenshots, CM1 is the "standard manager".
You are Excluding that program using "Request Type" (not program name). Are you aware of that? Ref Oracle Support: If a manager is created to run a particular concurrent program a 'request type' must be created and associated with that manager. A specialization rule should also be added to the new manager to INCLUDE that particular request type. Then add a specialization rule to the STANDARD manager to EXCLUDE this new request type. E.g. program = CustomProgram New Request type = Custom Associate CustomProgram with Custom request type using define program screen add EXCLUDE rule to STANDARD manager to exclude request type CUSTOM add INCLUDE rule to the custom manager to include request type CUSTOM |
Free forum by Nabble | Edit this page |