Re: Increasing value of Max Processes

There is a little room for ambiguity here, though. There are several other parameters that are, by default, derived from the process count (e.g. sessions, as Ricky implies). If you have set all these other values manually then changing the processes parameter costs you about 700 bytes per process.

Of course, unless you are using MTS, the value for sessions (which is the single biggest hitter) is likely to be similar to the value for processes, in which case Ricky's estimate is in the right ball park.

--
Jonathan Lewis
Yet another Oracle-related web site:  http://www.jlcomp.demon.co.uk

Practical Oracle 8i:  Building Efficient Databases
Publishers:  Addison-Wesley

Reviews at: http://www.jlcomp.demon.co.uk/book_rev.html



Ricky Sanchez wrote in message <3ACF6391.C675354A_at_more.net>...


>Actually, it increases the size of the shared pool by maybe 10k or so per

>process, so you might eat up an additional meg or so. The server creates

>additional state object structures to accomodate process and session

 information.


>Increasing processes also increases the burden on lgwr and pmon, since they

 have


>to scan process and session state objects to do their work.

>

>- ricky