Concurrent manager log file locations in R12.2

By -

Concurrent manager log file location:
Concurrent manager log files are located under $APPLCSF and $APPSLOG home

 [oracle@VIS ~]$cd $APPLCSF

 [oracle@VIS conc]$pwd
/apps/applmgr/fs_ne/inst/VIS/logs/appl/conc

 [oracle@VIS conc]$cd log/

 [oracle@VIS log]$pwd
/apps/applmgr/fs_ne/inst/VIS/logs/appl/conc/log
[oracle@VIS log]$

 Internal concurrent manager log file:
[oracle@VIS log]$ls -lrt *$TWO_TASK*

 Standard manager log file:
[oracle@VIS log]$ls -lrt w*.mgr

 Conflict resolution manager log file:
[oracle@VIS log]$ ls -lrt c*.mgr

Output post processer log file:
[oracle@VIS log]$ps -ef |grep OPP

Concurrent program related some basic SQL queries

How to find concurrent program status?
SQL> select REQUEST_ID,phase_code,status_code,ORACLE_SESSION_ID from apps.fnd_concurrent_requests where request_id=’1234567’;

How to find concurrent request output and log file location?
SQL> select LOGFILE_NAME, OUTFILE_NAME from fnd_concurrent_requests where request_id='1234567';

How to find which concurrent manger ran a specific concurrent request?
SQL> select b.USER_CONCURRENT_QUEUE_NAME from fnd_concurrent_processes a,fnd_concurrent_queues_vl b, fnd_concurrent_requests c where a.CONCURRENT_QUEUE_ID = b.CONCURRENT_QUEUE_ID and a.CONCURRENT_PROCESS_ID = c.controlling_manager and c.request_id ='856272604';

How many rows are in FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROCESSES tables?
select count(*) from FND_CONCURRENT_REQUESTS;
select count(*) from FND_CONCURRENT_PROCESSES;
Concurrent program phase code and status code Details

STATUS_CODE Column:

 A Waiting
B Resuming
C Normal
D Cancelled
E Error
F Scheduled
G Warning
H On Hold
I Normal
M No Manager
Q Standby
R Normal
S Suspended
T Terminating
U Disabled
W Paused
X Terminated
Z Waiting

PHASE_CODE column

 C Completed
I Inactive
P Pending
R Running



Comments

Post a Comment

Popular posts from this blog

How to troubleshoot long running concurrent request in R12.2

By -
We frequently encounter issues with concurrent programs running long and concurrent requests not picking up jobs. These problems are often expected from the development and functional team we need to address this issue To solve this, we should take the following steps: Collect below basis level of information to development team 1 Oracle seeded program/Custom program? 2 How much time it used earlier? 3 Is there any recent code change done in concurrent program? 4 Is this program fetching higher data compare to last run? 5 Does this job running any specific time/ It can be run any time? 6 Does this job fetching data using DB link? 7 Does the problem happen on both the test and production instance?   Troubleshooting Steps for Concurrent Requests Check for Locks and Blocking sessions Identify if the request is running but blocked by database locks/Blocking sessions. Use DBA tools or queries to identify and release locks if necessary. Review Parameters and Data ...
Read more

How to run Gather Schema Statistics in R12.2

By -
Image
What is Gather Schema Statistics? Gather Schema Statistics program generates statistics that quantify the data distribution and storage characteristics of tables, columns, indexes, and partitions. The cost-based optimization (CBO)  uses these statistics to calculate the selectivity of prediction and to estimate the cost of each execution plan. Why Run the Gather Schema Statistics? When Data is update, insert, delete in table of user end Like (Technical User ,Finance User ,Ect) It become necessary to run the Gather Schema Statistics It’s recommended to Run GSS in Weekly Once or twice. How to run Gather Schema Statistics? Login application with sysadmin user Submit Request Window Navigate to: Concurrent > Requests Enter the parameters This can be run for specific schemas by specifying the schema name or enter ‘ALL’ to gather statistics for every schema in the database Submit the Gather Schema Statistics program Parameters: S...
Read more

How to clear weblogic stuck threads in R12.2

By -
Web logic stuck threads Overview   What is stuck threads in weblogic server? Stuck threads are  long running threads and It means thread has been running longer predefined timeout.   What stuck threads will do? A thread might get stuck for various reasons.   Example :  When an SQL query is running and the time it takes to complete is say 800 seconds, then, as the default stuck thread timing is 600 seconds in WebLogic Server, the thread allocated for that query waits for 600 seconds and goes to stuck state. Then managed server status showing waning state   How to troubleshoot the stuck threads in EBS instance? Stuck threads will reduce the ebs performance and it’s very important activity to DBA’s Step 1: Go to the weblogic console and check for managed server status like oacore Step 2: if It will show the oacore server in “warning state” then we need to check   Scenario 1: Every alert we need to check the log file and investigate based on the log ...
Read more