Skip to main content

Collaborate 2011 - Day 5 and Wrap Up

By
The last (half day) of the conference. Makes me wonder why most (if not all) of the conferences add an additional half day after throwing "the" big party. Why not make it a full day and throw the party at that night - or just end with the Wednesday night party. That will keep everyone at the show. Because these last half days are usually not very well attended anymore, which is not very kind to the speakers.
Anyway, the first session of today was Obscure Tools of the Trade for Tuning SQL. The speaker - after handing out, or throwing, candies, discussed tools that are freely available to get insight in how your SQL runs. The first was not that obscure: DBMS_XPLAN. This package can show all kinds of details on your SQL and can even show AWR reports. And if you use it with the gather_plan_statistics hint, you can also show the expected rows vs the actual rows (so your statistics may be wrong). The next one wasTrace Analyzer, a.k.a. TRCA, available via Metalin. It is like TKPROF on steroids. The main advantage is, you can provide your developers access to this information without access to the udump directory or bothering the DBA. It generates nice HTML readable and navigable output.  Another one was SQLT (SQLTXPLAIN), also available from Metalink This tool understands DB-links, while TRCA does not. It has multiple methods, like xtract, xecute etc The output is like the TRCA output, but TRCA needs SQL, this one needs trace files. TRCA gives a broader view, SQLT more detailed. The last one discussed was Oracle Active Report for Real Time SQL Monitoring. You can use this by using the dbms_sqltune (11gr2) package. It returns HTML, containing Flash or not. So it generates very nice, OEM like, output (with or without using OEM).
Then Rich Niemiec did a very nice presentation about Trends in de Database World. Did you know one Oracle Database is capable of storing all, yes all, information on the entire planet if we only had the hardware? So, that's cloud computing to the max! And another remarkable thing (I've heard before, but still): The development of Fusion Applications is the largest project in the world! The three major trends Rich discussed where Consolidation, the lower cost grid using Linux and Globalisation. Of course they all come together at the end. An nice to know : Oracle's original name was SDL.
The last (real) one of the conference was about SQL Anti Patterns. It appeared to be a MySQL focussed session, but still a lot of the common mistakes made in the MySQL world also apply to the Oracle world, like these:
1. Check if a row exists before insert. You can end up with a race condition, two people might try to do the same thing (apart from that, it is an extra database action). So instead of that, just do insert and catch the error.
2. All string columns have the same, to large, size. Might take too much space for tables and indexes and arrays. So right size your strings. Another solution for reducing your indexes: use the first x characters of a column.
3. The assumption that a select without order by returns rows in order of primary key. Not true, not in MySQL, not in Oracle. Can be true if it is an "index only" query. There is no "natural" order. So if you need a specific ordering, specify that.
4. Commit and rollback in lower level functions. These may lead to unexpected results like half transactions. Ue these only on the highest calling level - the service layer, thus in the application itself.
The last session of this Collaborate was Iron Application Throw-down. Two teams had set up a solution for creating a session planner. The most striving thing was, both uses Oracle Application Express as the preferred front-end! I wonder why....

All in all, Collaborate is for 80% an applications event. So most of the session are aimed at EBS, Peoplesoft, JDEdwards etc. The same holds for the exhibitors. There is some DBA stuff going on (around 10% I guess) and the other 10% is Development, split by regular SQL and PL/SQL and APEX. No Forms, Designer and - even more remarkable, hardly no ADF or other Fusion Middleware!  So if you are a developer, the first event I would recommend, is ODTUG's KScope - see you all there!
Labels:
Location: Orlando, FL, USA

Comments

Learco Brizzi said…
Nice story. See you in Long Beach!
3:25 pm
Post a Comment

Popular posts from this blog

Filtering in the APEX Interactive Grid

By
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
1 comment
Read more

apex_application.g_f0x array processing in Oracle 12

By
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
Post a Comment
Read more

Stop using validations for checking constraints !

By
 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
Post a Comment
Read more