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: CATPROC gets invalidated



DBMS_DDL & STANDARD are special as well; see:

-----Original Message-----
From: oracle-l-bounce@(protected)]
On Behalf Of Alex Gorbachev
Sent: Monday, May 15, 2006 12:34 PM
Subject: Re: CATPROC gets invalidated

If it's of any concern to someone - we have hit the bug of upgrade
(not downgrade as Oracle support insists). The problem has something
to do with synonym for DBMS_STANDARD. Apparently it's not "normal"
synonym in a way that practically anything depends on it and it's
implemented somehow differently as I've been told. During the upgrade
procedure something goes wrong with this synonym and it results in
exact behavior we were facing.
Workaround - flushing shared pool (I wasn't able to verify it). We
used our workaround - compile DBMS_STANDARD package and package body
and than running utlrp.sql. Apparently, support says that it's not
that easy to compile dbms_standard and what we've done doesn't really
compile it - they claim that it's only possible to compile
dbms_standard in migrate/restrict mode.
Anyway, I don't think that 100% of above is exactly true but I was
given that info. Bug numbers are 4710649 and 4882839 fixed in 11.0.

Thanks to all replied.

2006/5/15, Alex Gorbachev <gorbyx@(protected)>:
> Hi all,
> This is very weird... Third time in the last few days catproc got
> invalidated. This is on database on AIX that was upgraded to
> and than downgraded back to (almost a month ago).
> it's a DW environment.
> Last occurrence's description:
> The issue appears in different forms one of which is trying to run
> ORA-04068: existing state of packages has been discarded
> ORA-04065: not executed, altered or dropped stored procedure
> ORA-06508: PL/SQL: could not find program unit being called
> ORA-06512: at "SYS.DBMS_STATS", line 12210
> ORA-06512: at line 2

Best regards,
Alex Gorbachev