Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 

 

Connect to Idle Instance Tips

Oracle Database Tips by Donald Burleson


Question:  We encounter the below problem yesterday morning:

(1) All running batch application hang running half-way

(2) Attempt to login via sqlplus giving below error:
 

ERROR:

ORA-00020: maximum number of processes (%s) exceeded

REMARK:
current parameter value for PROCESSES = 300

(3) Attempt to connect as sys to shutdown the database giving the below:

Connected to an idle instance.

At this point, we check that all background processes like pmon, smon, etc still exists.

(4) the instance later being terminated by LGWR, & we manage to startup (without need to shut it down)

**********************************************************

Referring to item (3), is anyone out there able to provide me a PRECISE explanation for what does it mean here "connected to an idle instance" in such a scenario?

Answer by Mark:

"Connected to an idle instance" usually means that you connected "AS SYSDBA" and the instance you connected to is not started.

However, if your instance is out of processes, then a non-SYSDBA connection will error out with ORA-0020, and a SYSDBA connection will error out with "Connected to idle instance." It's a little misleading, but that's what happens.

Usually, when this happens, I want to get connected to the instance, so that I can try to figure out which user is causing the problem. One way to do that is to use the 'ps' command to identify some of the oldest server processes, and kill the 3-5 oldest processes, and then quickly try connecting to the database. Once you're in, you can look at things like V$SESSION to try and determine which user(s) is (are) consuming so many connections, and then go from there.
 


 

 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2020

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.