Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: 9i : ORA-00020: maximum number of processes (%s) exceeded
Well, I set up processes = 12 just to do my testing. The regular value is
150 (I think it is default). I don't want to open 140 or so sessions for my
testing.
We occuasionally had some adhoc scripts running against 8i db that locked certain table and the other sessions would start to pile up after that. I had to bounce the db. I am wondering if thers is some other way to log into db in 9i without doing the session killing. I guess this might be one reason that we would stay in 8i for a while.
Guang
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of
Reginald.W.Bailey_at_jpmorgan.com
Sent: Wednesday, February 25, 2004 4:21 PM
To: oracle-l_at_freelists.org
Subject: Re: 9i : ORA-00020: maximum number of processes (%s) exceeded
Why would you set processes = 12? Are you trying to OFF you databse? Was this some kind of a bad experiment? What worked for 8i doesn't necessarily work for 9i. Use the kill command and just kill the SQL*Plus sessions, log in as SYSDBA and shutdown the DB, and call it a day. Or use "kill" to kill the database. Dealer's choice.
Reginald W. Bailey
IBM Global Services
JPMC Account - DCI ETS Database Management
Your Friendly Neighborhood DBA
713-216-7703 (Office) 281-798-5474 (Mobile)
reginald.w.bailey_at_jpmorgan.com
baileyre_at_us.ibm.com
gmei_at_incyte.com Sent by: To: oracle-l_at_freelists.org oracle-l-bounce_at_fre cc: elists.org Subject: 9i : ORA-00020:maximum number of processes (%s) exceeded
02/25/2004 03:03 PM Please respond to oracle-l
Hi:
In 8i, when I got the above error, I always could launch svrmgrl, connected as intenal and bounce the DB. Now in 9i without svrmgrl, how do we bounce the db if we have the above error?
I did the following test on a 9204 db on Solaris 9:
oracle 9209 1 0 13:59:20 ? 0:00 ora_pmon_YPD oracle 9217 1 0 13:59:21 ? 0:01 ora_smon_YPD oracle 9211 1 0 13:59:20 ? 0:00 ora_dbw0_YPD oracle 14801 14800 0 15:44:56 pts/3 0:00 ps -ef oracle 9223 1 0 13:59:21 ? 0:01 ora_qmn0_YPD oracle 14800 14787 0 15:44:56 pts/3 0:00 grep oracle oracle 9215 1 0 13:59:21 ? 0:02 ora_ckpt_YPD oracle 9219 1 0 13:59:21 ? 0:00 ora_reco_YPD oracle 9213 1 0 13:59:21 ? 0:02 ora_lgwr_YPD oracle 9221 1 0 13:59:21 ? 0:00 ora_cjq0_YPD
2. I opened two seperated sql sessions, connected as regular user. No problem. So I left them idle.
3. When I tried the 3rd session, I got
essex$ sqlplus user/password
SQL*Plus: Release 9.2.0.4.0 - Production on Wed Feb 25 15:46:31 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
ERROR:
ORA-00020: maximum number of processes (%s) exceeded
Enter user-name:
ERROR:
ORA-01017: invalid username/password; logon denied
Enter user-name:
ERROR:
ORA-01017: invalid username/password; logon denied
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus essex$ sqlplus '/ as sysdba'
SQL*Plus: Release 9.2.0.4.0 - Production on Wed Feb 25 15:46:57 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected.
SQL> shutdown immediate
ORA-24324: service handle not initialized ORA-24323: value not allowed ORA-00020: maximum number of processes (%s) exceeded
I can not shut down the DB. The other two sessions are still working as normal. I don't want to do "kill -9" to another sqlplus connection if I don't have to. Do I have another choice if I want to bounce the db?
TIA. Guang
![]() |
![]() |