Links
Home
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
smon 4030 - quick ideas?

smon 4030 - quick ideas?

2006-06-02       - By Kevin Closson

Reply:     1     2     3     4     5     6     7     8     9     10     >>  

>>>
>>>ORA-04030 (See ORA-04030.ora-code.com) means that the Oracle process attempted to
>>>allocate more memory for heap, similar to using the C
>>>"malloc()" function, so process limits could be very relevant...


Right, Tim, but since I didn't see what platform it is
or any other detail, I'd like to remind people that
malloc() (actually the brk() system call) also fails
if the heap whacks the attach address of the SGA. If
there has been any of that funky SGA relocation down
to addresses just north of the initialized data you'll
get this too. So, questions:

1. Did the .trc file show a system call failure? It should
  because 4030 is the result of an OSD failure.

2. Any "Relocating the SGA" madness going on ?

--
http://www.freelists.org/webpage/oracle-l