(转)How To Kill runaway processes After Terminating Concurrent Request

Every concurrent Request uses some resources for running. If we find that the concurrent request is taking long time and decided to terminate the concurrent request , the resources may not be released soon. These processes are called runaway processes. So we need to manually kill the processes at database and os level to have the resources released to the system. 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 ;
SQL> alter system kill session ‘session-id,session-serial’ $ kill -9 <server pid>  
Complete details about the request can be found using the following query :
SELECT   qt.user_concurrent_queue_name ,
         fcr.Request_Id Request_id     ,
         fu.User_name                  ,
         p.spid                        ,
         s.sid
                  ||’,
         ‘
                  || s.serial# SIDSERIAL ,
         SUBSTR( Fcpv.Concurrent_Program_Name
                  ||’ – ‘
                  || Fcpv.User_Concurrent_Program_Name, 1,46) Program           ,
         TO_CHAR( fcr.actual_start_date, ‘mm/dd hh24:mi’ )    actual_start_date ,
         phase_code                                                             ,
         status_code                                                            ,
         TO_CHAR( TRUNC(SYSDATE) + ( SYSDATE – fcr.actual_start_date ) , ‘hh24:mi:ss’ ) duration
FROM     apps.Fnd_Concurrent_Queues Fcq     ,
         apps.fnd_concurrent_queues_tl qt   ,
         apps.Fnd_Concurrent_Requests Fcr   ,
         apps.Fnd_Concurrent_Programs Fcp   ,
         apps.Fnd_User Fu                   ,
         apps.Fnd_Concurrent_Processes Fpro ,
         v$session s                        ,
         v$process p                        ,
         apps.Fnd_Concurrent_Programs_Vl Fcpv
WHERE    phase_code              = ‘C’
AND      status_Code             = ‘X’
AND      s.paddr                 = p.addr
AND      fcr.requested_by        = user_id
AND      fcq.application_id      = qt.application_id
AND      fcq.concurrent_queue_id = qt.concurrent_queue_id
AND      userenv(’lang’)         = qt.language
AND      fcr.os_process_id       = s.process
AND      fcr.Controlling_Manager = Concurrent_Process_Id
AND
         (
                  fcq.concurrent_queue_id = fpro.concurrent_queue_id
         AND      fcq.application_id      = fpro.queue_application_id
         )
AND
         (
                  fcr.concurrent_program_id  = fcp.concurrent_program_id
         AND      fcr.program_application_id = fcp.application_id
         )
AND
         (
                  fcr.concurrent_program_id  = fcpv.concurrent_program_id
         AND      fcr.program_application_id = fcpv.application_id
         )  

(转)How To Kill runaway processes After Terminating Concurrent Request

时间: 2024-11-03 22:11:52

(转)How To Kill runaway processes After Terminating Concurrent Request的相关文章

How to Kill All Processes That Have Open Connection in a SQL Server Database[关闭数据库链接 最佳方法] -摘自网络

SQL Server database administrators may frequently need in especially development and test environments  instead of the production environments to kill all the open connections to a  specific database in order to process SQL Server maintenance task ov

Concurrent Request:Inactive phase,No Manager status

Symptom 随便submit一个request,发现几乎所有的Concurrent Manager都为No Manager状态,Phase为Inactive. Solution 一个Concurrent Request的生命周期包含不同的阶段(Phase):Pending, Running, and Completed,并且对于每一个Phase,又可能会有不同的状态. Pending Phase - Normal, Standby, Scheduled, Waiting Running Ph

基于CentOS与VmwareStation10搭建Oracle11G RAC 64集群环境

1.资源准备 最近,在VmwareStation 10虚拟机上,基于CentOS5.4安装Oracle 11g RAC,并把过程记录下来.刚开始时,是基于CentOS 6.4安装Oracle 11g RAC, 没有成功,主要是Oracle 11g RAC安装,没有针对CentOS 6.4的内核的一些包. 本文内容详实,包括安装过程中遇到的一些问题,也单独编一章节,第四章节的FAQ. http://blog.chinaunix.net/xmlrpc.php?r=blog/article&id=46

Oracle Study之--Oracle 11g RAC故障(Failed to create or upgrade OLR)

Oracle Study之--Oracle 11g RAC故障(Failed to create or upgrade OLR) 系统环境:       操作系统: RedHat EL5.5       Cluster:   Oracle Grid 11.2.0.1.0       Oracle:     Oracle 11g  11.2.0.1.0 故障现象:             在Oracle 11gR2  RAC添加新节点的过程中,在new node上运行root.sh时出现以下故障:

Worker Thread

http://www.codeproject.com/Articles/552/Using-Worker-Threads Introduction Worker threads are an elegant solution to a number of problems about concurrent processing; for example, the need to keep the GUI active while a computation is being performed.

关于Oracle E-Business Suite并发处理机制(Current Processing)

2012年写过一篇关于Oracle E-Business Suite并发管理器的文章,回头看之前总结的内容还是比较单薄,很多点没说到,最近在看这块的内容,索性再写一篇稍微完整的文章来. Oracle E-Business Suite并发处理机制(Current Processing)的好处 区别于普通功能的处理机制,并发处理机制其实是一个异步处理机制,它把程序放到后台来运行,前台的操作还给用户,允许用户可以继续做其他业务. 技术上将,异步处理的好处是降低系统特定时间点的负载,提升系统资源的整体使

CRS-0184: Cannot communicate with the CRS daemon.之节点脱离集群问题解决

1.系统环境: OEL6.5企业版 Oracle11.2.0.2 RAC + ASM 2.报错信息: $ crs_stat -t CRS-0184: Cannot communicate with the CRS daemon. $ crsctl check has CRS-4639: Could not contact Oracle High Availability Services 3.报错原因查找: 在节点1节点查看IP地址,VIP已经不存在 $ ifconfig -a en0: fla

【Android】-- adb shell 命令探索

ADB是什么,做android开发的没有不知道的. window下运行cmd,输入adb help就会打印adb都能够做的事情,包括 adb push ..adb pull .. adb devices  adb install... 等等..并且一搜一大把. 其中有一个命令叫做  adb shell,android是基于linux的,shell模式下linux的命令可是非常多的,android去掉了许多linux的命令,那么从这写命令里面又能够发现什么宝藏呢?寻宝之旅开启!! 首先linux的

Android Activity为什么要细化出onCreate、onStart、onResume、onPause、onStop、onDesdroy这么多方法让应用去重载?

原文:http://www.xuebuyuan.com/1608083.html 最近在研究Activity的启动流程,老罗的blog在看,也找了其它资料学习,也跟过Android4.3的源码, 在跟代码的过程中,突然想到下面的这个问题: 网上太多根据Android开发规范翻译转载的内容,都不是我想要的答案,那就自己分析下. 如下是一段典型的Activity间切换的日志,从AActivity切换到BActivity: 10-17 20:54:42.247: I/com.example.servi