02 November, 2009

New APEX training Dates...

Sumner Technologies has just announced a new set of public and on-line training dates:

Classroom Based Public Training

Alexandria, Virginia :
As part of our way of saying thanks to you, these two sessions will be discounted even more than normal. Intro to APEX I will be only $1200 per student, and Intro to APEX II will be only $800. And if you sign up for both classes, you can save another $100 and take both for only $1900 per student!

Salt Lake City, Utah :
On-Line Based Public Training
In addition to the public instructor-led training, we are also offering a number of public online classes. Our online classes feature the same exact same content as our instructor-led classes, and are conducted over a web conference and toll-free phone line, making it easy to attend from either work or home. All sessions are taught live by our same great instructors who conduct our on-site classes. Each session will begin at 12:00 PM ET and run for approximately four hours.
If you register more than one student from your organization for an online class, each student will receive a 10% discount.

Questions, or want private on-site training?

Should you have any questions about the courses, technical requirements or want to discuss private on-site training, please send us a note at info@sumnertech.com or call us at (703) 879-4615. We look forward to seeing you soon!

Oracle APEX and Oracle Application Express are registered trademarks of Oracle Corporation and/or its affiliates.

15 June, 2009

All Change Please...

As I mentioned in my last post, on June 1, 2009 I joined the team at Sumner Technologies. Since then, Scott Spendolini and I have been working on Sumner's portfolio to broaden the scope of what we're offering.

New items include SumnerPrint, a PL/SQL-based solution that allows you to easily print APEX reports to PDF, HTML and XLS, and SumnerFramework, an application security and management framework for APEX. We're also working on several new courses and service offerings.

As part of the inevitable website changes, we've introduced a new company blog. We'll be using this blog to provide information about products, services and training classes that we provide as well as unique technical tips and tricks on APEX and other Oracle-related technologies.

You can subscribe to the SumnertechBlog at http://feeds2.feedburner.com/SumnertechBlog.

I'll still be updating my blog, but it will become much more personal, and much less about Oracle and APEX.

And don't forget to come visit us at ODTUG KALAIDOSOPE!

11 June, 2009

ODTUG Kaleidoscope - The countdown begins...

As many of you know, ODTUG Kaleidoscope runs from June 21-25 in Monterey, California. Topics covered will range from Essbase and Hyperion, BI and Data Warehousing, SOA, BPM to my favorite, Application Express.

This year there are over 40+ APEX related presentations, a number of which will be presented by Oracle ACE and ACE DIRECTORS. Pretty exciting stuff if you're an APEX geek like me. But for me there are several things that will make this particular conference "special".

Of course, the opportunity to attend so many good sessions is high on my list, but I also get to see a number of people that I haven't seen for quite some time. I'm really looking forward to the APEX Meet-Up that John Scott is organizing.

But one thing that will be very different is that it will be my first conference as a partner in Sumner Technologies. As of June 1, 2009 I joined forces with Scott Spendolini to help broaden Sumner's offerings. And, not only will Sumner (Scott) be presenting, but we will also have a booth in the exhibitors area this year.

To coincide with all of this, we've just relaunched our website outlining our full range of course, services and software offerings.

On top of all of that, the 23rd of June is my 42nd Birthday. What a great opportunity to celebrate with all my APEX friends!

So, if you're there, stop by the booth and say "Hi". I look forward to seeing you all there.

08 April, 2009

The trouble with DBMS_XPLAN...

As some of you may know, I used to be the Product Development Director for Hotsos. Part of my job entailed work the Laredo product, which helps identify potentials performance problem areas when making changes to your database structure, indexes, statistics, init parameters, etc.

Recently I was called back in on a particularly sticky problem that one of their customers was having in using Laredo. Without going into a long and arduous explanation, the problem boiled down to the fact that Laredo was using DBMS_XPLAN to emit formatted explain plans to the user and they were coming out wrong.

I suppose you would have expected me to learn my lesson by now, but I kind of expect the Oracle documentation to be correct for the most part. So when we looked up DBMS_XPLAN.DISPLAY in the PL/SQL Packages and Types Reference for 10g, I kind of expected to be able to take the code example and use it verbatim.

Here is what it said:

DISPLAY Function

This table function displays the contents of the plan table.

In addition, you can use this table function to display any plan (with or without statistics) stored in a table as long as the columns of this table are named the same as columns of the plan table (or V$SQL_PLAN_STATISTICS_ALL if statistics are included). You can apply a predicate on the specified table to select rows of the plan to display.




