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: 10.1.0.4 patchset 2 catcpu.sql slop

rjamya

2005-06-29

Replies:
That's not the point, Oracle states in Metalink note 3663846.8 proclaiming that it is fixed in 10.1.0.4 and is isn't. This works in 9ir2 but broke sometime in 10g. Can you spell regression?

Raj

On 6/29/05, Mladen Gogala <mgogala@allegientsystems.com> wrote:
rjamya wrote:

> One thing we found on 10.1.0.4 <http://10.1.0.4> is large pl/sql
> blocks don't compile. They fail with pls-123 Program too large error.
> I am currently working on creating a test case for Support, since the
> bug was closed as fixed in 10.1.0.4 <http://10.1.0.4>. Ha !!
>
> Raj
>
One way of fixing this would be to make a recommendation not to use
large PL/SQL blocks.
That wouldn't be the first time that the problem is solved on the
marketing level.

--
Mladen Gogala
Oracle DBA
Ext. 121





--
------------------------------
select standard_disclaimer from company_requirements where category = 'MANDATORY';