| High CPU for inactive session [message #571234] |
Thu, 22 November 2012 06:01  |
sathik
Messages: 196
Registered: August 2009
Location: INDIA
|
Senior Member |
|
|
when I was analyzing high CPU utilization issue, I saw that the most of the top PID's were INACTIVE in database. But it was utilizing more than 4% CPU. how it is utilizing CPU without doing any work in database?
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
24013 oracle 2167M 1581M sleep 53 0 0:01:53 20% oracle/1
13260 oracle 2167M 1580M sleep 30 0 0:01:16 14% oracle/1
24399 oracle 2167M 1582M sleep 59 0 0:03:01 4.2% oracle/1
11509 oracle 2178M 1593M sleep 59 0 0:02:10 2.8% oracle/11
16216 oracle 1040K 832K sleep 16 2 0:00:00 1.2% find/1
12276 oracle 2166M 1579M sleep 59 0 0:00:29 0.9% oracle/1
24227 oracle 2167M 1582M sleep 59 0 0:02:16 0.6% oracle/1
24011 oracle 2169M 1583M sleep 59 0 0:02:28 0.6% oracle/1
10876 oracle 2167M 1581M sleep 59 0 0:02:57 0.4% oracle/1
28703 oracle 2169M 1583M sleep 59 0 0:02:16 0.3% oracle/11
16067 oracle 2135M 1563M sleep 59 0 0:00:04 0.3% oracle/1
2880 root 14M 5504K sleep 59 0 4:30:10 0.3% scopeux/1
921 root 57M 16M sleep 29 10 30:46:59 0.2% java/12
24628 oracle 2167M 1581M sleep 59 0 0:02:08 0.2% oracle/1
12866 nettrap0 4840K 4640K cpu0 59 0 0:00:05 0.2% prstat/1
16136 oracle 1912K 1456K sleep 53 2 0:00:00 0.1% lpmon_flag_mana/1
17160 oracle 2139M 1553M sleep 59 0 3:55:20 0.1% oracle/11
7587 oracle 169M 79M sleep 59 0 13:24:23 0.1% emagent/17
15461 oracle 45M 17M sleep 59 0 0:04:33 0.1% httpd/5
2910 root 1064K 696K sleep 59 0 0:39:55 0.1% perf64/1
679 root 3792K 2384K sleep 59 0 4:14:00 0.1% nscd/21
590 root 2344K 1176K sleep 59 0 1:33:39 0.0% rpcbind/1
8178 root 25M 6592K sleep 59 0 4:37:54 0.0% discusge/1
15798 oracle 2166M 1578M sleep 59 0 0:00:11 0.0% oracle/1
15552 oracle 45M 17M sleep 59 0 0:04:22 0.0% httpd/5
15468 oracle 45M 17M sleep 59 0 0:04:28 0.0% httpd/5
11313 root 4568K 2872K sleep 59 0 0:00:01 0.0% sshd/1
17155 oracle 2141M 1557M sleep 59 0 5:13:08 0.0% oracle/258
143 root 4048K 2608K sleep 59 0 0:08:03 0.0% picld/6
8161 root 246M 37M sleep 59 0 0:11:35 0.0% java/29
15557 oracle 45M 17M sleep 59 0 0:04:23 0.0% httpd/5
17136 oracle 2134M 1555M sleep 59 0 0:03:07 0.0% oracle/1
16135 oracle 1096K 888K sleep 53 2 0:00:00 0.0% sh/1
16939 oracle 111M 21M sleep 59 0 1:05:16 0.0% java/19
16906 oracle 17M 3688K sleep 59 0 2:39:17 0.0% opmn/19
27976 oracle 2174M 1588M sleep 59 0 0:02:15 0.0% oracle/11
1 root 1288K 624K sleep 59 0 0:48:35 0.0% init/1
7586 oracle 6688K 2840K sleep 59 0 0:59:40 0.0% perl/1
21752 oracle 2176M 1591M sleep 59 0 0:03:52 0.0% oracle/11
NPROC USERNAME SIZE RSS MEMORY TIME CPU
101 oracle 107G 77G 100% 39:30:23 45%
56 root 768M 150M 0.2% 78:36:54 0.8%
2 nettrap0 6736K 6080K 0.0% 0:00:05 0.2%
3 hpqw 19M 11M 0.0% 0:00:00 0.0%
1 par123 336K 8K 0.0% 0:00:00 0.0%
2 kdps 3000K 2232K 0.0% 0:01:47 0.0%
1 daemon 3200K 1440K 0.0% 0:00:28 0.0%
SID SERIAL# PROCESS PROGRAM STATUS SPID SQL_HASH_VALUE LAST_CALL_ET
---------- ---------- ------------ ------------------------------------------------ -------- ------------ -------------- ------------
305 18474 15550 httpd@poswart1 (TNS V1-V3) INACTIVE 24013 0 6
SID SERIAL# PROCESS PROGRAM STATUS SPID SQL_HASH_VALUE LAST_CALL_ET
---------- ---------- ------------ ------------------------------------------------ -------- ------------ -------------- ------------
189 18916 15471 httpd@dys339d001 (TNS V1-V3) INACTIVE 13260 0 11
SID SERIAL# PROCESS PROGRAM STATUS SPID SQL_HASH_VALUE LAST_CALL_ET
---------- ---------- ------------ ------------------------------------------------ -------- ------------ -------------- ------------
267 59933 15549 httpd@dys339d001 (TNS V1-V3) INACTIVE 24399 0 9 |
|
|
|
|
|
|
|
| Re: High CPU for inactive session [message #571966 is a reply to message #571965] |
Tue, 04 December 2012 23:39  |
 |
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
|
Senior Member |
|
|
>Could any one help me...I want to run a job on oracle db's which kills all inactive jobs and mails the report to respective recipients....
most sessions are INACTIVE most of the time.
blindly terminating INACTIVE sessions is a great way to ABORT the whole database!
post SQL & results that show candidate sessions.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
