Problem with DB2 and ADO 2.8 ?

This is a discussion on Problem with DB2 and ADO 2.8 ? within the db2-udb forums in Other Databases category; I had a test machine with ADO 2.7. We use ADO/ODBC/DB2 Connect v8.1.9 up to a mainframe. Never had a problem. We have build machines upgrading to XP and ADO 2.8 so I wanted to test upgrading to ADO 2.8.1 on my test machine. Now when I run the Application and get to a point that runs a query in a COM+ transactional component (even SELECT statement), I get the following error. IBM][CLI Driver][DB2] SQL0998N Error occurred during transaction or heuristic processing. Reason Code = 16 . Subcode = 3-8004D00E . SQLSTATE=58005 ...

Go Back   Database Forum > Other Databases > db2-udb

Database Forums

Register FAQ Calendar Search Today's Posts Mark Forums Read
  #1  
Old 01-09-2006, 12:15 PM
Default Problem with DB2 and ADO 2.8 ?

I had a test machine with ADO 2.7.

We use ADO/ODBC/DB2 Connect v8.1.9 up to a mainframe. Never had a problem.

We have build machines upgrading to XP and ADO 2.8 so I wanted to test
upgrading to ADO 2.8.1 on my test machine.

Now when I run the Application and get to a point that runs a query in a COM+
transactional component (even SELECT statement), I get the following error.

IBM][CLI Driver][DB2] SQL0998N Error occurred during transaction or
heuristic processing. Reason Code = "16". Subcode = "3-8004D00E".
SQLSTATE=58005


I am wondering if ADO 2.8 changed some security somewhere that is causing this?

--
Thanks,

Dave

Reply With Quote
  #2  
Old 01-09-2006, 06:39 PM
Default Solution

http://publib.boulder.ibm.com/infoce...db2l0/duow.htm



If the MTS COM objects use ADO to access the database, you must turn off the OLEDB resource pooling so that the Microsoft OLEDB provider for ODBC (MSDASQL) will not interfere with ODBC connection pooling. This feature was initialized to OFF in ADO 2.0, but is initialized to ON in ADO 2.1. To turn OLEDB resource polling off, copy the following lines into a file called oledb.reg, save it as a plain text file, and issue the command oledb.reg. The Windows operating system will import this registry setting.

REGEDIT4

[HKEY_CLASSES_ROOT\CLSID\{c8b522cb-5cf3-11ce-ade5-00aa0044773d}]
@="MSDASQL"
"OLEDB_SERVICES"=dword:fffffffc


Reusing ODBC Connections Between COM Objects Participating in the Same Transaction
ODBC connections in MTS COM objects have connection pooling turned on automatically (whether or not the COM object is transactional).

For multiple MTS COM objects participating in the same transaction, the connection can be reused between two or more COM objects in the following manner.


Reply With Quote
Reply


Thread Tools
Display Modes



All times are GMT -4. The time now is 05:34 AM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Integrated by bbpixel2009 :: jvbPlugin R1013.368.1

Search Engine Friendly URLs by vBSEO 3.1.0
vB Ad Management by =RedTyger=
In an effort to better serve ads to our visitors, cookies are used on Mydatabasesupport.com. For more information, check out our Privacy Policy.