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-4031

Tanel Poder


Are those ORA-4031's accompanied with "large pool" or "shared pool" parameter in alert log?
If large pool, set the large_pool_size to higher value, despite the autotuning feature.
If shared pool, then please run this as SYS. In 10gR1 it should show you into how many shared subpools your SP has been divided to.
select count(*) from x$kghlu where kghlushrpool = 1;
If it's more than 1 then you might be hitting a bug/issue with shared subpools and it would be advisable to set _kghdsidx_count=1 and bounce the instance. That seems to be Oracle support's latest standard advice whenever having shared pool related issues...
(btw, in 10gR2 the x$kghlu shows 4X more entries as shared pool has been split up even further - protected by the same amount of latches though..)
----- Original Message -----
From: Tracy Rahmlow
To: oracle-l@freelists.org
Sent: Tuesday, May 09, 2006 2:28 AM
Subject: ORA-4031

This weekend we upgraded from 32-bit to 64-bit (AIX 5.2) and we are experiencing a large number of 4031 errors(these were extremely rare under 8).  We have contacted Oracle support as a sev 1 issue, but I thought I would drop a note to see if anyone has experienced anything like this while we wait.  Under 8 our shared pool was approximately 250m.  We initially set the shared pool to 1.2g under 10 and that was not enough.  In the interim, we decided to increase the shared pool to 3g to see if we can buy some time while we continue to wait (and that has been successful so far).  We do have some literal sql and some opportunities for improvement, but I would think we should experience "somewhat" similar behavior in terms of memory usage with the upgrade vs. the prior version.  The amount of memory seems very excessive to me.  In addition, we are not using the memory autotuning featur e.  Anybody know of a bug related to excessive shared pool usage or any other thoughts?  Thanks


Tracy Rahmlow | Lead Database Analyst
Information Systems
Ameriprise Auto & Home Insurance

AMEX Assurance Company
IDS Property Casualty Insurance Company
3500 Packerland Drive | De Pere, WI 54115-9070
Office: 920.330.5164 | Fax: 920.330.5350

Ameriprise made the following
annotations on 05/08/06, 11:29:55

"This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you."