All Oracle Error Codes
Oracle DBA Forum

Frequent Oracle Errors

TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated

RE: ora-01031

Bobak, Mark


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
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."

-----Original Message-----
From: oracle-l-bounce@(protected)
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 *
(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

Next, I connected again. This time, the database allowed me to shutdown

My doubt is: why I got ORA-1031errors, even though I tried to shutdown
as oracle user with group dba.

Thanks, Pedro.