Skip to main content

My New Oracle Badge

Went out to Reston VA to meet with my new boss, Mike Hichwa, and some of the members of his team. It was a fantastic few days. For one thing, there was no shortage of folks eager to help me get my new Macbook Pro set up. That was especially important since I have used a Windows machine for decades. The Macbook is a beautiful machine and the Mac OS is a joy, but still....lots of adjustments to make. So: a grateful shout out to Christina, Taj and Shakeeb in particular for their patience as I went back to them again and again with questions.

But the first thing I did on arriving at the Oracle offices was to get my badge. I gotta say I was a bit surprised at how excited I was about that. It's been a long time since I've had a new job, and I am pleased as can be to be back "on the inside" at Oracle Corporation.

We're still sorting the details of my responsibilities at Oracle, but I can tell for sure that I will be doing some new and very different things, which you will enjoy greatly!

And so to finish off this post, here's my badge.....

 




Comments

  1. UnknownApril 8, 2014 at 2:19 AM

    Nice badge! I'm looking fwd to see my boss let me choose Mac OS X according to my wish, until then I must stay on Windows *DEEP SIGH*.

    ReplyDelete
  2. AnonymousApril 9, 2014 at 9:08 AM

    Congrats! :)

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

PL/SQL 101: Three ways to get error message/stack in PL/SQL

The PL/SQL Challenge quiz for 10 September - 16 September 2016 explored the different ways you can obtain the error message / stack in PL/SQL. Note: an error stack is a sequence of multiple error messages that can occur when an exception is propagated and re-raised through several layers of nested blocks. The three ways are: SQLERRM - The original, traditional and (oddly enough) not currently recommended function to get the current error message. Not recommended because the next two options avoid a problem which you are unlikely  to run into: the error stack will be truncated at 512 bytes, and you might lose some error information. DBMS_UTILITY.FORMAT_ERROR_STACK - Returns the error message / stack, and will not truncate your string like SQLERRM will. UTL_CALL_STACK API - Added in Oracle Database 12c, the UTL_CALL_STACK package offers a comprehensive API into the execution call stack, the error stack and the error backtrace.  Note: check out this LiveSQL script if...
5 comments
Read more