Question posted by: c.splittgerber@listec.de
(Guest)
on
July 23rd, 2008 08:25 AM
We have some trouble with C-written application and UDF on 64-bit
Windows ...
Given the following production environment:
- Windows 2003 Server on AMD64
- Microsoft C/C++ Compiler of Visual Studio 9.0 Express Edition (looks
like 32-bit only)
- DB2 V8.2 and multiple instances of DB2 V9.1 installed and running
After successfully compiling and linking (against 32-bit libraries of
DB2 V9.1) the application tblinfo (which can be found in DB2 c-
samples), running the program tblinfo.exe ends with SQL-error -1390:
DB2INSTANCE variable is not set.
We are pretty sure, that DB2INSTANCE is set to a valid DB2 V9.1
instance. Even calling "sqleatin" to attach to a DB2-instance ends
with SQL-error -1390.
What about the default DB2 installation instance, since DB2 V8.2 is
also installed on the server, the default DB2-instance cannot be
switched to any V9.1 instance.
Can anybody help us to fix that problem?
By the way, when running a copy of that tblinfo.exe on another Windows
2003 Server on AMD64 without a DB2 V8.2 instance, it runs perfect. And
it (the same tblinfo.exe) also runs perfect on Windows 32-bit Intel
computer.
But our final target is to deploy a C-written UDF on the above
described environment. Guess what happens ...
- UDF works perfect on Windows 32-bit Intel computer
- DB2 instance crashes with memory error on AMD64 computer when using
that UDF
What could be the reason for the instance crash with the UDF ...
- problem with DB2INSTANCE or default instance caused by DB2 V8.2 on
the same server
- problem caused by running a 32-bit DLL on a 64-bit environemt (a 32-
bit EXE runs on 64-bit)
Thanks for any comments.
