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

ORA-06508 and the Shared Pool sizing

Robyn

2005-06-29

Hello everyone,

We've run into a new issue and I'm curious as to how 'normal' this might be.  We have a new/upgraded application in test. User testing was scheduled to start yesterday but one trigger was failing.  This trigger calls a procedure owned by another user and had worked in the past.  It is an 'after update' trigger and the procedure populates a status table,  but resulted in ORA-06508: PL/SQL: could not find program unit being called.

The developers worked through all the stuff they knew to check (permissions, full identificiation of the objects, etc) to no avail.  The procedure and trigger appeared to be valid, but compiling the trigger caused the procedure to go invalid.  Procedure could be recompiled but the trigger still didn't work.

I searched at Metalink and found several documents referrencing this error for various Oracle applications, while the docs specific to the database all mentioned the same stuff that had already been tried.

The Oracle applications docs stated that the shared pool was too small and needed to be increased.  Seemed odd to me since the error mentioned not finding a program unit, but these were the only docs that referenced receiving just this error.  In every other case, there was a related error message was mentioned.

So, I shutdown the database, increase the shared pool by 128M (or 33%) and the procedure worked.  However a later attempt to recompile again broke the procedure.  This time the database was restarted without an increase in the shared pool and again, the procedure worked.

We're going to test a few things later when the users get off the system, but this seems really odd.  The database is on HP-UX not WinDoze, so I should not have to play the restart game to fix a problem.  Has anyone seem a similar problem?  I am planning to open a TAR if it repeats but I can't test again until tonight.

TIA ... Robyn