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: database duplication

Dennis Williams



I have seen character set errors quite a bit in RMAN recoveries. If
you are using OEM, it may be that the character set on your PC differs
from the character set on the server. If not, examine the character
set of each of the databases involved.
  I have also ended up completing the recovery of a database without
using RMAN more than once. It probably means that somehow the archive
logs were not available to RMAN at the point it tried to perform the
recovery. You may be able to complete the recovery by putting the
archive logs where they are expected by the new database and issuing a
recover database from sqlplus.
  Database duplication with RMAN works really slick, but there are
some details that are difficult to work out. Once you get it going in
your environment, take careful notes and you should have no difficulty
the next time.

Dennis Williams