Steve Rainbird wrote:
> <snip>>
>>
>> BTW in case it matters we are currently using DB2 Express-C.
>>
>> --
>> Steve
>>
>>
>>
>
> Looks like this may be the problem. The machine the 64bit database is on
> has 6GB memory. DB2 Express-C has limit of 4GB I believe.
>
>

Not entirely sure about that.
I'm running an Express-C on a 64bit server with 16GB memory.
Ofc it only uses 4GB at the moment. (It's a failover machine for when
our WSUE machine goes offline. It's running a testenvironment on
express-C and when our pri. machine explodes, we can reinstall the
failover machine to run the WSUE. Financial matter, in case anyone is
wondering why the *** we're running an express-c on a 64bit machine).

In our production environment, we're using an 64bit linux db2 WSUE
machine using 16GB memory. Our clients are 32bit linux machines running
the db2 client. So we're using 32bit clients to connect to a 64bit db
server.

In our test environment, we're using an 64bit linux with 16GB running
db2 express-C to which 32bit linux machines running the db2 client are
connecting.

So I think, at least at one point, we have a very similar situation to
yours, and it works without a hassle. We even have 32bit windows
machines connecting to our test environment using QUEST and DB2CC.

What kind of errors do you get?

Regards, Jurgen.