Wednesday, 7 January 2015

oracle apps concurrent managers basics and information's

Concurrent Managers :
=====================
Recommend to go through Basic information about Concurrent Managers (Doc ID 69336.1)

We have below concurrent managers to server the request for user and system.ICM,Standard manager and Conflict resolution manager and we can also have custom manager.

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

++ 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.

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

++ Start CM

Status:
=======
adcmctl.sh start apps/appspwd

adcmctl.sh stop apps/appspwd

adcmctl.sh status apps/appspwd

adcmctl.sh abort apps/appspwd
Source the environment

In 11i
cd $COMMON_TOP/admin/scripts
$adcmctl.sh start apps/apps

In R12

cd $ADMIN_SCRIPTS_HOME
$adcmctl.sh start apps/apps


++ check CM is up and running
ps -ef|grep FNDLIBR
ps -ef|grep LIBR ==>ICM doubt FNDSM

++ Check the CM status

In concurrent manager -> administer ==> Actual /target values

++ some status of Concurrent manager

A. Standby = Request is put in standby mode while CRM is resolving the incompatibility.
B. No Manager = CM is down or no manager was defined.
C. Disabled = Concurrent Program is disabled.

Location:
=========

++ logfiles of concurrent managers under
$APPLCSF/$APPLLOG. ==> if not set in ENV

 Request Log files will go to

$<MODULE>_TOP/$APPLLOG

and output files will go to

$<MODULE>_TOP/$APPLOUT

++ For 12c  $INST_TOP/logs/appl/conc/log
++ ST log Standard Manager log?

log file $APPLCSF/log/<CONTEXT>/<CONTEXT>_9999.mgr
$APPLCSF/log/<Context Name>/FNDSM9999.mgr

Manager Log Files:
         Standard manager log:                   w<XXXXXX>.mgr
         Transaction manager log:                t<XXXXXX>.mgr
         Conflict Resolution manager log:        c<XXXXXX>.mgr
++ The Diag=Y parameter allows you to add debugging information into the concurrent log files for troubleshooting.
       
       
++ To move the log file to temp file:

eg. find $APPLCSF/$APPLLOG -type f -mtime +45|xargs -i mv -f {} /tmp/45more_log

++ Default scripts for troublshooting
 
    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 thatprocessed
                         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


++ Which program is excluded from standard manager and included in other manager.

SQL> SELECT A.INCLUDE_FLAG, A.QUEUE_APPLICATION_ID, C.USER_CONCURRENT_QUEUE_NAME,a
B.CONCURRENT_PROGRAM_NAME
FROM APPLSYS.FND_CONCURRENT_QUEUE_CONTENT A, APPLSYS.FND_CONCURRENT_PROGRAMS B, APPS.FND_CONCURRENT_QUEUES_VL C
WHERE type_id = b.concurrent_program_id and b.concurrent_program_name = '&SHORT_NAME' and c.concurrent_queue_id = a.concurrent_queue_id
/

++ FND_CONCURRENT_PROCESSES and FND_CONCURRENT_REQUESTS should not exceed 50K for optimal performance.

DBA_EXTENTS or DBA_OBJECTS Table..there you can get the SIZE of the Objects

++Puring tables:

FND_CONCURRENT_REQUESTS
FND_FILE_TEMP
FND_CRM_HISTORY
FND_TM_EVENTS
FND_TEMP_FILES
FND_ENV_CONTEXT
FND_DUAL
FND_CONFLICTS_DOMAIN

++ define Cm process should be

thumbrule= 4 + (2 * profile value).

++ ps -aex|grep FNDLIBR|grep ORCL

The above command will list out FNDLIBR process related to instance ORCL only in multi instance evn

Information center:
Concurrent Processing - Product Information Center (PIC) (Doc ID 1304305.1)

Basic information about Concurrent Managers (Doc ID 69336.1)
Note 453527.1 How To Trace a Concurrent Request And Generate TKPROF File
Troubleshooting Assistant: Oracle Concurrent Processing (Doc ID 1616330.2)
EBS - Technology Area - Webcast Recording 'E-Business Suite - Concurrent Manager Performance - Best Practices' [video] (Doc ID 1367676.1)
Concurrent Processing - Troubleshooting Concurrent Manager Issues (Unix specific) (Doc ID 104452.1)
Concurrent Processing - How to Debug Concurrent Request Transaction Managers from Oracle Applications Manager (OAM) (Doc ID 1308185.1)

No comments: