Hello,

Is there a simple way to debug DB2 SQL procedures, such as: which branch
of a conditional construct was chosen, what value did a counter reach,
etc, _without_ installing some big, complicated IDE?

My question could maybe be rephrased as "is there a way to perform printf-
style debugging in DB2 SQL procedures?"

If not: I'm considering creating a C-based UDF which logs arbitrary
strings to syslog, so that a SQL procedure can inform the surroundings of
its state during development.

--
Troels

On Sep 5, 11:17*pm, Troels Arvin <tro... (AT) arvin (DOT) dk> wrote:
I don't know if Serge's SQL PL/PL/SQL profiler would be of use:
http://www.google.com/url?sa=D&q=htt...wEjqjrdlB7VRmg

(I hope this link works, otherwise he had posted it a short while
ago.)

What else comes to my mind is a debug table and a debug function,
something like insert into dbg values (current timestamp, message).

PL/SQL should have a debug function built in if you're on V9.7.

Sorry, mainly guesses here.

Hello,

Willem Fischer wrote:

I'm not thinking about performance at this point, but may come in handy
later on.


Yes, but can such inserts be done outside of the currently running
transaction? - Otherwise I suppose that no messages will end up in the
message-table?


That's interesting. I suppose this relates to DBMS_OUTPUT which seems to
be exactly what I was looking for. Thanks.

--
Troels

Hello,

I wrote:
Hmm. DBMS_OUTPUT requires that Oracle compatibility be enabled :-(

Is Oracle compatibility enabled in all DB2 LUW 9.7 editions, or does it
require a special licence?

--
Troels

On Sep 6, 12:42*pm, Troels Arvin <tro... (AT) arvin (DOT) dk> wrote:
It depends on which specific compatibility feature you want to use.
DB2 Enterprise Edition is the only version that supports the full
spectrum.
Regarding DBMS_OUTPUT (and other system-defined modules), this is
supported in Workgroup Edition but not in Personal Edition or Express(-
C) Edition, see:
http://publib.boulder.ibm.com/infoce.../c0053670.html

You may also want to checkout this forum-post on DeveloperWorks:
http://www.ibm.com/developerworks/fo...85419&tstart=0

HTH

--
Jeroen

On Sep 5, 2:17*pm, Troels Arvin <tro... (AT) arvin (DOT) dk> wrote:
One thing you can do is create a global temporary table, and have
your
procedure insert records into the GTT. Then, simply query your GTT
to
see your output...

On 9/6/2010 10:28 AM, The Boss wrote:

DBMS_OUTPUT is supported without compatibility vector.
Also if you search for my name on developerworks you will find an
article on SQL PL "tracing".
Out of the box it only logs entry/exit/error, but I also provided a DATA
function which you can embed as printf.

There was some snafu in DB2 9.7.0 for Windows with the library used
which was rectified no later than FP2. So if you want to go that route
ensure you are on the latest and greatest on Windows.

Also if you use the SQL PL / PL/SQL profiler you can execute it after
flushing the package cache to get an individual run.
(Probably not something to do on a production machine...)

Send me a note and I send you a more streamlined version of the profiler...

Cheers
Serge
--
Serge Rielau
SQL Architect DB2 for LUW
IBM Toronto Lab