I currently have a problem with a database instance that crashes when I access a proxy table from a iSeries System (DB2).
The Environment is Window 2008 R2 x64, SA 10.0.1.4239, iAccess for Windows V7R1(IBM ODBC Driver v13.00.01.00 Date 1/15/2010 CWBODBC.DLL)
The Software installer has installed a 64bit and a 32bit ODBC Driver. When I start the Database with the 32bit Database engine the System can access the remote table and returns a result set.
When started in 64bit mode a plain select against the proxy table
select * from eurinvx64
Crashes the database with an internal Server error after a couple of seconds. ISQL has already prepared the result set columns but I think this is done based on the locally stored proxy definition.
My knowledge of the iSeries environment is very limited. Does anybody know if a better 64bit ODBC Driver is available ?
I have tested first with the iSeries Software V6R1 but the behaviour was the same.
Any tips are welcome
It seems that there should be a specific 64-bit Microsoft Windows ODBC driver available for the iSeries database:
The ODBC architecture involves an application, driver manager, ODBC driver, and a data source. IBM i Access provides both a 32-bit and 64-bit ODBC driver. The 64-bit ODBC driver is automatically installed along with the 32-bit ODBC driver when running under a 64-bit version of Windows . ODBC applications running in 64-bit versions of Windows will automatically use the appropriate ODBC driver, depending on what bit version the application was compiled for. For example, the 64-bit driver can only be used by a 64-bit application.
Some follow-up questions:
answered 20 Sep '11, 12:00