Skip to main content

PL/SQL Challenge Website Joining Oracle!

When I (re)joined Oracle in March 2014, the PL/SQL Challenge website was also acquired by Oracle. I'd been thinking that in a few months or so, we'd have it up and running on an Oracle server, re-branded with lots of red.

But then, well, I got kind of busy with all sorts of other stuff. My bad.

But I am very happy to announce that over the coming weekend (13-14 June), PL/SQL Challenge will go offline for hopefully no more than a few days and then resurface as an Oracle website.

And that's why for the first time in five years, we will not offer new, competitive quizzes on SQL or PL/SQL or anything else this coming week (we will still put up some of our "deja vu" quizzes). I don't want to set up quizzes and then not give you sufficient time to take them (and you never quite know what's going to happen so....).

Now, those of you who've been to the website know that we use lots of orange (why? Because it's a pleasant color and also is the thematic color of my Oracle PL/SQL books published by O'Reilly Media):


You are probably also very familiar with Oracle's use of red:


Well, do not worry - we are not going to replace all that orange with red. That would make the website unreadable, an assault on the eyes. But come 15 June, our banner will be transformed as follows:


Chills running down my spine....so exciting!

The site will be largely unchanged from current functioning. You will, however, need to accept the Oracle Terms of Use. In addition, since some players may have been using an email address on the PL/SQL Challenge different from their Oracle Single Sign-on email, we will give you an opportunity to synchronize the two accounts:


The "fine print" asks you to authorize us to transfer profile information from the PL/SQL Challenge to your Oracle Profile. We are asking for this, because the PL/SQL Challenge collected all sorts of profile information, some of which is already in your Oracle Profile, which is the "source of truth" at Oracle. So you will no longer be able to provide your name, country or company in the PL/SQL Challenge. Instead this information is stored in your Oracle Profile.

We plan over time to integrate points on the PL/SQL Challenge with OTN community rankings, but that may take a little while to complete. Do not worry, though! All your hard work and dedication on this site will be recognized.

I look forward to a greatly increased level of quiz-taking activity, as well as a broader array of quizzes offered, and I hope you do, too!

Comments

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