Skip to main content

Results of the Oracle Dev Gym PL/SQL Challenge Championship for 2018

You will find below the rankings for the PL/SQL Challenge Championship for quizzes taken in 2018. The number next to the player's name is the number of times that player has participated in a championship. Below the table of results for this championship, you will find another list showing the championship history of each of these players.

Congratulations first and foremost to our top-ranked players:

1st Place: mentzel.iudith
2nd Place: Andrey Zaytsev
3rd Place: Tony Winn

Next, congratulations to everyone who played in the championship. We hope you found it entertaining, challenging and educational. And for those who were not able to participate in the championship, you can take the quizzes through the Practice feature. We will also make the championship as a whole available as a Test, so you can take it just like these players did.

Finally, many thanks and our deepest gratitude to our reviewers, especially Elic, who has once again performed an invaluable service to our community.

Rank Name Total Time % Correct Total Score
1 mentzel.iudith (5) 33 m 96% 3467
2 Andrey Zaytsev (5) 32 m 93% 3370
3 Tony Winn (3) 26 m 89% 3193
4 Ivan Blanarik (5) 33 m 86% 3116
5 Karel_Prech (5) 34 m 86% 3062
6 NielsHecker (5) 40 m 86% 3038
7 JeroenR (4) 35 m 86% 3010
8 Chase Mei (5) 24 m 82% 2951
9 MarcusM (3) 32 m 82% 2920
10 Oleksiy Ponomarenko (3) 25 m 82% 2897
11 mcelaya (4) 38 m 82% 2845
12 Maxim Borunov (5) 36 m 75% 2754
13 Jan Šerák (5) 40 m 75% 2689
14 Stelios Vlasopoulos (5) 44 m 79% 2674
15 Aleksei Davletiarov (1) 44 m 75% 2673
16 Rimantas Adomauskas (3) 33 m 75% 2666
17 seanm95 (5) 29 m 71% 2582
18 Mike Tessier (3) 33 m 71% 2567
19 siimkask (5) 18 m 71% 2525
20 Henry_A (5) 18 m 64% 2475
21 Rakesh Dadhich (5) 21 m 64% 2364
22 NickL (3) 31 m 64% 2324
23 Talebian (4) 34 m 64% 2314
24 Köteles Zsolt (1) 39 m 64% 2294
25 Otto Palenicek (3) 44 m 64% 2270
26 msonkoly (4) 44 m 61% 2171
27 Sachi (3) 10 m 61% 2108
28 RalfK (1) 13 m 54% 2045
29 PZOL (4) 30 m 57% 2027
30 richdellheim (1) 42 m 61% 1979
31 Sartograph (2) 30 m 61% 1976

Championship Performance History

After each name, the quarter in which he or she played, and the ranking in that championship.

Name History
mentzel.iudith 2014:1st, 2015:2nd, 2016:18th, 2017:2nd, 2018:1st
Andrey Zaytsev 2014:2nd, 2015:5th, 2016:1st, 2017:21st, 2018:2nd
Tony Winn 2016:2nd, 2018:3rd
Ivan Blanarik 2014:16th, 2015:16th, 2017:17th, 2018:4th
Karel_Prech 2014:4th, 2015:6th, 2016:11th, 2017:9th, 2018:5th
NielsHecker 2014:21st, 2015:1st, 2016:15th, 2017:3rd, 2018:6th
JeroenR 2014:7th, 2015:20th, 2016:6th, 2018:7th
Chase Mei 2014:25th, 2015:26th, 2016:3rd, 2017:20th, 2018:8th
MarcusM 2014:17th, 2015:37th, 2018:9th
Oleksiy Ponomarenko 2016:10th, 2017:4th, 2018:10th
mcelaya 2015:38th, 2016:34th, 2017:29th, 2018:11th
Maxim Borunov 2015:9th, 2016:17th, 2017:8th, 2018:12th
Jan Šerák 2014:24th, 2015:8th, 2016:7th, 2017:22nd, 2018:13th
Stelios Vlasopoulos 2014:37th, 2015:19th, 2016:24th, 2017:5th, 2018:14th
Aleksei Davletiarov 2018:15th
Rimantas Adomauskas 2017:6th, 2018:16th
seanm95 2014:34th, 2015:4th, 2016:9th, 2017:18th, 2018:17th
Mike Tessier 2017:33rd, 2018:18th
siimkask 2014:15th, 2015:14th, 2016:13th, 2017:12th, 2018:19th
Henry_A 2014:32nd, 2016:33rd, 2017:11th, 2018:20th
Rakesh Dadhich 2014:29th, 2015:31st, 2016:35th, 2017:31st, 2018:21st
NickL 2015:21st, 2018:22nd
Talebian 2015:23rd, 2018:23rd
Köteles Zsolt 2018:24th
Otto Palenicek 2016:29th, 2017:28th, 2018:25th
msonkoly 2015:15th, 2017:13th, 2018:26th
Sachi 2015:30th, 2016:28th, 2018:27th
RalfK 2018:28th
PZOL 2015:35th, 2017:23rd, 2018:29th
richdellheim 2018:30th
Sartograph 2017:10th, 2018:31st
Labels:

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