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: Backup Controlfile and ArchiveLog -- was re Urgent ORA-00600: internal error code

Mark W. Farnham



In all cases, ensure that you HAVE CORRECTLY CREATED THE CONTROLFILEs,
naming every DataFile -- once you OPEN, Oracle does a Data
Dictionary check and any
datafile in the Data Dictionary but not in your Controlfile becomes
a  "MISSING" datafile !
{so sometimes we do another backup, if we can, before the OPEN RESETLOGS !}


Regarding the extra backup: This is also why, whichever side you are on in
the quasi-religious argument about whether online redo logs should be backed
up, the first step of recovery is to secure a copy of the quiescent images
of the online redo logs (most safely apart from your backup media and most
conveniently online) since they contain data that is permanently lost upon
the execution of the open resetlogs command. Whether you (unlikely) crash
restarting or experience PEBKAC during the recovery, having a copy of the
logs as they exist before the restart gives you at least a chance to try



PS: PEBKAC, first heard by me from Mike Brown, Problem Exists Between
Keyboard and Chair. Similar meaning to CFT (controlled flight into terrain)
with fewer tragic overtones.