Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: ora-01031

RE: ora-01031

From: Bobak, Mark <>
Date: Wed, 30 May 2007 16:11:14 -0400
Message-ID: <>

Hi Pedro,

My guess is, when you did "connect / as sysdba", the process table was already filled, and you actually failed to connect.

Then, when you tried to shutdown abort, you got ORA-1031 cause you weren't actually connected.

It's interesting to note that if you connect as sysdba, and the connection is successful, you see something like:
"Connected to:

Oracle Database 10g Enterprise Edition Release - 64bit Production
With the Partitioning, OLAP and Data Mining options"

Of course, this will vary, based on the version of Oracle you're running.

If you fail to connect, cause process table is full, you'll get:

Which is a just a *bit* counterintuitive....but that's what happens.

So, "Connected." means you *failed* to connect!

Hope that helps,


Mark J. Bobak
Senior Oracle Architect

"There are 10 types of people in the world: Those who understand
binary, and those who don't." -----Original Message----- From: [] On Behalf Of Pedro Espinoza Sent: Wednesday, May 30, 2007 3:09 PM To: oracle-l Subject: ora-01031 One of our production users complained that he couldn't connect to the database. I looked into the listener.log and found the following. Environment: single instance on solaris sparc 64, 5.8 30-MAY-2007 14:33:31 * (CONNECT_DATA=(SID=XYZ)(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))) * (ADDRESS=(PROTOCOL=tcp)(HOST= * establish * TMAN * 12518 TNS-12518: TNS:listener could not hand off client connection TNS-12547: TNS:lost contact TNS-12560: TNS:protocol adapter error TNS-00517: Lost contact Solaris Error: 32: Broken pipe Note 340089.1 suggests to increase the processes. I, then, connected to the db using "connect '/as sydba'" XYZ>show parameter process ORA-01012: not logged on I have checked whether oracle processes exist. I did ps -aef | grep XYZ, and found that all processes were running. I exit from this session, and then connected '/as sysdba' from local box, so there is no business of orapw,e tc). When I tried to shutdown immediate, I got the following: XYZ> shutdown immediate; ORA-24324: service handle not initialized ORA-24323: value not allowed ORA-00020: maximum number of processes (%s) exceeded Then, I tried XYZ> shutdown abort; ORA-01031: insufficient privileges XYZ> exit Disconnected Next, I connected again. This time, the database allowed me to shutdown abort. My doubt is: why I got ORA-1031errors, even though I tried to shutdown as oracle user with group dba. Thanks, Pedro. -- --
Received on Wed May 30 2007 - 15:11:14 CDT

Original text of this message