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: RMAN backup of archived log fails

Jared Still


On 6/6/07, Tony van Lingen <tony.vanlingen@epa.qld.gov.au> wrote:

I checked the catalog with the command you listed: unless the bplist
output is limited to a number of lines (I can't get a definitive answer
to that from our NB guys), we're basically stuffed.

I don't believe so. The bplist output can be quite long.

It seems that the NB
catalog is spread over a number of servers, so if RMAN queries one it
will not get the entire list of available files.

That seems... suboptimal.

Sigh.... where have the days of tar and 'alter tablespace backup'
gone... things were so easy then....

Feeling your pain.  When doing tests that require restoring the
database I have taken to making a cold backup on disk for simplicity
and expeditiousness. (is that really a word :)

RMAN is very robust, extremely powerful and highly configurable.

That's another way of saying it can be very complicated and provide
many ways to shoot one's self in the foot. ;)

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist