In the April session, Steven touched on his thoughts regarding where to handle exceptions (briefly: as close as possible to where it was raised). This conflicts with Tom Kyte's position that you should let the exception propagate up to the outermost block and then handle exceptions there. Tom can't speak for himself, but Steven is sure others will chime in.

00:00 Setting the stage
03:15 Tom Says
04:00 Steven Says
05:00 Chris Says
08:15 LiveSQL exploration
11:40 Avoiding redundant entries in error log
13:30 Using conditional compilation to direct output to screen
15:00 Chris says: handle expected exceptions, avoid WHEN OTHERS
17:30 Lots of discussion
29:30 Don’t forget to log the call stack
33:23 Picking a -20NNN error code for raise_application_error
35:29 Utility package by Sven Weller on top of utl_call_stack
38:02 Thoughts on tracing parameter values