Home
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: Checking if remote database is up

stephen booth

2005-04-26

Replies:
On 4/26/05, Gene Sais <Gsais@(protected):
> I prefer to do the check outside the db from a ksh script. It's not goin=
g to help when the db doing the check is down :).

If the local DB is down then the app can't run anyway so this isn't a
problem. Most of the transactions only use the local database. We
need a check that can be done before the transactions that need the
remote database to make sure it's available and return an appropriate
value. From what the consultants who are implementing the app are
telling me it can be ammended to run an extra function and then do or
not do a transaction based on that result. What it can't handle is a
transaction failing, it can't trap and handle exceptions.

Stephen

--=20
It's better to ask a silly question than to make a silly assumption.
--
http://www.freelists.org/webpage/oracle-l