By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,282 Members | 1,617 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,282 IT Pros & Developers. It's quick & easy.

Upgrade IBM DB2 7.2 to 8.2 - Issues with Autocommit

P: 1
Hello there,
I am impressed with the questions and answers in this forums and belive this group will help me thru my issues.

We are currently upgrading our application hardware. Ours is VB application(client) and that connects thru DCOMS and IBM DB2 connect 7.2 (on a win 2000 server) to backend DB2 database (7.2, due for upgrade) and triggers stored procs on the backend.

We were asked to move the middleware server to windows 2003.

I got a VB programeer to get the new VB application build with new middleware server IP and got the new DCOMS installed and running on the new server,

Also got the new IBM DB2 connect 8.2 enterprise edition and didnt the database setup. I tested the connection and even stored procs from dev centre.

When our application was tested, we got 'Invalid Cursor open' error and we set autocommit to 0 (No)

The application seem to work but has serious issues. Its not commiting any change that we do.

for example, when we request a new remmitance from database, it return a new number. when we do this next time, I brings in the same number, but the backend stored proc usually give the number and increment the table value by 1 for next use.

I am not sure how to fix this. There is no commits in the storedproc.

I checked the old setup using on win 2000 server, and there is autocommit was not disabled..

I am a novice in this area and apolgies if my explaination is confusing....

any help on setting up the DB2 connet would be appriciated....

Oct 23 '06 #1
Share this question for a faster answer!
Share on Google+

Post your reply

Sign in to post your reply or Sign up for a free account.