Comments on: Worst practices when using Oracle JDBC Drivers – great presentation by Douglas Surber

By: Joe

Joe — Tue, 07 Aug 2007 16:05:53 +0000

7.1.6 won’t work really well imo.
Good stuffs !

By: oranus

oranus — Sat, 27 Jan 2007 14:15:56 +0000

I’m an author of ETL product and Oracle is the only JDBC driver which caused redesign of my application JDBC access layer.
When I evaluate sources of other projects I always see the comments like this:
Some driver’s( guess who? – Ora…) throw exception here!!!

Regarding the statement cache. My project also use it because not all JDBC drivers support this feature. But my statement cache is configurable and can be replaced with a native driver solution. But I’m not sure if Oracle driver implements caching correctly

By: Ames Tiedeman

Ames Tiedeman — Mon, 30 Oct 2006 15:13:49 +0000

Will ORCL wipe RHAT off the map now?
Will customers chose Oracle as the vendor of choice?

Comments?

By: llanerobass

llanerobass — Sun, 29 Oct 2006 19:04:39 +0000

Seems to be impossible: upgrading Oracle is out of the budget for my client

By: Marco Gralike

Marco Gralike — Sun, 29 Oct 2006 13:37:47 +0000

@llanerobass

You should at least upgrade to 7.3.4. Oracle 7.2 and 8.0 were the worse Oracle releases I worked with. Oracle 7.2 was also very quick replaced by version Oracle 7.3.

Oracle 7.2 is the version that marked the first SQL*Net V2(.1) drivers coming into existance and was backwards compatible with SQL*Net version 1.

So I can imagine that you will have problems with the OCI calls. The 7.3 version was compatible with the first Oracle 8 SQL*Net drivers ( SQL*Net version 2.2) so you would have a far better chance that this version would work against your JDBC drivers.

By: llanerobass

llanerobass — Thu, 26 Oct 2006 17:39:33 +0000

If you try to connect to an Oracle 7.2.3 DB using the newest version of the JDBC drivers, you’ll get an ORA-01010 error: “invalid OCI operation”.

By: llanerobass

llanerobass — Thu, 26 Oct 2006 15:28:34 +0000

And what about Oracle 7.2.3 & Oracle 7.1.6 versions? I’ve been trying to use the lastest Oracle JDBC drivers over those versions and it fails… Even worst, I need to use JDBC over two different Oracle DBs: a 9i DB and a 7.2.3 DB (the lastest Oracle JDBC driver do not work over the 7.2.3 DB so I needed to load dynamically two versions of the Oracle JDBC driver… What a thing to do!)

By: Jan Kettenis

Jan Kettenis — Thu, 26 Oct 2006 13:46:14 +0000

Could you be more specific with point 9. It is not clear if the first or second alternative is the best. I read that you should not use the first but the second or last instead, of which the last is not preferred because of performance.

By: JJ Walker

JJ Walker — Wed, 25 Oct 2006 21:07:03 +0000

You seem to be switching between what to do and what not to do on each of these. Very confusing. You need to be more consistent or people will end up doing the wrong things.

For example, number 10 is phrased as a bad practice. Number 1. says “Do not use your own statement cache”. So you are saying it’s a bad practice to not use my own statement cache? That’s not what the description says.

WTF?

By: Lucas Jellema

Lucas Jellema — Wed, 25 Oct 2006 18:28:45 +0000

Dear Anonymous,

Thanks for your contribution to this discussion, I am sure. However, I would like to ask two things of you:

- could you please add your name to your contribution? If you feel inclined to making such strong statements, at least have the courtesy to make yourself be known
- could you please substantiate your comments on the Oracle JDBC drivers? I am not saying you are wrong in the statements you are making – though I by no means support them – but I feel that some prove or corroborating sources would be in order. So please write another comment in which you go into more detail about your personal experiences with the Oracle JDBC drivers that have made you voice your opinion.

I am afraid that anonymous comments are not the way to go on our weblog. If you for whatever reason choose to not come forward, I will have to remove your comment from the blog.

best regards,

Lucas