It's not a secret anymore!
The moose likes JDBC and Relational Databases and the fly likes Migrating a project from Oracle 8i to 10g Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "Migrating a project from Oracle 8i to 10g" Watch "Migrating a project from Oracle 8i to 10g" New topic

Migrating a project from Oracle 8i to 10g

Bhavani Kumar

Joined: Feb 22, 2005
Posts: 15
Hi All,
I have a J2EE web project which runs on WAS and has Oracle 8i as the database. Now we are considering to upgrade the DB from 8i to 10g.

I would like to know what are the steps that need to be taken care of from the front end (java code) so that the project runs similar to how it used to run with 8i.
Paul Sturrock

Joined: Apr 14, 2004
Posts: 10336

Nothing should need changed beyond the JDBC url and the version of the driver.

Not an advanced question. Moving...
[ March 02, 2007: Message edited by: Paul Sturrock ]

JavaRanch FAQ HowToAskQuestionsOnJavaRanch
Purushoth Thambu
Ranch Hand

Joined: May 24, 2003
Posts: 425
You need not be concerned about upgrade unless you are DBA. It will be DBA's responsibility to properly configure 10g but as a developer you may have to do some regression testing on load/performance. If you know bit about the DB then you can look at the 8i & 10g configuration for DB mode, SGA size, max open cursor size, max connection and stuff like that. If you are java developer then noticeable difference is the 8i JDBC driver "oracle.jdbc.driver.OracleDriver" has been deprecated, in 10g drivers so you have to use "oracle.jdbc.OracleDriver"

It's definitely worth to take a look at the Oracle JDBC FAQ
Scott Selikoff
Saloon Keeper

Joined: Oct 23, 2005
Posts: 3753

Upgrading has the potential to completely break your code. That being said, there's really no way to know what will break and what won't without actual testing. What you normally do in a situation like this is perform the upgrade on a test system then perform a full set of system tests.

Its not the JDBC that is 'as likely' to fail but any stored procedurs, triggers, views, etc that your code depends on may stop functioning all together on an upgrade. I've seen upgrades from Oracle 9 to 10 that crashed JDBC code due to some dependence on a problematic function call in a stored procedure. For the most part, you just test it out on a copy of your database, figure out the issues, and if everything goes well, upgrade the real database. Last I checked Oracle lets you download developer versions of 10 for free so getting the software is easy enough.

[OCA 8 Book] [Blog]
I agree. Here's the link:
subject: Migrating a project from Oracle 8i to 10g
It's not a secret anymore!