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

ADO.Net Application compatibility between fix pack lvl on build PC and fix pack lvl on deploy target

P: n/a
Hi all,

I have come across an issue that appears to relate to APAR IY76615:

IY76615 CONNECTION WITH .NET DATA PROVIDER MAY FAIL WHEN UPGRADING TO
DB2 V8 FP10

This is documented as having been fixed in fix pack 11. We upgraded the
deployment target from fixpack 9 to fixpack 10 and got connection
errors with our ASP.Net app. I'll post a response once I determine if
FP 11 or 12 resolves this issue.

Another possible cause of the above error is a compatibility issue
between a the fix pack level on the build PC and the fix pack level on
the deployment target. The application was built in this case on a
workstation using V8.1 fix pack 8.

So my question is are there any circumstances when the fix pack level
on a build PC must match the fix pack level on the deployment target?
If there is leeway, how much leeway is there? I'm aware this kind of
thing has never been a problem with the other APIs DB2 caters for, but
I need to make sure.

The way I see it is if the IBM.Data.DB2 assembly version hasn't
changed, then underlying driver compatibility should not have been
broken. Is the case? In the above case the assembly version is the same
at 8.1.2.1.

Regards,
Christian

Oct 11 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
>
This is documented as having been fixed in fix pack 11. We upgraded the
deployment target from fixpack 9 to fixpack 10 and got connection
errors with our ASP.Net app. I'll post a response once I determine if
FP 11 or 12 resolves this issue.
As an update to this, more information is at the following link:

http://www-1.ibm.com/support/docview...id=swg1IY76615

We have gone with this option.

Christian.

Oct 16 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.