Right now we're currently planning to upgrade our oracle database from 9i Enterprise to 11g Standard. We were asked to asses if this upgrade would have any impact on our current java applications. Its an upgrade to a higher version of oracle but to a Standard edition. I actually got hold of a table which lists the detailed differences between Standard and Enterprise editions and most of them I am not familiar with since I'm not really a database guy.
The critical function I can see that I think might be affected by this upgrade is the use of message queueing (JMS). We basically make use of the Spring Framework's JMS capability. Do you think this would be affected when we upgrade our database from 9i Enterprise to 11g Standard?
I initially taught this should be posted in the Database forum but since I want to know if the use of Spring JMS would be affected by it, I placed it here. Any help would be appreciated.
I guess it depends on how you're using JMS--if messages are persisted in the database I suppose it's possible. Without the reference material you're referring to, or any information regarding your JMS setup, I don't see any way to help, though.
Normally JMS would be affected only by whatever you're using to implement JMS (usually a JEE container or library like ActiveMQ).
Joined: Aug 11, 2005
David Newton wrote:I Without the reference material you're referring to, or any information regarding your JMS setup, I don't see any way to help, though.
Thanks for the help David. Here's a link to our Spring-context.xml file. I removed some parts though.
My answer is the same--I suppose it's possible. Since (I think?) you're persisting JMS messages in the DB, a DB change could potentially affect JMS operations. *Would* it? Meh--I don't know. I doubt it. Can't you just test it?
subject: Database Upgrade and Spring Framework's JMS capability