Tuesday, December 6, 2022

How to Kill Long Running Concurrent Job in R12

 

How to Kill Long Running Concurrent Job in R12


Step 1) Find SID and Serial Number for Concurrent Job
Step 2) Kill the long running session
Step 3) Update fnd_concurrent_requests table to mark the request in error and completed


STEP1:

SELECT a.request_id, d.sid, d.serial# ,d.osuser,
d.process , c.SPID ,d.inst_id
FROM apps.fnd_concurrent_requests a,
apps.fnd_concurrent_processes b,
gv$process c,
gv$session d
WHERE a.controlling_manager = b.concurrent_process_id
AND c.pid = b.oracle_process_id
AND b.session_id=d.audsid
AND a.request_id = 344625347--------------req id
AND a.phase_code = 'R';

STEP2:

select ORACLE_PROCESS_ID from apps.fnd_concurrent_requests where REQUEST_ID=&REQUEST_ID;

select ORACLE_PROCESS_ID from apps.fnd_concurrent_requests where REQUEST_ID=&REQUEST_ID;

alter system kill session ‘sid,serial#’ immediate:

STEP3:

 UPDATE fnd_concurrent_requests
SET phase_code = 'C', status_code = 'D'
WHERE Request_id=&request_id;


If this does not solve your problem then try restarting Standard Concurrent Manager and Output Post Processor Concurrent Manager.






Table import and export.

Create Data Pump Directory. The first step in Oracle Data Pump is to create an OS level directory which will be used by Oracle for perform...