Doc ID 2089560.6
PROBLEM DESCRIPTION
-------------------
You are logged on to a server running multiple Oracle Applications instances,
and you want to know if there are any concurrent managers processes running
for a particular instance running.
The following command:
ps -ef | grep FNDLIBR
shows all FNDLIBR processes running on the server. However, how can you tell
which processes are associated with which instance? How can you find all other
concurrent manager processes and System PIDs?
SOLUTION DESCRIPTION
--------------------
You need to run $FND_TOP/sql/afcmstat.sql as the APPS user in the
APPL_TOP/instance you are interested in.
The section labeled: "Managers with their corresponding Oracle and System
Process Id's" contains the information you are looking for. If the internal
manager is not running, you will not get a list under the heading.
These SQL scripts are useful in diagnosing concurrent manager related
problems. The names are listed below (located in $FND_TOP/sql):
NAME DESCRIPTION
-----------------------------------------------------------------
afcmstat.sql Lists active manager processes along with
defined max capacity to be in effect at the
present time. Note: could be slow if table
FND_CONCURRENT_PROCESSES is large (since
history is maintained in it).
afimchk.sql Tells the status of ICM and PMON method in effect.
afrqrun.sql Lists all the running, waiting (waiting to be
registered after sub requests completed) and
terminating requests.
afrqwait.sql Lists requests that are constrained and thus
waiting for the ICM to release them.
afrqscm.sql Prints log file name of managers that can run a
given request. Helpful when a runnable request
stays pending to check for possible error
messages in manager log file.
afcmcreq.sql Prints the log file name of the manager that
processed the request (takes request id as
argument).
afrqstat.sql Summary of completed concurrent requests
grouped by completion status and execution type.
afimlock.sql Lists locks that the ICM is waiting to get.
afcmrrq.sql Lists managers that are currently running a
request (username, request id, program name,
start date, etc).
No comments:
Post a Comment