4031 - errors 2004-06-03 - By Mercadante, Thomas F
Kathy,
Your developers sound like they follow my favorite quote:
"Lets hurry up and do it wrong so that we can fix it right later ".
just beautiful. no time to get the answers up front, but lots of time to
teeth-nash later on to fix it.
gotta love it.
Tom Mercadante
Oracle Certified Professional
-- --Original Message-- --
From: Duret, Kathy [mailto:kduret@(protected)]
Sent: Thursday, June 03, 2004 9:54 AM
To: 'oracle-l@(protected) '
Subject: RE: 4031 - errors
Sounds like a great plan. I will check it out. I have to get rid of all
the dbms_output.enable that is hard coded all over the place and other
things before I can do this.
And I wasn 't worried about the developers... I was worried about monkey boy
.... I spend most of my week trying to fix alot of the stuff he does.
One month ago for instance, he set pctincreased and pct used to over 100 on
the tables he moved into production.....
I am trying get it so I can do a code review BEFORE things get moved into
production....but it doesn 't go to far....they consider themselves fast
paced here which translates into:
Throw stuff into production, fix the problems, redo the code, fix the
problems, redo the code, user hates it, revamp the code, more problems.....
leave the old tables, view behind and of course there are
still reports and batch jobs using the old tables that they don 't have time
to change their code to take care of.
well enough venting for today. monkey boy caused another problem that I
have to fix....
Kathy
-- --Original Message-- --
From: Jamadagni, Rajendra [mailto:Rajendra.Jamadagni@(protected)]
Sent: Thursday, June 03, 2004 7:23 AM
To: oracle-l@(protected)
Subject: RE: 4031 - errors
Not a problem ... the switch should be controlled from outside the code, and
that means it can be changed dynamically at runtime in production if needed.
I implemented similar technique in 99 (I was a duheveloper then), the debug
code is still in production code, but turned off.
all it takes a simple update and on the next invocation debug messages are
turned on. Here is the sample ...
oraclei@(protected) <mailto:oraclei@(protected) > > sys
SQL*Plus: Release 9.2.0.2.0 - Production on Thu Jun 3 08:22:27 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Oracle Data
Mining options
JServer Release 9.2.0.2.0 - Production
08:22:28 SQL > select * from v_debug_state;
NAME TYPE Debug?
-- ---- ---- ---- ---- ---- ---- ---- -- -- ---- -- -- ---- ---- ---
DBPK_PACING_DATA PACKAGE Debugging is Off
DBPK_RS100 PACKAGE Debugging is Off
DBPK_SBS_FINAL_LOG PACKAGE Debugging is Off
DBPK_SBS_LOG PACKAGE Debugging is Off
DBPK_SIDE_BY_SIDE PACKAGE Debugging is Off
5 rows selected.
08:22:36 SQL >
Raj
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---
----
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
select standard_disclaimer from company_requirements;
QOTD: Any clod can have facts, having an opinion is an art !
__ __
From: oracle-l-bounce@(protected) [mailto:oracle-l-bounce@(protected)]
On Behalf Of Duret, Kathy
Sent: Wednesday, June 02, 2004 5:40 PM
To: 'oracle-l@(protected) '
Subject: RE: 4031 - errors
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.
Kathy
-- --Original Message-- --
From: Jared.Still@(protected) [mailto:Jared.Still@(protected)]
Sent: Wednesday, June 02, 2004 4:32 PM
To: oracle-l@(protected)
Subject: RE: 4031 - errors
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
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.
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.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN " >
<HTML > <HEAD >
<META HTTP-EQUIV= "Content-Type " CONTENT= "text/html; charset=US-ASCII " >
<TITLE >Message </TITLE >
<META content= "MSHTML 6.00.2800.1400 " name=GENERATOR > </HEAD >
<BODY >
<DIV > <SPAN class=775515813-03062004 > <FONT face=Arial color=#0000ff
size=2 >Kathy, </FONT > </SPAN > </DIV >
<DIV > <SPAN class=775515813-03062004 > <FONT face=Arial color=#0000ff
size=2 > </FONT > </SPAN > </DIV >
<DIV > <SPAN class=775515813-03062004 > <FONT face=Arial color=#0000ff size=2 >Your
developers sound like they follow my favorite quote: </FONT > </SPAN > </DIV >
<DIV > <SPAN class=775515813-03062004 > <FONT face=Arial color=#0000ff
size=2 > </FONT > </SPAN > </DIV >
<DIV > <SPAN class=775515813-03062004 > <FONT face=Arial color=#0000ff size=2 > "Lets
hurry up and do it wrong so that we can fix it right later ". </FONT > </SPAN > </DIV >
<DIV > <SPAN class=775515813-03062004 > <FONT face=Arial color=#0000ff
size=2 > </FONT > </SPAN > </DIV >
<DIV > <SPAN class=775515813-03062004 > <FONT face=Arial color=#0000ff size=2 >just
beautiful. no time to get the answers up front, but lots of time to
teeth-nash later on to fix it. </FONT > </SPAN > </DIV >
<DIV > <FONT face=Arial color=#0000ff size=2 > </FONT > </DIV >
<DIV > <SPAN class=775515813-03062004 > <FONT face=Arial color=#0000ff size=2 >gotta
love it. </FONT > </SPAN > </DIV >
<P > <FONT face=Arial size=2 >Tom Mercadante </FONT > <BR > <FONT face=Arial
size=2 >Oracle Certified Professional </FONT > </P >
<BLOCKQUOTE dir=ltr style= "MARGIN-RIGHT: 0px " >
<DIV > </DIV >
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left > <FONT
face=Tahoma size=2 >-- --Original Message-- -- <BR > <B >From: </B > Duret, Kathy
[mailto:kduret@(protected)] <BR > <B >Sent: </B > Thursday, June 03, 2004
9:54 AM <BR > <B >To: </B > 'oracle-l@(protected) ' <BR > <B >Subject: </B > RE: 4031 -
errors <BR > <BR > </FONT > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff
size=2 >Sounds like a great plan. I will check it out. I have
to get rid of all the dbms_output.enable that is hard coded all over the place
and other things before I can do this. </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff
size=2 > </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff size=2 >And
I wasn 't worried about the developers... I was worried about monkey boy .... I
spend most of my week trying to fix alot of the stuff he
does. </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff
size=2 > </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff size=2 >One
month ago for instance, he set pctincreased and pct used to over 100 on the
tables he moved into production..... </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff
size=2 > </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff size=2 >I am
trying get it so I can do a code review BEFORE things get moved into
production....but it doesn 't go to far....they consider themselves fast paced
here which translates into: </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff
size=2 > </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff
size=2 >Throw stuff into production, fix the problems, redo the code, fix
the problems, redo the code, user hates it, revamp the code, more
problems..... leave the old tables, view behind and of course there are
</FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff
size=2 >still reports and batch jobs using the old tables that they don 't have
time to change their code to take care of. </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff
size=2 > </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff size=2 >well
enough venting for today. monkey boy caused another problem that I have
to fix.... </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff
size=2 > </FONT > </SPAN > </DIV >
<DIV > <SPAN class=937410813-03062004 > <FONT face=Arial color=#0000ff
size=2 >Kathy </FONT > </SPAN > </DIV >
<BLOCKQUOTE dir=ltr style= "MARGIN-RIGHT: 0px " >
<DIV class=OutlookMessageHeader dir=ltr align=left > <FONT face=Tahoma
size=2 >-- --Original Message-- -- <BR > <B >From: </B > Jamadagni, Rajendra
[mailto:Rajendra.Jamadagni@(protected)] <BR > <B >Sent: </B > Thursday, June 03, 2004
7:23 AM <BR > <B >To: </B > oracle-l@(protected) <BR > <B >Subject: </B > RE: 4031 -
errors <BR > <BR > </FONT > </DIV >
<DIV dir=ltr align=left > <SPAN class=261561912-03062004 > <FONT
face= "Courier New " color=#0000ff size=2 >Not a problem ... the switch should
be controlled from outside the code, and that means it can be changed
dynamically at runtime in production if needed. I implemented similar
technique in 99 (I was a duheveloper then), the debug code is still in
production code, but turned off. </FONT > </SPAN > </DIV >
<DIV dir=ltr align=left > <SPAN class=261561912-03062004 > <FONT
face= "Courier New " color=#0000ff size=2 > </FONT > </SPAN > </DIV >
<DIV dir=ltr align=left > <SPAN class=261561912-03062004 > <FONT
face= "Courier New " color=#0000ff size=2 >all it takes a simple update and on
the next invocation debug messages are turned on. Here is the sample ...
</FONT > </SPAN > </DIV >
<DIV dir=ltr align=left > <SPAN class=261561912-03062004 > <FONT
face= "Courier New " color=#0000ff size=2 > </FONT > </SPAN > </DIV >
<DIV dir=ltr align=left > <SPAN class=261561912-03062004 > <FONT
face= "Courier New " color=#0000ff size=2 > <A
href= "mailto:oraclei@(protected) " >oraclei@(protected) </A >>
sys </FONT > </SPAN > </DIV >
<DIV > <SPAN class=261561912-03062004 > <FONT face= "Courier New " color=#0000ff
size=2 >SQL*Plus: Release 9.2.0.2.0 - Production on Thu Jun 3 08:22:27
2004 </FONT > </SPAN > </DIV >
<DIV > <SPAN class=261561912-03062004 > <FONT face= "Courier New " color=#0000ff
size=2 >Copyright (c) 1982, 2002, Oracle Corporation. All rights
reserved. </FONT > </SPAN > </DIV >
<DIV > <SPAN class=261561912-03062004 > <FONT face= "Courier New " color=#0000ff
size=2 >Connected to: <BR >Oracle9i Enterprise Edition Release 9.2.0.2.0 -
64bit Production <BR >With the Partitioning, Real Application Clusters, OLAP
and Oracle Data Mining options <BR >JServer Release 9.2.0.2.0 -
Production </FONT > </DIV >
<DIV > <FONT face= "Courier New " color=#0000ff size=2 > </FONT > </DIV >
<DIV dir=ltr align=left > <FONT face= "Courier New " color=#0000ff
size=2 >08:22:28 SQL> select * from v_debug_state; </FONT > </DIV >
<DIV > <FONT face= "Courier New " color=#0000ff
size=2 >NAME
TYPE
Debug? <BR >-- ---- ---- ---- ---- ---- ---- ---- -- -- ---- --
-- ---- ---- --- <BR >DBPK_PACING_DATA
PACKAGE Debugging is
Off <BR >DBPK_RS100
PACKAGE Debugging is
Off <BR >DBPK_SBS_FINAL_LOG
PACKAGE Debugging is
Off <BR >DBPK_SBS_LOG
PACKAGE Debugging is
Off <BR >DBPK_SIDE_BY_SIDE
PACKAGE Debugging is Off <BR > </FONT > </DIV >
<DIV dir=ltr align=left > <FONT face= "Courier New " > <FONT color=#0000ff > <FONT
size=2 > <SPAN class=261561912-03062004 >5 </SPAN > rows
selected. </FONT > </FONT > </FONT > </DIV >
<DIV > <FONT face= "Courier New " color=#0000ff size=2 >08:22:36 SQL>
<BR > </FONT > </SPAN > </DIV >
<DIV dir=ltr align=left > <SPAN class=261561912-03062004 > <FONT
face= "Courier New " color=#0000ff size=2 >Raj </FONT > </SPAN > </DIV >
<DIV dir=ltr align=left > <SPAN class=261561912-03062004 > </SPAN > <SPAN
lang=en-us > <FONT face= "Courier New "
size=2 >-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -- <BR >Rajendra
dot Jamadagni at nospamespn dot com <BR >All Views expressed in this email are
strictly personal. <BR >select standard_disclaimer from
company_requirements; <BR >QOTD: Any clod can have facts, having an opinion is
an art ! </FONT > </SPAN > </DIV >
<DIV > </DIV > <BR >
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left >
<HR tabIndex=-1 >
<FONT face=Tahoma size=2 > <B >From: </B > oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)] <B >On Behalf Of </B >Duret,
Kathy <BR > <B >Sent: </B > Wednesday, June 02, 2004 5:40 PM <BR > <B >To: </B >
'oracle-l@(protected) ' <BR > <B >Subject: </B > RE: 4031 -
errors <BR > </FONT > <BR > </DIV >
<DIV > </DIV >
<DIV > <FONT face=Arial color=#0000ff size=2 > <SPAN
class=966393421-02062004 >the trouble with the switch here it that the
developers forget to switch it off. </SPAN > </FONT > </DIV >
<DIV > <FONT face=Arial color=#0000ff size=2 > <SPAN
class=966393421-02062004 > </SPAN > </FONT > </DIV >
<DIV > <FONT face=Arial color=#0000ff size=2 > <SPAN class=966393421-02062004 >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 </SPAN > </FONT > </DIV >
<DIV > <FONT face=Arial color=#0000ff size=2 > <SPAN
class=966393421-02062004 >carving another face on mount Rushmore.
</SPAN > </FONT > </DIV >
<DIV > <FONT face=Arial color=#0000ff size=2 > <SPAN
class=966393421-02062004 > </SPAN > </FONT > </DIV >
<DIV > <FONT face=Arial color=#0000ff size=2 > <SPAN
class=966393421-02062004 >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. </SPAN > </FONT > </DIV >
<DIV > <FONT face=Arial color=#0000ff size=2 > <SPAN
class=966393421-02062004 > </SPAN > </FONT > </DIV >
<DIV > <FONT face=Arial color=#0000ff size=2 > <SPAN
class=966393421-02062004 >Kathy </SPAN > </FONT > </DIV >
<BLOCKQUOTE >
<DIV class=OutlookMessageHeader dir=ltr align=left > <FONT face=Tahoma
size=2 >-- --Original Message-- -- <BR > <B >From: </B > Jared.Still@(protected)
[mailto:Jared.Still@(protected)] <BR > <B >Sent: </B > Wednesday, June 02, 2004
4:32 PM <BR > <B >To: </B > oracle-l@(protected) <BR > <B >Subject: </B > RE: 4031 -
errors <BR > <BR > </FONT > </DIV > <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 > </BLOCKQUOTE > <BR > <BR > <BR >
<P > <FONT face=Arial size=2 >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. </FONT > </P > </BLOCKQUOTE > <BR > <BR > <BR >
<P > <FONT face=Arial size=2 >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. </FONT > </P > </BLOCKQUOTE > </BODY > </HTML >
|
|
