DB2 7.x OLEDB Managed Provider Bug
-
A few years back, I had to use DB2 on AIX machine as the database for my ASP.NET 1.1 application. The provider had an interesting bug. When a Primary Key constraint is violated by inserting a duplicate record, it wouldn't throw a simple exception but an
ExecutionEngineExceptionwould get invoked. I came across the then forum post, one of my team members posted then over here (http://www.dbforums.com/archive/index.php/t-479734.html[^]) We also cross-checked this provider issue using ASP and it was just giving the message "Exceptions occured". Interestingly, the DB2 ODBC Driver works fine. I was just curious at least if the later versions of DB2 OLEDB Provider are free of this malady.Vasudevan Deepak Kumar Personal Homepage Tech Gossips
-
A few years back, I had to use DB2 on AIX machine as the database for my ASP.NET 1.1 application. The provider had an interesting bug. When a Primary Key constraint is violated by inserting a duplicate record, it wouldn't throw a simple exception but an
ExecutionEngineExceptionwould get invoked. I came across the then forum post, one of my team members posted then over here (http://www.dbforums.com/archive/index.php/t-479734.html[^]) We also cross-checked this provider issue using ASP and it was just giving the message "Exceptions occured". Interestingly, the DB2 ODBC Driver works fine. I was just curious at least if the later versions of DB2 OLEDB Provider are free of this malady.Vasudevan Deepak Kumar Personal Homepage Tech Gossips
We use a third-party managed provider from DataDirect[^] for connecting to DB2. If possible, prefer a native .NET provider to using an OLE DB provider through OleDbConnection or an ODBC driver through OdbcConnection. We looked at IBM's own managed provider but discovered it wasn't compatible with the customer's security settings (I forget the details, I think they were still using plaintext password authentication).
Stability. What an interesting concept. -- Chris Maunder
-
A few years back, I had to use DB2 on AIX machine as the database for my ASP.NET 1.1 application. The provider had an interesting bug. When a Primary Key constraint is violated by inserting a duplicate record, it wouldn't throw a simple exception but an
ExecutionEngineExceptionwould get invoked. I came across the then forum post, one of my team members posted then over here (http://www.dbforums.com/archive/index.php/t-479734.html[^]) We also cross-checked this provider issue using ASP and it was just giving the message "Exceptions occured". Interestingly, the DB2 ODBC Driver works fine. I was just curious at least if the later versions of DB2 OLEDB Provider are free of this malady.Vasudevan Deepak Kumar Personal Homepage Tech Gossips
As interesting as this is, is it really a Coding Horror? There's no code for us to gasp and recoil in fear from, then laugh shakily when we realise that we can see the wires.
Deja View - the feeling that you've seen this post before.
-
As interesting as this is, is it really a Coding Horror? There's no code for us to gasp and recoil in fear from, then laugh shakily when we realise that we can see the wires.
Deja View - the feeling that you've seen this post before.
Pete O`Hanlon wrote:
There's no code for us to gasp and recoil in fear from
It isn't a big deal. I have also given a situation where the provider crashes. A simple table with a Unique or Primary Key. A Console Application that tries to violate the primary key by inserting a duplicate value is enough to detonate the setup.:)
Vasudevan Deepak Kumar Personal Homepage Tech Gossips