msouterblight1a
Member
All,
If I run select * from v$session where SID=<blocking sid> I can determine the PID of the Call Object Kernel and the thread, I can then look at that in Server Manager to determine the user and application. But, this only works if the issue is coming from the Enterprise Server. If someone runs a wide open query from the web client and it starts eating up CPU, etc. I can determine the SID on the datbase, and it will show me the PID for the WebLogic process, and even the thread, but I don't have any way to associate that with the JDE user.
Does anyone have any ideas of how to do this?
Matthew
If I run select * from v$session where SID=<blocking sid> I can determine the PID of the Call Object Kernel and the thread, I can then look at that in Server Manager to determine the user and application. But, this only works if the issue is coming from the Enterprise Server. If someone runs a wide open query from the web client and it starts eating up CPU, etc. I can determine the SID on the datbase, and it will show me the PID for the WebLogic process, and even the thread, but I don't have any way to associate that with the JDE user.
Does anyone have any ideas of how to do this?
Matthew