Skip to main content

UKOUG 2008 Report Back

This year I decided to do just one post about the UKOUG and not - as previous year - (try to) get out a post every day. Takes the pressure of me...
The first impression is that Birmingham was quite cold this time of year, the second is that the UKOUG seems less crowded this year. The first observation is quite right, the second one is wrong. Due to the shifted schedule of the session, they not all start and end at the same time, so the crowd is more scattered over the day. So no long lines for the food or traffic jams in the Exhibition Hall (the fact was that there where about 2,250 attendees, 'just' 5% less than next year - probably to do with the financial situation out there).
I won't list all the sessions I went to: See the previous post about my intentions - I didn't made all of them...

My personal top 3 this year (in order of appearance):

Beginners' Guide To Trouble-shooting
by Jonathan Lewis
I had never seen Jonathan presenting before but it is good to get an introduction into this subject by the master himself. He split up the performance in a quadrant with 'Wait Time' and 'Service' on one side and 'Using' and 'Competing' on the other side. That gives an insight where to look for one of the three classifications of problems : 'My task is slow', 'The batch took too long', 'The system is slow'.

Oracle SQL Developer: Focusing on a Few Advanced Features by Sue Harper
Sue showed how to create and use XML extensions, remote debugging APEX applications and how to Refactor anonymous PL/SQL blocks in APEX into database procedures. If she had the time she could have shown a lot more than she did, but (just like in a lot of other sessions) 45 minutes is very very short....

Performance Tuning Basics by Doug Burns
Doug did a great job in big Hall 1. His presentation ran very smoothly as well as in presentation style, in the sheets (just a few words or a picture on every sheet) as in content. He explained about ASH, AWR and ADDM - acronyms I had heard about but didn't quite understand the details (as I am not a DBA - apparently). The main message was: The only thing that really matters in the end is: DB Time, not latches, buffer gets, reads etc - only the time that passes between a user action and a system response defines the performance (but of course all the reads and latches and stuff lead to a certain DB Time...).

My own session:
On the last full day of the conference around 03:00 PM I had my session. It was a rather small room, with around 100 seats but pretty well attended with an audience of around 80 people. IMHO all went very good, ended right on time and could even answer some questions. My goal was to show that you can do a lot more with APEX than what is widely known and I think I got that message across. I did a sneak peek at the evaluation forms and saw a lot of 'Excellents' and 'Very goods' and some very positive comments. So I was (and still am) quite happy about that! BTW I already uploaded the application to apex.oracle.com, but I still have to seed it with some data. If that is finished I'll post the link on this blog.
Because there wasn't that much APEX going on, I 'had' to visit sessions with other interests, like performance tuning and JDev. I don't know yet if that's a good or a bad thing. But I will sure to try to get in (again as a presenter) next year! BTW next year the UKOUG will split the different streams into different shorter events. The (to me) most interesting event will still be at the end of November, but then only for three days.

Comments

Unknown said…
I was at your session and for me it was the best session that I went to at the conference.

Will be good to see your application on the Apex hosted site.
Anonymous said…
Good to see you again, Roel, and thanks for the kind comments which are much appreciated.

I agree with you, too. Let's get to a three day, more focussed conference so that all parties can get the most from an event without trying to cram too many events together.

Cheers,

Doug
Anonymous said…
Roel,

Thanks for the info on these.

Is there any chance that Sue Harper's presentation on SQL Developer is available online? I'd love to see the Apex-related parts.

Thanks also for posting your slides. Obviously not as good as seeing them, but my boss wouldn't okay the trip across the pond to see it live! :-)
Stew said…
Sorry to be a pest, but I tried to look through your embedded slide show and it's too small to read. When I clicked on the links to view it at the source, it said the slide show was private. It looks like you used some cool addins that I'd like to investigate. Could you please made the slides public?

Thanks again,

Stew
Roel said…
@Paul: Thanks for the feedback. It almost makes me blush.

@Stew: I changed the slideshow setting to public now.
SydOracle said…
Thanks.
For Stew, there is a 'full screen' mode if you click on the whiteboard icon near the bottom right.
Stew said…
Thanks to both Roel and Gary.

Popular posts from this blog

Filtering in the APEX Interactive Grid

Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for

Stop using validations for checking constraints !

 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function