Beruflich Dokumente
Kultur Dokumente
How to resolve All Concurrent Requests stuck in pending phase or Some Concurrent
Manager 's status show Target node/queue unavailable?
History
1. 2009-03-23 Initialization
Reference
--------
Scope
--------
--------
2.Before starting the concurrent managers using adcmctl.sh,Make sure all concurrent
managers process FNDLIBR have been shutdown at the OS level.
for example:
>ps -ef|grep $USER|grep FNDL
if there still have FDNLIBR processes still running.
>kill -9 PID
PID form output of the command ps in previous step.
5.Make sure customize env file has been added in env file which used in Concurrent
Manager start/stop scripts adcmctl.sh.
if your environment have user defined customize env files,please sure they have been
added in env file used in adcmctl.sh.
7.Rebuild the concurrent manager views. As applmgr run the following from the OS:
This is non-destructive.
Concurrent Manager views can be rebuilt by running the following command at the
command line:
e. Change the profile option for 'Concurrent: Active Request Limit' to Null (blank).
f. Exit Oracle Applications and log in again for the change to take affect.
10. The Concurrent managers were brought down, while an outstanding request was still
running in the background. In which case, update the
sql>
update fnd_concurrent_requests
where status_code='T';
sql> commit;
STATUS_CODE
2 from fnd_lookups
4 order by lookup_code;
LOOKUP_CODE MEANING
--------------- --------------------
A Waiting
B Resuming
C Normal
D Cancelled
E Error
G Warning
H On Hold
I Normal
M No Manager
P Scheduled
Q Standby
R Normal
S Suspended
T Terminating
U Disabled
W Paused
X Terminated
Z Waiting
PHASE_CODE
2 from fnd_lookups
-------------- --------------------
C Completed
I Inactive
P Pending
R Running
This value should be NULL (CRM is running; target and actual process amount are the
same), or 'A' ('Activate concurrent manager' control status).
update fnd_concurrent_queues
commit;
d. Verify the status of the concurrent managers through the Concurrent -> Manager
-> Administer form.
If the CRM is still not active, bounce (deactivate, activate) the Internal Concurrent
Manager. This is done through the Concurrent > Manager > Administer form from the
'System Administrator' responsibility. It can also be done through the CONCSUB
command at the command level.
Setting the control_code to 'A' in the fnd_concurrent_queues table for the Conflict
Resolution Manager indicates that this concurrent manager is to be activated with the
parameter values specified through this table for this manager (MAX_PROCESSES,
CACHE_SIZE, etc).
Control_code
2 from fnd_lookups
4 order by lookup_code;
LOOKUP_CODE MEANING
--------------- --------------------
A Activating
B Activated
D Deactivating
E Deactivated
P Suspended
R Restarting
T Terminating
U Updating environment information
V Verifying
X Terminated
12. What is the cache size? Try increasing the cache size then stop/restart the concurrent
managers.
If concurrent requests are rarely prioritized and there are managers that service short-
running requests, consider setting the cache size to equal at least twice the number of
target processes. This increases the throughput of the concurrent managers by attempting
to avoid any sleep time.
For example:
If more than one manager or worker processes the same type of requests with only a
small cache size, it may be unable to process any jobs in a single processing cycle,
because other processes have already run the cached requests. When this happens, it is
important to note that the manager will sleep before refreshing its cache. To increase
manager throughput where there are sufficient requests of the required type in the queue,
increase the cache size to improve the chance of the manager finding work to process and
thus avoid having to enter a sleep phase.
TIP: Ensure that the system is not resource-constrained before attempting to increase the
rate of concurrent processing in this way, otherwise,
these changes may actually reduce concurrent processing throughput because jobs take
longer to run.
Enter the number of requests your manager remembers each time it reads which requests
to run. For example, if a manager's workshift has 1 target process and a cache value of 3,
it will read three requests and wait until these three requests have been run before reading
new requests.
In reading requests, the manager will only put requests it is allowed to run into its cache.
For example, if you have defined your manager to run only Order Entry reports then the
manager will put only Order Entry requests into its cache.
If you enter 1, the concurrent manager must look at its requests list each time it is ready
to process another request.
By setting the cache size at a higher number, the concurrent manager does not have to
read its requests list each time it runs a request. However, the manager does not recognize
any priority changes you make for a particular request if it has already read that request
into its cache. Further, even if you give a higher priority to a new request, that new
request must wait until the buffer is empty and the manager returns to look at the requests
list. That request may have to wait a long time if you set the buffer size to a high number.
You should use cache size to tune your concurrent managers to work most efficiently for
you site's needs. If your organization tends to reprioritize jobs going to a certain manager,
that manager should have its buffer size set fairly low.
Suggestion: Enter a value of 1 when defining a manager that runs long, time-consuming
jobs, and a value of 3 or 4 for managers that run small, quick jobs.
13.Concurrent Manager [Output Post Processor] can not be started with Actual is 0 and
Service Info %%service threads running.
Select [Output Post Processor] in Administer and click [Processes] button in lower right
corner,verify [Start Date],if it early than restart date,you should Terminate it first in main
windows and the restart it.
15.if "The target node/queue unavailable" had been shown after cloning or Adding
new node.
>sqlplus apps/appsuat
Connected to:
1 row updated
SQL> commit;
Commit complete
SQL> exit
16.from note:738405.1,if the Internal Concurrent Manager starts, but all others managers
have a status of 'Target queue/node unavailable'.
and the log file of internal Concurrent Manager shows the following errors:
>ping hostname
@END