Hi And Welcome Aboard ,
DS is still 32Bit application (except Itanium processors on HP which has 64Bit version), therefor in order to have it interact with 64Bit DB you need a 32Bit client to connect to your DB.
Usually there is a version for 32Bit or one that supports both 64Bit and 32Bit applications.
You'll have to check if one exists for your configuration.
You might want to check future releases of 64Bit DS application availability options with your support.
IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.
Our situation:
- Upgrading to a 64-bit DB2 database and 64-bit DB2 client (but the directories for 32-bit are also installed)
- AIX 5.2 operating system
- Datastage PX 7.5
We have datastage jobs that:
- read and write to DB2 tables
- call unix scripts that use DB2 CLI command line statements (eg. "db2 connect to zzz").
The problem:
- We can get Datastage working with DB2 by changing the LIBPATH to point to the 32-bit library. We also change the PATH to use the 32-bit bin. However, the "db2 connect to" statement times out before it connects.
It seems like we cannot have a situation that allows us to use Datastage AND use the CLI.
Options we're considering:
- Write a "wrapper" for the unix scripts called by Datastage, to change the PATH and LIBPATH to point to the 64-bit DB2 directories. It's more of a kludge than an elegant solution. It also worries me that by "tricking" the system to use 32-bit, things may fall in a heap if there are any unexpected 64-bit function calls.
- Install another DB2 instance that is 32-bit (to be used by Datastage), and remotely use the 64-bit instance, which requires some fiddling with the unix scripts and database binding, and complicates the configuration.
Has anyone got a solution to this issue, or can they suggest other options?
We are using DB2 V8.2 64-bit (on AIX 5.2 64-bit), and DataStage EE 7.5. I know we ran into all sorts of issues when we converted, but I'll need to get back to you on what they were.
However, and most importantly, we did get it working with no wierd work arounds. No wrappers needed.
Currently the database is on the same server as Datastage, ie. local.
Another 32-bit application (that uses the DB2 client) has problems accessing the 64-bit database, so it sounds like it's a DB2 issue. We have referred it to our friendly DBA's to also seek a solution. I'll keep you posted.
The DB2 guys suggested:
- Installing a 32-bit DB2 instance, and remotely use the 64-bit instance.
We didn't really want to do that, so for now we've gone with the "kludge" in the called unix script that changes the LIBPATH and PATH to point to the 64-bit directories, just prior to running the "db2" command.
Gazelle wrote:The DB2 guys suggested:
- Installing a 32-bit DB2 instance, and remotely use the 64-bit instance.
We didn't really want to do that, so for now we've gone with the "kludge" in the called unix script that changes the LIBPATH and PATH to point to the 64-bit directories, just prior to running the "db2" command.
Hi i'm getting the similar kind of error , when connecting to DB2 64-bit instance.
Currently the LD_LIBRARY_PATH has this value which points to 64 bit lib.
/IBMdb2/home/db2rtcl/sqllib/lib64:/opt/IBMdb2/V8.1/lib64
But should the PATH variable also needs a change ? And if could you specify them also ?
,