Specifies the statement_id of the plan to be displayed. This parameter defaults to NULL, which is the default when the EXPLAIN PLAN command is executed without a set statement_id clause.If no statement_id is specified, the function will show you the plan of the most recent explained statement.

And even came with an example that showed how to use it:

To display the plan for a statement identified by ‘foo’, such as statement_id=’foo’:

SELECT * FROM table (DBMS_XPLAN.DISPLAY(‘plan_table’, ‘foo’));

So, when we coded a statement that went into the product that looked like the following, I would have expected to be shown the explain plan output for the correct statement.

select * from table(DBMS_XPLAN.DISPLAY(‘LAR_SCENARIO_PLAN_VW’,’82-2476-34’, ‘BASIC’))

But instead what we got was THIS:


Notice that we get two “0” IDs and two “1” IDs. And they are OBVIOUSLY from two different statements! WHAT THE….

Now I know I specifically told it to get me only the the plan where “82-2476-34” was that STATEMENT_ID. Did I get the ordinal position of the parameters wrong? I tried again with the following statement:

select *
STATEMENT_ID =>;’82-2476-34’,

Unfortunately, I received the same result. SO, I decided to go digging into the underlying plan table to see what was going on. I decided to select all rows where the STATEMENT_ID was equal to ‘82-2476-34’ to see if there was a duplicate STATEMENT_ID in the table. No luck.


Hmm... That doesn't make any sense! There has to be something going on that makes DBMS_XPLAN bring back extraneous rows. My search then turned to the extraneous rows to try to find what they had in common with the rows that should have been coming back. So I started looking at the expanded output of DBMS_XPLAN and trudged through the base table examining the individual attributes to see where DMBS_XPLAN might have been losing it's mind.

The search finally lead me to PLAN_ID. If I selected all the records from the base table where the PLAN_ID = 7191, the same PLAN_ID as my original statement, here is what I got.


EUREKA! But WHY would DBMS_XPLAN bring back other statement ID's when I specifically passed in statement id "82-2476-34”? Luckily DBMS_XPLAN is not wrapped so I was able to use SQL-DEVELOPER's debug feature to walk through the execution of DMBS_XPLAN and grab the explain plan SQL.

/*+ opt_param('parallel_execution_enabled','false') */
NVL( other_xml, remarks ) other_xml,
NULL sql_profile,
NULL sql_plan_baseline,
plan_id =
MAX( plan_id )
WHERE id =0
AND statement_id = :stmt_id)


The problem shows up very clearly in the generated SQL. The WHERE clause is taking the STATEMENT_ID I passed and getting the MAX(PLAN_ID) and selecting ALL records that have that PLAN_ID. But what if, as in my case, there are multiple statements with the same plan ID?

OK. Well, since DBMS_XPLAN provides the ability to add filter predicates, I'll try call the procedure as follows:

select * from table(DBMS_XPLAN.DISPLAY(‘LAR_SCENARIO_PLAN_VW’,’82-2476-34’, ‘BASIC’, 'STATEMENT_ID= ''82-2476-34'''))

Adding the filter predicate changed the where clause, but not as I thought it might.


AND statement_id = :stmt_id
AND STATEMENT_ID = '82-2476-34'

WHAT THE %*@#? ...

Ok... I walked through the code again a little more carefully and came to the conclusion that this is just a run of the mill code error. Oracle are building pieces of the where clause and pasting them together based on certain criteria, mixing and matching based on what your PLAN_TABLE looks like. When it comes to the part where they paste in the STATEMENT_ID that you pass in, if you haven't passed anything to FILTER_PRED, they forget to paste the predicates limiting the selection to your chosen STATEMENT ID in all the necessary places.

While the resulting WHERE CLAUSE you get by actually passing something in to FILTER_PRED is not technically correct, it does work.

I hope this might save some people some time, if they run into something similar. In the mean time I'll be looking into METALINK to see it the bug is logged, and if not I'll log it.

Happy Coding!

24 February, 2009

JavaScript and Dates.

If you've ever tried to work with date manipulation and formatting in JavaScript, then you know what a hassle it can be. While trying to solve a particularly itchy problem with dates, I ran across this post by Steven Levithan that everyone should be aware of.

He's put together a very nice little Java Script library that lets you format a JavaScript Date object very easily. The available date format masks have been abstracted in such a way that it is quite easy to make them match what you're used to as an Oracle developer.

So, if you ever have to deal with Date formatting in Javascript, then this is definitely something to check out.