Home
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: Oracle 10 on linux

Jared Still

2006-07-11

Replies:
On 7/11/06, John Dunn <jdunn@sefas.com> wrote:
I am running Oracle 10 R2  on linux with automatic memory management and
keep getting the following error :

ORA-04031: unable to
allocate 3888 bytes of shared memory ("shared pool","unknown object","sga
heap(1,0)","kglsim object batch"

Anyone else seen this?


Yes.

Increase your shared pool size.

v$sgastat may report that there is plenty of memory, but you may still see errors.

250meg is considered by some to be the minimum allowable shared pool size on 10g.

Moving a database with minimal memory requirements to 10g (64bit) on linux required setting
the sga_target size to 400m, and the shared_pool_size to 250m.

This is a little more than double what the memory requirements were on 8i.

I have not tried to troubleshoot this down to a root cause, as it is all working at the moment.
(Yes, always other things to do)

You could also try going back to fully manual memory management.
ie. set sga_target to 0, and manually set db_cache_size, shared_pool_size...


--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist