In researching a client error, I came accross this discovery. We have
a 32-bit db2 client connecting to a 64-bit instance. Would that cause
a problem ? Here are the stats:
32-bit client
[ Process: 4812, Thread: 1016 ]
[ Date & Time: 02-06-2007 00:16:49.000003 ]
[ Product: QDB2/NT DB2 v8.1.5.449 ]
[ Level Identifier: 02060106 ]
[ CLI Driver Version: 08.01.0000 ]
[ Informational Tokens: "DB2 v8.1.5.449","s040212","WR21334","Fixpack
5" ]
This client connects to this database:
DB21085I Instance "db2inst1" uses "64" bits and DB2 code release
"SQL08024"
with level identifier "03050106".
Informational tokens are "DB2 v8.1.1.104", "s060120", "U805924", and
FixPak "11".
It seems that the calls to our database host wouldn't be utilizing
memory appropriately.
Anyone come accross this before?
Otto Carl Marte - 06 Feb 2007 11:23 GMT
I have not come across this problem, as I tend to keep my clients and
servers both on either 32 bits or 64 bits.
Its simple enough to update the client to 64 bits or as a last resort
the server instance (db2iupdt -w32 <instance name>).