Sunday, February 21, 2021

How To Kill runaway processes After Terminating Concurrent Request

 

Every concurrent Request uses some resources for running.

 

If we decided and terminate the conc request which is taking long time and not progress any more further after terminate it from front end, some times the resources may not be released soon. these processes are called runway process which will be create blocking other sessions.


so we need to manually kill the processes at DB and OS level.

 

Once terminate the concurrent request from the front end.

 

Then


SQL>select request_id,oracle_process_id,os_process_id from fnd_concurrent_requests where request_id=’&Req_Id’;
SQL>select p.spid , s.sid , s.serial# from v$session s , v$process p where s.paddr = p.addr and s.process = &os_process_id ;

 

Kill session id in Database

SQL> alter system kill session ‘session-id,session-serial’

 

killpid at OS level
$ kill -9 <server pid>

 

 

 

No comments:

Oracle Database Password Management: Resetting Password Policies and User Account Expiry Issues

  Checking Password Lifetime Policy Oracle password expiration rules are controlled through profiles. The following query helps identify the...