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
weren't actually connected.
It's interesting to note that if you connect as sysdba, and the
connection is successful, you see something like:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit
With the Partitioning, OLAP and Data Mining options"
Of course, this will vary, based on the version of Oracle you're
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."
Sent: Wednesday, May 30, 2007 3:09 PM
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: 10.2.0.2 single instance on solaris sparc 64, 5.8
30-MAY-2007 14:33:31 *
(ADDRESS=(PROTOCOL=tcp)(HOST=184.108.40.206)(PORT=56635)) * 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 processORA-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 initializedORA-24323
: value not allowedORA-00020
: maximum number of processes (%s) exceeded
Then, I tried
XYZ> shutdown abort;ORA-01031
: insufficient privileges
Next, I connected again. This time, the database allowed me to shutdown
My doubt is: why I got ORA-1031
errors, even though I tried to shutdown
as oracle user with group dba.