This means that you have too many database connections basically. Unfortunately since the demise of svrctl, it also means that you as a DBA cannot connect internal to do something about it!
You need to either ask a couple of users to log out, or you need to kill some sessions at the OS level. Once you managed to connect, see if you can spot anyone making abnormal numbers of connections. If you can't find anything you will need to increase the init parameter 'processes'. Unfortunately, this will require a restart of the database to take effect:
Note. When connecting via TNS, you may get this error
when the database is out of processes:
You need to either ask a couple of users to log out, or you need to kill some sessions at the OS level. Once you managed to connect, see if you can spot anyone making abnormal numbers of connections. If you can't find anything you will need to increase the init parameter 'processes'. Unfortunately, this will require a restart of the database to take effect:
**********------------------------------------ **********
**********------------------------------------ **********If you are using spfile: -
SQL> show parameter spfile;
SQL> show parameter processes NAME TYPE VALUE ------------------------------------ ----------- ------- processes integer 150 SQL> select count(*) from v$process; COUNT(*) ---------- 149 SQL> alter system set processes=300 scope=spfile; System altered. SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. SQL> show parameter processes NAME TYPE VALUE ------------------------------------ ----------- ---------
processes integer 300
**********------------------------------------ **********
**********------------------------------------ **********
If you use pfile then create spfile from pfile; Shutdown db then startup then run SQL> alter system set PROCESSES= xx scope = spfile; **********------------------------------------ **********
**********------------------------------------ ********** If you want to use pfile instead of spfile,than go to $ORACLE_HOME/dbs/ cp initSID.ora initSID.ora_org
Now Edit initSID.ora file
vi initSID.ora Enter "i" (Without Quotes)
PROCESSES=XX SESSIONS 2*XX
Press ESC
Then Type ":w" (Without Quotes to save Value in initSID.ora file)
Then ":q!" (Without Quotes to exit from initSID.ora)
You may need to reboot db after change this parameter
SHUTDOWN DB
Start DBNote. The maximum allowed processes is one less than the init parameter 'processes'
Note. When connecting via TNS, you may get this error
when the database is out of processes:
ORA-12516: TNS:listener could not find available handler with matching protocol stack
=========
Frist decide your system open wiht spfile or init file. You can understand it by using below query show parameter spfile; If you use spfile then issue: alter system set PROCESSES= xx scope = spfile; If you use pfile than create spfile from pfile; Shutdown db then startup then run alter system set PROCESSES= xx scope = spfile; If you want to use pfile instead of spfile,than go to $ORACLE_HOME/dbs/ cp initSID.ora initSID.ora_org vi initSID.ora PROCESSES=xxx
You may need to reboot db after change this parameter
=============================
Sukhwinder Singh
Apps DBA
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.