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


On 4/26/05, Niall Litchfield <niall.litchfield@(protected):
> Would a quick hack to code the procedure as a version of
> declare
>   l_alive number;
> begin
>    select 1 into l_alive from dual@(protected);
>         if l_alive =3D 1 then
>   proc_name;
> end if
> end;
> /
> make sense?
> This might avoid ocella upgrades breaking your check, or dealing with
> the politics :).

Yes, that looks like it will do the job nicely.

> Alternatively you might wish to add error handling for what ever
> errors you get when the ocella db is down and add that to your
> functions and procedures...

Unfortunately the app just fires dynamic SQL directly at the database,
no functions or procedures involved. I'm told by the consultants that
they can add some code to call a function and check the result. I
suspect packaging that block up in a function that returns TRUE if it
works and adding an exception handler for the ORA-03113 error which
returns FALSE would do quite nicely.



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