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: gather_stats_job died due to AUTO SGA error

Don Seiler

2007-04-18

Replies:
On 4/11/07, Don Seiler <don@(protected):
> AUTO SGA: Disabling background sga tuning due to err 604
>
> Also, is the sga auto tuning still disabled? Where can one check?

After reading Jonathan Lewis' article at
http://jonathanlewis.wordpress.com/2007/04/16/sga-resizing/, I ran the
query against v$sga_resize_ops and sure enough there hasn't been any
operations since 11-APR-07 02:30:38, when this error happened.

v$sga_resize_ops also shows an INSANE amount of activity, each time
shrinking the buffer cache (db_cache_size) and growing the shared pool
(shared_pool_size).

What confuses me is that the INITIAL_SIZE and FINAL_SIZE never change
during this flurry. Here is a small sample of the output, there is
lots more just like it:

START_TIME      OPER_TYPE COMPONENT        PARAMETER
OPER_MODE INITIAL_SIZE FINAL_SIZE
------------------ ---------- --------------------
-------------------- --------- ------------ ----------
11-apr-07 02:30:29 SHRINK   DEFAULT buffer cache db_cache_size
IMMEDIATE   838860800 838860800
            GROW     shared pool       shared_pool_size
IMMEDIATE   587202560 587202560

11-apr-07 02:30:30 SHRINK   DEFAULT buffer cache db_cache_size
IMMEDIATE   838860800 838860800
            GROW     shared pool       shared_pool_size
IMMEDIATE   587202560 587202560

11-apr-07 02:30:33 SHRINK   DEFAULT buffer cache db_cache_size
IMMEDIATE   838860800 838860800
            GROW     shared pool       shared_pool_size
IMMEDIATE   587202560 587202560

I'm considering the suggestion of setting decent minimums for the pool
sizes, but I don't see how it would address this particular issue.
Perhaps it is just that bug, and perhaps ASMM isn't as fantastic as I
thought.

--
Don Seiler
oracle: http://seilerwerks.blogspot.com
ultimate: http://www.mufc.us
--
http://www.freelists.org/webpage/oracle-l