Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
X002548
Not Just a Number
15586 Posts |
 Posted - 2009-09-29 : 09:20:32
|
Don't know where to put this, so...We upgraded an app to SQL 2k5 from 2000. It uses web sphere and JDBC. Everything works fine on 2000.Now however, we are getting error messages when a sproc(s) are being called...I'll have to dig it up...but here is IBM's response...which floored me...I took out the Transaction out of a sproc and it still is failing....is she completely blowing smoke?Anything I've EVER built (Oracle, DB@, SQL Server 6.x-2005) manages the transactions in the sprocs...what if you need nested transactions? (I've never have done that though)...Please read the response below:quote:
It looks like you are beginning and committing transactions via SQL within your stored procedures. The DataDirect Connect for JDBC driver has never supported this type of behavior on the grounds that in JDBC, transaction management must always be done through the JDBC driver. However, in older versions of their driver, they (DataDirect) did nothing to prevent this sort of misuse. But in more recent versions of the DataDirect Connect for JDBC driver, their code is designed such that these types of transactions unknown to the JDBC driver will cause errors. This issue has previously been escalated to DataDirect, and they have stated it is impossible (and contrary to the JDBC specification) to reverse their behavior. Our first recommendation is to remove all transactions from the stored procedures and always use JDBC for transactions instead. If you are unable (or unwilling) to do this, and the best workaround that we can offer is to provide you with a backlevel DataDirect Connect for JDBC driver, that is prior to when DataDirect changed their code, which is what the IBM link that you referenced in your email is for). We should emphasize that even when using the backlevel driver, the usage of transactions inside of stored procedures is still considered unsupported by DataDirect Technologies, and so you would be doing this at your own risk as we would be unable to get any fixes from DataDirect in this scenario. I believe you would have to have a pre-6.1.0.15 level to get the older DataDirect driver out of the fixpacks, since I believe it was changed in 6.1.0.15 (hence the 6.1.0.17 level didn't work for you). If needed, I can work with the team to get you the back-level driver if you want to go that route either temporarily (while you make the changes required in your app) or permanently (but remember doing so is pretty much unsupported by DataDirect). Kind Regards, SusanSusan M. HansonService Release Architect, WebSphere Application Server
Brett8-)Hint: Want your questions answered fast? Follow the direction in this linkhttp://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspxAdd yourself!http://www.frappr.com/sqlteam |
|
|
X002548
Not Just a Number
15586 Posts |
|
|
X002548
Not Just a Number
15586 Posts |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2009-09-30 : 15:45:29
|
| Great...so all it was, was that a sproc had 2 result sets, that the front end didn't know about, and didn't manage, and the new jdbc driver was "fixed" to through an error that the developer wasn't aware ofIt had nothing to do with transactions in sql serverBrett8-)Hint: Want your questions answered fast? Follow the direction in this linkhttp://weblogs.sqlteam.com/brettk/archive/2005/05/25/5276.aspxAdd yourself!http://www.frappr.com/sqlteam |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
|
|
JDBC Driver