Links
Home
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
4031 - errors

4031 - errors

2004-06-02       - By Jared.Still@(protected)

Reply:     <<     21     22     23     24     25     26     27     28     29     30     >>  

oracle-l-bounce@(protected) wrote on 06/02/2004 02:03:38 PM:

> OK - here are some things that contributed to my problems and woes:
>
> 3) The other choke, gasp, dba had alot of dbms_outputs in procedure,
> functions except that he moved into production instead of commenting
them
> out.

Commenting them out is bad form for production code. A switch that can
be set at runtime to enable/disable the debug code is quite a bit better.

The default of course should be false.

Jared


> one procedure that called another function which called another
> function, had more than 20 of these things. And yes same person who is
> updating
> across the links.....
>

Many functions is better than 1 big one. You just need to implement
a trace mechanism to trace the call stack when the, *ahem*, debug
flag is set.

Jared


<br > <font size=2 > <tt >oracle-l-bounce@(protected) wrote on 06/02/2004
02:03:38 PM: <br >
<br >
> OK - here are some things that contributed to my problems and woes: <br >
> <br >
> 3)  The other choke, gasp, dba had alot of dbms_outputs in procedure, <br >
> functions except that he moved into production instead of commenting
them <br >
> out. <br >
</tt > </font >
<br > <font size=2 > <tt >Commenting them out is bad form for production code.
 A switch that can </tt > </font >
<br > <font size=2 > <tt >be set at runtime to enable/disable the debug code
is quite a bit better. </tt > </font >
<br >
<br > <font size=2 > <tt >The default of course should be false. </tt > </font >
<br >
<br > <font size=2 > <tt >Jared </tt > </font >
<br >
<br >
<br > <font size=2 > <tt >>      one procedure that called
another function which called another <br >
> function, had more than 20 of these things.  And yes same person
who is <br >
> updating <br >
>      across the links..... <br >
> <br >
</tt > </font >
<br > <font size=2 > <tt >Many functions is better than 1 big one.  You
just need to implement </tt > </font >
<br > <font size=2 > <tt >a trace mechanism to trace the call stack when the,
*ahem*, debug </tt > </font >
<br > <font size=2 > <tt >flag is set. </tt > </font >
<br >
<br > <font size=2 > <tt >Jared </tt > </font >
<br >