Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: 4031 - errors

RE: 4031 - errors

From: Duret, Kathy <>
Date: Wed, 2 Jun 2004 16:39:43 -0500
Message-ID: <>

the trouble with the switch here it that the developers forget to switch it off.  

I totally agree with the many functions, procedure rule. I tried today to get them to break it up, but getting the developer and the other choke dba to change their code is harder than
carving another face on mount Rushmore.  

BTW loved your comment Johnathan... yet another top has coffee stains all over it. I have to remember to put down my drink before I read these emails.  


-----Original Message-----
From: [] Sent: Wednesday, June 02, 2004 4:32 PM
Subject: RE: 4031 - errors 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.


> 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.


This transmission contains information solely for intended recipient and may be privileged, confidential and/or otherwise protect from disclosure. If you are not the intended recipient, please contact the sender and delete all copies of this transmission. This message and/or the materials contained herein are not an offer to sell, or a solicitation of an offer to buy, any securities or other instruments. The information has been obtained or derived from sources believed by us to be reliable, but we do not represent that it is accurate or complete. Any opinions or estimates contained in this information constitute our judgment as of this date and are subject to change without notice. Any information you share with us will be used in the operation of our business, and we do not request and do not want any material, nonpublic information. Absent an express prior written agreement, we are not agreeing to treat any information confidentially and will use any and all information and reserve the right to publish or disclose any information you share with us.

Please see the official ORACLE-L FAQ:

To unsubscribe send email to: put 'unsubscribe' in the subject line.
Archives are at
FAQ is at
Received on Wed Jun 02 2004 - 16:36:36 CDT

Original text of this message