有关并发管理器的文章

BASIC INFORMATION ABOUT CONCURRENT MANAGERS

This article is intended to familiarize you with the basic functionality and
processes of the concurrent managers.

TABLE OF CONTENTS

1. Concurrent Manager Basics
2. Starting the Concurrent Managers
3. Stopping the Concurrent Managers
4. Location of Concurrent Manager Log Files
5. FNDLIBR Processes on the Server
6. Cleaning out Concurrent Manager Tables
7. PMON Method Information
8. Helpful Diagnostic Scripts

1. CONCURRENT MANAGER BASICS

A. The ICM (Internal Concurrent Manager) controls all of the other
concurrent managers.

B. The Standard Manager accepts any and all requests. It has no
predefined specialization rules and is active all the time. It is not
recommended to add specialization rules to the standard manager as it
can cause problems.

C. The Conflict Resolution Manager resolves conflicts, such as request
incompatibilities.

2. STARTING THE CONCURRENT MANAGERS

A. There are two ways to determine if the concurrent managers are up and
running:

1. Log in to applications as System Administrator responsibility and
navigate to the concurrent manager administration page (Concurrent,
Manager, Administrator) and under the processes column if the
target and actual column equal the same number (above 0) this means
the managers are up and running.

2. You can also go into SQL*PLUS as APPS and run the following script.:

SQL> @$FND_TOP/sql/afimchk.sql

This script. will return output similar to the below:

Status Since Method
-------------------------------------- --------- ----------- ------
Internal Conc Manager is running on - colapp03 05-MAR-99 06:41:32 PM LOCK

B. Use this syntax to start the concurrent managers from the command line:

Startmgr sysmgr=apps/apps (10.7 & 11.0)

adcmctl.sh apps/ start (11.5)

C. On Windows NT, the concurrent managers are started with a service.
This is created by using the following command:

cmsrvadm add [automatic/manual]

Please refer to the NT installation manuals for more detailed
information on this topic.

3. STOPPING THE CONCURRENT MANAGERS

You stop the concurrent managers from the command line:

CONCSUB apps/apps SYSADMIN 'System Administrator' SYSADMIN CONCURRENT FND
DEACTIVATE or ABORT

DEACTIVATE tells the managers to complete processing of any running
requests before terminating. This is a cleaner way of bringing down the
managers.

ABORT tells the managers to terminate the managers immediately.
When the concurrent managers are terminated through the abort command,
the jobs that they were running will be returned to pending status.

adcmctl.sh apps/ stop (11.5)

On NT you need to stop the service.

4. LOCATION OF CONCURRENT MANAGER LOG FILES

A. The concurrent manager log files can be located in one of the following
places:

1. If the environment variable $APPLCSF is set, the default location
is $APPLCSF/$APPLLOG

2. If the environment variable $APPLCSF is not set, the logs go to
$FND_TOP/$APPLLOG

The default name of the concurrent manager log files is std.mgr. You
can change these by setting the parameter logfile=.

3. On NT the log files are called CM_.LOG

B. The logfile= parameters can be appended for additional
functionality. This parameter allows you to specify the name of the
log file. The default name of the log file is std.mgr.

C. The Diag=Y parameter allows you to add debugging information into the
concurrent log files for troubleshooting.

Manager Log Files:

Standard manager log: w.mgr
Transaction manager log: t.mgr
Conflict Resolution manager log: c.mgr

Where: is the concurrent process id of the manager

5. FNDLIBR PROCESSES ON THE SERVER MACHINE

When the concurrent managers are up, they create an FNDLIBR process on the
server machine. If the concurrent managers are up, one FNDLIBR process
will appear for the ICM and each Standard manager that is defined.

On UNIX, you can locate this FNDLIBR process by doing the following:

ps -ef | grep -i FNDLIBR

On NT, you check the task manager, under the processes tab to see the
FNDLIBR process.

6. Please reference Note 134007.1 cmclean.sql & Note 171855.1 Diagnostic Script. for Concurrent Manager.

7. PMON METHOD INFORMATION

Ensure that the PMON method is set to LOCK. Using the LOCK method has been
recommended since Version 10.6.

You will usually have one of two settings for PMON:

1. RDBMS= the internal manager queries against fnd_v$process to
retrieve the session id and the operating system process id.

2. LOCK= the internal concurrent manager tries to lock on the process
it is monitoring.

If you use the diag=y option in your start manager command then the PMON
method being used will be written on the first page of the log file.

To change the PMON method do the following in sqlplus as APPLSYS:

1. SQL> @$FND_TOP/sql/afimpmon.sql (10.7)

The following line will appear:

"If you wish to continue type the word 'dual':"

Type: dual.
Enter value for 1:
Type: LOCK

2. SQL> @$FND_TOP/sql/afimpmon.sql (11.0)

The afimpmon.sql script. was updated to prompt only for one parameter,
'dual' and then automatically changes the PMON method to LOCK.

8. HELPFUL DIAGNOSTIC SCRIPTS

The following SQL scripts located under $FND_TOP/sql are useful when
diagnosing concurrent manager problems:

1. afimchk.sql Tells the status of the ICM and PMON method

2. afcmstat.sql Lists active manager processes

3. afrqrun.sql Lists all the running, waiting and terminating
requests

4. afrqwait.sql Lists requests that are constrained and waiting
for the ICM to release them

5. afrqscm.sql Prints log file name of managers that can run a
given request. It can be used to check for possible
errors when a request stays in pending status. It
requires a request id value.

6. afcmcreq.sql Prints the log file name of the manager that processed
the request

7. afrqstat.sql Summary of completed concurrent requests grouped by
completion status and execution type. It requires
number of days prior to today on which to report
parameter.

8. afimlock.sql Lists locks that the ICM is waiting to get

9. afcmrrq.sql Lists managers that currently are running a request

 

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/209689/viewspace-589300/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/209689/viewspace-589300/