|
-
I just saw a thread with this subject (initiated today by s_radhak), but the thread was allready closed !?! Btw, who decides when to close a particular thread? The original poster? The moderators?
Anyway, s_radhak wanted to know how to determine which background process is running in which session and I have a feeling he haven't got the answer yet. So here it is. There is a dynamic performance view called V$BGPROCESS which lists all the possible background proceses, both those that are actualy started and also those that arent (but are available). If you join this view to V$SESSION by process address you'll get all the background proceses listed with current sessions.
SELECT s.sid, s.username, s.process, s.program, b.description background
FROM v$session s, v$bgprocess b
WHERE s.paddr = b.paddr(+);
HTH,
Jurij Modic
ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
-
I think it was the owner who had closed the thread. Though the moderators has the right to close the threads, I have noticed in the past except "Uday" no one had ever bothered to close threads. The moderator "Uday" too had closed it only after posting some comment on the thread!
So In this case, I think it was the owner and not the moderator who had closed the thread.
Sam
Thanx
Sam
Life is a journey, not a destination!
-
Link
Hi Jmodic, 5th May 2001 19:27 hrs chennai
Good Stuff for the day.
like lsnrctl.exe and imp.exe if are all counted as job queues are they all counted as process and the counts in to the limit of init.ora parameter process ...?
Cheers
Padmam
Attitude:Attack every problem with enthusiasam ...as if your survival depends upon it
-
Padmam,
Lsnrctl and also listener itself do not have any database process associated with them. They are both external programs that do not interfere with the database. Well, listener does connect user sessions with database, but it runs entirely outside the database. Lsnrctl is only control program for listener, it does not interfere with the database at all.
On the other hand, imp.exe and exp.exe are normal database clients, just like SQL*Plus or any other tool. They connect to the database as a normal user processes and of course count toward the upper process limit in init.ora.
Jurij Modic
ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
-
But Counted
Dear Jmodic, 9th May 2001 18:33 hrs chennai
your explanation is pretty Good but look at this link and the investiagtion i have posted.
I found that after investigation that lsnrctl shows as a process that why i had doubt can you kindly check it up on this
http://www.dbasupport.com/forums/sho...threadid=10261
The process 7,8,9,10.
Cheers
Padmam
Attitude:Attack every problem with enthusiasam ...as if your survival depends upon it
-
Padmam,
Check your init.ora, I bet you have the following parameter set in there: JOB_QUEUE_PROCESSES=4.
I'm 99% sure your processes 7 to 10 belongs to job queue processes. You could have found the answer by yourself if you have run the query I've provided in this thread:
SELECT s.sid, s.username, s.process, s.program, b.description background
FROM v$session s, v$bgprocess b
WHERE s.paddr = b.paddr(+);
Run it and see what is reported in the last column for those four processes.
HTH,
Jurij Modic
ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
-
Hi Jmodic,
Thanks for the reply. I closed the thread since I found the info I needed from V$BGPROCESS.
Thank you.
-
Thanks jmodic
hi , 10th May 2001 16:41 hrs chennai
Thanks Jmodic
Cheers
Padmam
Attitude:Attack every problem with enthusiasam ...as if your survival depends upon it
-
Wrong posting !!! :(
Sam
[Edited by sambavan on 05-11-2001 at 12:39 PM]
Thanx
Sam
Life is a journey, not a destination!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|