Don't know about semaphore specifics, but yes, Oracle uses threads on NT /
2000 / XP in a way similar to its use of threads in Unix / Linux, and I
*believe* that the PROCESSES parameter will limit the number of those
threads. To test this, you could set a low value for PROCESSES on a
dedicated-server Windows box and then try to max out the threads by opening
connections. You could also use a tool such as pviewer, perfmon, or even
the Task Manager to monitor how many threads are in use by the Oracle
process. I'd do this myself but I don't have a "Winoracle" box available -
I've got plenty of Oracle boxes, and plenty of Windows boxes, but not any
running both. Let me know if you are able to verify this.
--
Cheers,
Chris
___________________________________
Chris Leonard, The Database Guy
http://www.databaseguy.com
Brainbench MVP for Oracle Admin
http://www.brainbench.com
MCSE, MCDBA, OCP, CIW
___________________________________
<si004_at_hotmail.com> wrote in message
news:e9f7d2f5.0305010646.60f4c5e7_at_posting.google.com...
> Hi All,
>
> What is the exact meaning of the PROCESSES pfile parameter under the
> NT architecture? The only Oracle documentation I have found (Database
> Reference) describes what seems to make sense under an UNIX
> architecture (ie processes not threads).
>
> I have a basic understanding of what the PROCESSES parameter means
> under the UNIX architecture. Does Oracle on NT, when configured in
> dedicated server mode (ie not MTS), acquire semaphore sets for
> background threads analageous to how semaphore sets are acquired for
> background processes under UNIX?
>
> Cheers
>
> Simon Inglis.
Received on Thu May 01 2003 - 13:55:55 CDT
