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: 30+ long db_link names and dbms_metadata.get_ddl

Dan Fink


I wrote a series of scripts that combined the 50% of DBMS_METADATA that worked with custom calls for the 50% that did not. I logged multiple TARs (even more than when I was working on 7.0.? OPS on OpenVMS), turned them into several bugs and railed against the horrible documentation. I really despise it when the conceptual documentation is written by marketing and the user documentation is written by the original programming team. No offense to programmers (I was one once...and still am to some degree), but they tend to write as if they were the audience. They are obviously very smart, but need to remember that we are all not as smart, or at least not as smart in the same areas. I did manage to find some articles on the web about DBMS_METADATA, but it was all a regurgitation of the documentation and not useful at all.

I played around with the 10gR1 version and found it was living up to it's promise. Much easier to use and you could actually extract a simple schema with one call! I have not used it in a year, so it may have changed substantially. All in all, it is a great little feature. The upside of the 9i version is that I learned a great deal about long -> clob conversion, extracting ddl using hierarchical queries to resolve most dependencies, etc.

Dan Fink

----- Original Message -----
From: Darrell Landrum
Sent: Thu May 26 09:32:50 MDT 2005
To: oracle-l@(protected)
Subject: RE: 30+ long db_link names and dbms_metadata.get_ddl

Right on about it being buggy! It is a great start to a great tool, but has
some gotchas. One example is, in my experience, dbms_metadata extracts the
ddl of a materialized view with "enable query rewrite" even if you have it
disabled on your materialized view. Not life threatening, but still
problematic until you catch on.