| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: Oracle sessions and OS processes
Linda,
v$session_longops is known to be buggy even though Oracle hasn't acknowledged it.
The reason why your runaway process can have a longer accumulated time than smon/pmon may be that the accumulated time is not the elapsed time; instead it's process execution time. Even if SMON or any other background process has a status ACTIVE in v$session, they still don't have execution time equal to elapsed time at the OS level. A major portion of their "active" activity is simply sleep. But your runaway process may be doing a lot of active work consuming CPU. Again, I suggest you kill (or kill -9) the process on command line.
Please correct me if there's any error.
Yong Huang
yong321_at_yahoo.com
you wrote:
Yong,
In fact the join on serial# was provided by Oracle Technical support.
Attached the file for reference. I am going to open another tar and
request Oracle Co. to clear this misleading.
The OS process number generated by your join makes more sense for me. Sep 1 is the database started time which also supposed to be the application started time. Then, the accumulated time is even larger than the smon/pmon time. It is continuously growing. It is scaring me.
SQL> select spid, sid, a.serial#, b.username
2 from v$session a, v$process b
where a.serial#=9 and a.paddr=b.addr; 3
SPID SID SERIAL# USERNAME --------- ---------- ---------- --------------- 1343 172 9 oracle
$ ps -ef|grep 1343
oracle 1343 1 12 Sep 01 ? 28233:41 oracleDEEP (LOCAL=NO)
 |
 |