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

Checking if remote database is up

stephen booth


One of our new systems (Documentum from EMC) uses a database link to a
remote database (Ocella from Ocella) for some processes. Due to
organisation politics the people managing the Ocella database don't
tell the people managing Documentum when they're taking their system
down (the joys of working in the public sector). Documentum can do
most of it's functions when Ocella is down, it just can't do certain
transactions, unfortunately it's currently not very good at dealing
with situations where the Ocella database is down.

We're looking at some way of checking if the Ocella database is up
before trying a transaction that needs it then reporting back to the
user if it's down. What we're currently thinking of is putting an
empty table in the Ocella database then querying that from a PL/SQL
function over the link and trapping the error. If we get data or 'No
Rows Returned' then we know that the database is up and the link is
working. If we get an ORA-03113 then we know that the database is
down or the link isn't working for some other reason (e.g. Network
broken again). the function returns either TRUE or FALSE depending on
whether the remote dtabase is up or not.

Does anyone have experience of a similar situation? Is there a more
elegant/reliable method? Anything I've failed to consider that will
make this all blow up?



It's better to ask a silly question than to make a silly assumption.