Printable View
HI,
Constantly I see many unknown sessions on my DBA studio which do not have a username,osuser,machine name and programs associated with them.
But they do have a session Id, Status and os process Id fields populated and the status is always active.
What are these sessions. I have killed them in the past without any issues but they keep popping up.
ANy Ideas what these are.
Thanks
Ron
Weird, does the application server have any upload/download processes that run on the fly? I have something similar but it does not show as "unknown". Could be a front end process?
MH
If you know the client pid, why not just go to that machine and look it up?
Could it be that you are looking at instance background processes (SMON, PMON, DBWR, LGWR, ....)? They perfectly match your description...
QUOTE]Originally posted by jmodic
Could it be that you are looking at instance background processes (SMON, PMON, DBWR, LGWR, ....)? They perfectly match your description... [/QUOTE]
Not in version 9.2, they are clearly identified as
OSUSER= Oracle
STATUS = Active
PROGRAM = Oracle@box_name(CHKPT, DBWO, PMON....Ect...)
Is this dependant on configuration?
Even my 8.1.6 box identifies it as an Oracle process.
MH
This is the output of the query on v$session.
Please note sid 29,36 and 42 have no info on them and are also not background processes.
1 select SID,SERIAL#,substr(USERNAME,1,10)username,COMMAND,STATUS,SERVER,substr(SCHEMANAME,1,10)SCHAMENAME,
2* SUBSTR(OSUSER,1,10)OSUSER,PROCESS,substr(MACHINE,1,20),TERMINAL,SUBSTR(program,1,20)PROGRAM from v$session
SID SERIAL# USERNAME COMMAND STATUS SERVER SCHAMENAME OSUSER PROCESS SUBSTR(MACHINE,1,20) TERMINAL PROGRAM
--------------- --------------- ---------- --------------- -------- --------- ---------- ---------- --------- -------------------- ---------------- --------------------
1 1 0 ACTIVE DEDICATED SYS shirley 1876 THELMA THELMA ORACLE.EXE
2 1 0 ACTIVE DEDICATED SYS shirley 1448 THELMA THELMA ORACLE.EXE
3 1 0 ACTIVE DEDICATED SYS shirley 1504 THELMA THELMA ORACLE.EXE
4 1 0 ACTIVE DEDICATED SYS shirley 1468 THELMA THELMA ORACLE.EXE
5 1 0 ACTIVE DEDICATED SYS shirley 1484 THELMA THELMA ORACLE.EXE
6 1 0 ACTIVE DEDICATED SYS shirley 1916 THELMA THELMA ORACLE.EXE
11 15824 0 ACTIVE DEDICATED SYS
12 1 0 ACTIVE DEDICATED SYS shirley 1380 THELMA THELMA ORACLE.EXE
13 3 CTXSYS 0 ACTIVE DEDICATED CTXSYS shirley 1512:2092 HEROLD\THELMA THELMA ctxsrv.exe
19 2766 SYS 3 ACTIVE DEDICATED SYS aminocha 2340:2108 HEROLD\AMINOCHA-DT AMINOCHA-DT SQLPLUSW.EXE
21 23681 0 ACTIVE DEDICATED SYS
22 5397 HFOD 0 KILLED PSEUDO HFOD shirley 1516:1220 HEROLD\THELMA THELMA sqlplus.exe
25 1408 SYS 0 INACTIVE DEDICATED AMINOCHA aminocha 2244:2260 HEROLD\AMINOCHA-DT AMINOCHA-DT jrew.exe
27 27548 0 ACTIVE DEDICATED SYS shirley 2348 THELMA THELMA ORACLE.EXE
29 33277 0 ACTIVE DEDICATED SYS
36 7755 0 ACTIVE DEDICATED SYS
37 529 COMPANY 0 INACTIVE DEDICATED COMPANY aminocha 1716:2180 HEROLD\AMINOCHA-DT AMINOCHA-DT SQLPLUSW.EXE
42 2677 0 ACTIVE DEDICATED SYS
18 rows selected.
Those are probably Oracle's SNP job queue background processes. You can verify this by querying V$BGPROCESS, using SADDR of those "strange" sessions from V$SESSION as ADDR for V$BGPROCESS.