Skip to main content

Shameless, I know. But it feels so good...

We all like to get patted on the back, stroked, egos fed, right?

I am no exception.

And the very best kind of stroking for me is when a developer tells me things like:

"Your book changed my life."

"That code you posted on your blog saved me a whole day's work."

and so on. Honestly, I don't think the endorphin flow is from some sort of personal pride. It's more that the enormous chunk of my life that I have devoted to PL/SQL can help other individuals improve their quality of life and personal happiness in some way (I am much less enamored with helping the bottom line of corporations).

In that vein, this morning, I received the following wonderful email:

Subject: Error trapping - THANK YOU
Steven,

Your Oracle article about error trapping in PL/SQL saved my bacon this morning. I woke up to a production error with commercial software that we wrote. 

I had already implemented many aspects of your recommendations. When I started troubleshooting at 0600, I had tools and plans in hand (the solution didn't come for 2 hours) BUT I had tools and plans!!!!

I debated posting my efforts publicly because I simply parroted your work. 

After the firefight this morning, I recognized that echoing your words can only help the cause.

Again, Thank you!!!!


Ah....it doesn't get better than that. Well, there is something better than that: spending time with my granddaughter, Loey, who at 3.5 years of age is a true fashionista:




Comments

  1. Martin D'SouzaMay 15, 2015 at 7:55 AM

    For anyone looking for a complete PL/SQL logging platform, there's a widely used free open source project called Logger: https://github.com/OraOpenSource/Logger

    ReplyDelete
  2. iudithMay 15, 2015 at 10:23 AM

    Hello Steven, All,
    It is very upsetting indeed to witness an error scenario, without any opportunity
    to research it, or being able to offer any advice ...
    Sad to say, but in many such occasions, since it is NOT my own code and I have
    practically no chance to touch it in any way, I am practically helpless ...
    I wish I were in a more cooperative environment, in which at least out of curiosity
    we could work together at least to isolate the problem, and, since it looks like
    an Oracle bug, at least to be able to create a reproducible sample case.
    I am always in favor of sacrificing even a high amount of so called "productive time"
    for the sake of research and, maybe, for highlighting a case that might hid a bug ...

    And ... yes ... Loey is indeed a very nice "Little Lady" ... still enjoying the opportunity
    of polarizing the 100% attention for her alone :):)
    As I remember, for not too much time left ... even if she will probably not have to share it with the happy PL/SQL developers community in the first place :):)

    Cheers,
    Iudith

    ReplyDelete

Post a Comment

Popular posts from this blog

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of work, revamping algorithms, ensuring correctness, you know the score. Then my eyes snagge
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch,
4 comments
Read more

Quick Guide to User-Defined Types in Oracle PL/SQL

A Twitter follower recently asked for more information on user-defined types in the PL/SQL language, and I figured the best way to answer is to offer up this blog post. PL/SQL is a strongly-typed language . Before you can work with a variable or constant, it must be declared with a type (yes, PL/SQL also supports lots of implicit conversions from one type to another, but still, everything must be declared with a type). PL/SQL offers a wide array of pre-defined data types , both in the language natively (such as VARCHAR2, PLS_INTEGER, BOOLEAN, etc.) and in a variety of supplied packages (e.g., the NUMBER_TABLE collection type in the DBMS_SQL package). Data types in PL/SQL can be scalars, such as strings and numbers, or composite (consisting of one or more scalars), such as record types, collection types and object types. You can't really declare your own "user-defined" scalars, though you can define subtypes  from those scalars, which can be very helpful from the p
24 comments
Read more