If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

You should increase de PROCESSES parameters that is directly related to the maximum number of sessions you can have.

In a "normal" database configuration, each user session is "attached" to one process. So, if the PROCCESS parameter is set low you will be running out of processes and getting the error "ORA-00020: maximum number of processes exceeded".

Also, you might try to setup SHARED SERVERS that is another Oracle feature that pools several processes an share them among several (a lot) user session. So, as an example, you could have only 10 processes handling the load of 200-250 sessions. Well, this is another topic but if you're interested we can talk more about it.

But for now:
1. You should increase the PROCESSES parameter
2. Quit the SESSIONS parameter. Oracle will calc this value from the PROCESSES parameter (1.1 * PROCESSES + 5)
3. Parameters like LICENSE_MAX_SESSIONS and LICENSE_MAX_USERS should be 0 (ZERO) that means unlimited (if you have this kind of license from Oracle).

Originally posted by pgamez I think changing the SESSIONS parameters is not the right way.

You should increase de PROCESSES parameters that is directly related to the maximum number of sessions you can have.

In a "normal" database configuration, each user session is "attached" to one process. So, if the PROCCESS parameter is set low you will be running out of processes and getting the error "ORA-00020: maximum number of processes exceeded".

Also, you might try to setup SHARED SERVERS that is another Oracle feature that pools several processes an share them among several (a lot) user session. So, as an example, you could have only 10 processes handling the load of 200-250 sessions. Well, this is another topic but if you're interested we can talk more about it.

But for now:
1. You should increase the PROCESSES parameter
2. Quit the SESSIONS parameter. Oracle will calc this value from the PROCESSES parameter (1.1 * PROCESSES + 5)
3. Parameters like LICENSE_MAX_SESSIONS and LICENSE_MAX_USERS should be 0 (ZERO) that means unlimited (if you have this kind of license from Oracle).

Hope this can help.

Cesar Gamez

not true, a session can have more that one process.

So my sessions could be low but still requiring processes to be high.

If you get max number of sessions exceeded you need to increase sessions not processes!

Read Manuals ???

Hello davey,

What do you mean read the manuals ?

I increased the PROCESSES parameter in init.ora file as suggested and I still get the same problem with my Reports Services after Restarting my Database.

From the previous Posts, it looks to me as if only 9% of processes are used, this does not explain the reason I am gettings this error message, also, I set the PROCESSES value to 9999 and the query output indicates only 150 total processes.

Re: Read Manuals ???

I increased the PROCESSES parameter in init.ora file as suggested and I still get the same problem with my Reports Services after Restarting my Database.

From the previous Posts, it looks to me as if only 9% of processes are used, this does not explain the reason I am gettings this error message, also, I set the PROCESSES value to 9999 and the query output indicates only 150 total processes.

PT

PS: Maybe this error message is not the cause but a side effect ???

quite frankly, i forgot what you rproblem even is - i dont even care anymore.