False Alerts For Concurrent Processing In OEM 12c

False Alerts For Concurrent Processing In OEM 12c There are false alerts from the Enterprise Manager (EM) console alerting about services down, but they are showing UP in the EM console and E-Business Suite (EBS). Timeout parameters are too low not allowing the correct acknowledge of the target status from EM.  1. Change the following parameters in the /sysman/config/emd.properties file:   dynamicPropsComputeTimeout_oracle_database=800   dynamicPropsComputeTimeout_host=480   agentJavaDefines=-Xmx2048M -XX:MaxPermSize=1024M   dynamicPropsComputeTimeout_oracle_ebs=800 Ignore step #2 if the service shows as UP in the console. 2. Login to EBS Console a. Go to Targets-->Oracle E Business Suite, Select the EBS Target on which 'Inventory Manager' is shown. b. Open "EBS Target Menu" -->Monitoring-->Metric and Metric Collection Settings. c. Change View "All Metrics", all metrics are displayed, go to "Native Services" , click on 'Every 15 Minutes' in 6th column next to "Native Services". d. Change the value from 15 mins to 30 or 45 mins. e. Save and re-test.

Concurrent Processing - Creating a Conflict Domain for a Concurrent Program

As SYSADMIN in Systems Administrator Responsibility

1) In CONCURRENT > CONFLICT DOMAIN Form

DOMAIN SHORTNAME DESCRIPTION
458 458
204 204

SAVE

NB: 458 = Vision Services org id
       204 = Vision Project Mfg org id

2) CONCURRENT > PROGRAM > DEFINE

Query PRC: Interface Revenue to General Ledger
Select Incompatiblities

Set the "Type" field value to Domain for PATTGL and save.


3) PROFILE > SYSTEM OPTION > Concurrent:Conflicts Domain

PROFILE > SYSTEM Query " CONCURRENT: CONFLICTS DOMAIN"
at the responsibility level:

Projects, Vision Services (USA) -- set the profile to 458
Projects, Vision Project Mfg (MRC) -- set the profile to 204

SAVE


4) CONCURRENT >PROGRAM > DEFINE

Query PRC: Interface Revenue to General Ledger

INCOMPATIBILITIES TAB > Remove Program "PRC: Interface Revenue to General

SAVE

As the conflict domain has been setup the incompatibility that PRC: Interface Revenue to General Ledger has with itself is then removed. 

For more Use the Concurrent Processing - Creating a Conflict Domain for a Concurrent Program (267167.1)

There are many dead processes for WFMGSMS Concurrent Manager

The Internal Concurrent Manager log file reports many dead processes referencing WFMGSMS (Workflow Summary Mailer Concurrent Manager) Concurrent Manager.

For example:

Found dead process: spid=(14546), cpid=(506393), Service Instance=(1064)
Starting WFMGSMS Concurrent Manager : 12-MAR-2009 05:32:23
Process monitor session ended : 12-MAR-2009 05:32:25

Solution:

To implement the solution, please execute the following steps:

1. Login as System Administrator.
2. Navigate to Concurrent / Manager / Define.
3. Query the "Workflow Mailer" and disable it.
4. In the same screen, query the "Workflow Summary Mailer", and disable it.
5. Bounce the Concurrent Managers.

Problem: Concurrent Manager Request Status Remains Terminating Indefinitely

Concurrent Manager Request Status Remains Terminating Indefinitely

Symptom: Concurrent request status Remains Terminating Indefinitely

Cause: It is be because concurrent manager table need a cleanup

Solution:

Run the below commands from apps user.

update fnd_concurrent_queues Set running_processes=0, max_processes=0;

delete from fnd_concurrent_processes;

Update fnd_concurrent_requests set status_code = 'X', phase_code = 'C' where status_code = 'T';

commit;