bash-3.2$ export ORACLE_SID=ANARDB bash-3.2$ bash-3.2$ rman Recovery Manager: Release 11.2.0.3.0 - Production on Mon Feb 10 09:00:00 2014 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. RMAN> connect target /; RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== ORA-00020: maximum number of processes (600) exceeded RMAN> RMAN> RMAN> exit Recovery Manager complete. bash-3.2$ bash-3.2$ echo $ORACLE_SID ANARDB bash-3.2$ bash-3.2$ sqll SQL*Plus: Release 11.2.0.3.0 Production on Mon Feb 10 09:01:15 2014 Copyright (c) 1982, 2011, Oracle. All rights reserved. ERROR: ORA-00020: maximum number of processes (600) exceeded Enter user-name: ERROR: ORA-01017: invalid username/password; logon denied Enter user-name: ^C bash-3.2$ bash-3.2$ bash-3.2$ sqlplus / as sysdba; SQL*Plus: Release 11.2.0.3.0 Production on Mon Feb 10 09:01:21 2014 Copyright (c) 1982, 2011, Oracle. All rights reserved. ERROR: ORA-00020: maximum number of processes (600) exceeded Enter user-name: ^C bash-3.2$ bash-3.2$ df -h Filesystem size used avail capacity Mounted on /dev/dsk/c0t0d0s0 59G 45G 13G 78% / /devices 0K 0K 0K 0% /devices ctfs 0K 0K 0K 0% /system/contract proc 0K 0K 0K 0% /proc mnttab 0K 0K 0K 0% /etc/mnttab swap 109G 1.7M 109G 1% /etc/svc/volatile objfs 0K 0K 0K 0% /system/object sharefs 0K 0K 0K 0% /etc/dfs/sharetab fd 0K 0K 0K 0% /dev/fd swap 109G 3.0M 109G 1% /tmp swap 109G 104K 109G 1% /var/run /dev/md/dsk/d10 138G 26G 110G 20% /export/home2 /dev/dsk/c0t0d0s6 90G 48G 40G 55% /export/home0 datapool 920G 877G 42G 96% /data /vol/dev/dsk/c0t4d0/sol_10_811_sparc 2.1G 2.1G 0K 100% /cdrom/sol_10_811_sparc bash-3.2$ bash-3.2$ cd /u01/app/oracle/diag/rdbms/ANARDB/ANARDB/trace/ bash-3.2$ bash-3.2$ bash-3.2$ tail -100f alert_ANARDB.log .......................... Process m002 submission failed with error = 20 Process m001 submission failed with error = 20 Mon Feb 10 08:16:46 2014 ORA-00020: maximum number of processes (600) exceeded ORA-20 errors will not be written to the alert log for the next minute. Please look at trace files to see all the ORA-20 errors. Process m002 submission failed with error = 20 Mon Feb 10 08:25:45 2014 ORA-00020: maximum number of processes (600) exceeded ORA-20 errors will not be written to the alert log for the next minute. Please look at trace files to see all the ORA-20 errors. Process m001 submission failed with error = 20 Mon Feb 10 08:26:49 2014 ORA-00020: maximum number of processes (600) exceeded ORA-20 errors will not be written to the alert log for the next minute. Please look at trace files to see all the ORA-20 errors. bash-3.2$sqlplus -prelim “/as sysdba” SQL> shutdown abort ORACLE instance shut down. SQL> startup mount ORACLE instance started. ORA-01012: not logged on Process ID: 0 Session ID: 0 Serial number: 0 It appears that the shutdown abort was successful but the mount command did not complete. Disconnect from the previously connected session and logon normally to start the instance. SQL>exit bash-3.2$sqlplus / as sysdba SQL>startup mount Now we can go ahead and increase our processes parameter. Actually I opted not to increase the parameter since I knew the root cause of the processes being exceeded. This was a Enterprise Manager Grid Control repository and due to some OMS processes had caused the database processes to be exceeded.