All change for HTML DB…

I read on Scott Spendolini’s Blog that HTML DB has been renamed to Oracle Application Express.

I think HTML DB was a really poor name, but I think the new name is a little confusing. A quick look on the net and you’ll see lots of people still talking about “Oracle Applications”, when referring to “Oracle E-Business Suite”. This new name makes HTML DB sounds like a cut down version of the Oracle ERP.

I would be interested to know what other names were passed around before this one was picked. Maybe, something a little clearer like:

  • Oracle Application Developer Express (OADE)
  • Oracle Developer Express (ODE)
  • Oracle Metadata Repository for the Runtime Generation of Applications Directly from the Database with no need for an additional Application Server… 10g! (OMRftGRoADftDwnnfaaAS… 10g!)

The last one does it for me 🙂

Cheers

Tim…

Raptor 3 (and a little bit) …

After the last abortive attempt to release Raptor EA3, we now have a new version. This one seems to have re-fixed the bits that got broken in the original version 3 release. So far so good.

It makes me wonder about the sense of releasing beta and early adopter applications to the general public. It’s a little like washing your dirty laundry in public 🙂

Cheers

Tim…

Raptor 3 Early Adopter?

The Early Adopter 3 of Raptor has hit the OTN site, but I would think before you leap in.

It looks like a number of previous bugs have been reintroduced in EA3. The SQL formatter doesn’t work in any editor except the SQL Worksheet, and the debugger appears to have gone missing. I expect the support forum may fill up rather fast. Not exactly a glowing advertisment for Oracle development 🙁

Cheers

Tim…

Critical Update, not so critical for Tru64…

The recent press interest in Oracle security has certainly increased the profile of security within our company (about time too). Unfortunately, it’s also repeatedly highlighting the lack of support provided by Oracle.

For all you guys and girls on first tier platforms, I guess you’ve applied the latest CPU already, or are at least in the planning stages.

Not me! I’m living the life of leisure, waiting for it to be released for Tru64. Although Oracle support will not give a specific date, it currently looks like it will take 2-3 weeks. Good to know that everyone and their dog knows how to hack my systems and there is no fix available.

So currently I’m still waiting for:

  • Patch 10.1.0.4.0 for 10g Release 1 on Tru64.
  • Oracle 10g Release 2 (10.2.0) on Tru64.
  • Patch 4751926 on Tru64.
  • EM 10g Release 2 Grid Agents (10.2.0) for Tru64.

If Oracle had any balls, they would ditch the majority of their platforms and maybe start providing a reasonable service. But they haven’t and they won’t.

Bunch of jokers!

Cheers

Tim…

PL/SQL vs J2EE – Some comments…

Robert Vollman has a good post called PL/SQL vs J2EE. I started to write a comment, but it became too long so I decided to post is on my blog instead.

I’ll start by saying I have a very strong position on this point, as expressed in a previous post My Utopian Development Environment.

I’m ready to be shot down in flames by a J2EE guru, but this is what I observe when I look at our J2EE applications interacting with the database.

  • By far the most executed statement on our databases is “ALTER SESSION SET ISOLATION_LEVEL = READ COMMITTED”. This is executed in excess of 100,000 times an hour for one application alone. Why? Because every time the 10g application server does anything, it seems to send this first. Now this equates to the default operation in Oracle, so it is completely pointless. The developers didn’t know how to stop it so I raised a TAR with Oracle support and was told I couldn’t!
  • The way EJBs maintain there state is rather odd. When an EJB persists it’s state, using an insert or update, it immediately requeries it’s state. This turns a single operation into two database calls.
  • When the container detects a failure in a database transaction, it retries the transaction twice before bombing out with an error. I don’t know if this is configurable or not, but this is what I see.
  • Instantiating or persisting complex structures involves multiple database calls, each made individually with their own associated network traffic.

Now I’m not a J2EE developer and these observations are based on the applications I work with, but this does not add up to a scalable and performance orientated solution to data processing.

In addition, we have some data transfers that cannot go through the application layer (don’t ask!), so we have to duplication some of the J2EE business logic in PL/SQL. Same logic, two locations, disaster waiting to happen!

Googling around leads me to the conclusion that a lot of people are suffering the same problems as us. So what does this mean? Either J2EE just isn’t built for performance, or most J2EE developers don’t know how to do the job correctly. Either way, it’s like giving people a rope to hang themselves with.

My opinion? If you want it fast, put it in the database. If you want a single location for business logic, regardless of the applications accessing it, put it in the database.

Cheers

Tim…

Security article, SQL/XML and my PC…

I wrote a summary of some of the recent security posts (Basic Security Measures for Oracle). If I’ve missed something out feel free to drop me a line.

I’ve been doing some SQL/XML again today. It’s really quite simple, but when I’m away from it for a while I manage to convince myself it’s going to be a pain. Well the XML generation was no problem, pity defining the XML Schema wasn’t as easy. It looks like I’m going to get to play with this a bit more in the next few days.

I’ve just bought another 1G of RAM for my machine at home. It makes playing DVDs at the same time as running Oracle10g on a VMware virtual machine much easier 🙂 In the next few days I should receive my NSLU2. After my recent Windows fiasco I decided to get a bit more storage and a NAS to connect them to. It seemed like a much better idea than plugging some disks into the back of my machines. Time will tell 🙂

Cheers

Tim…