Timestamp problem after upgrade DB2 ODBC Client from 7.x to 8.x

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

peesz - 10 Jan 2006 16:52 GMT

After upgrade ODBC Client from version 7.2 to 8.1 (FixPack 10) a have
problem with tables where primary key is set to timestamp filed.

In version 7.2 TIMESTAMP was mapped in MS Access as CHAR(26). Everything
worked OK.

In 8.1 (FP10) TIMESTAMP is mapped as DATE/TIME. I can't see tables with
timestamp primary key. In every field I see "#deleted".

I tried to setup patch2=24 and patch1=131072 but it doesn't work.

Have you got any experiance with that problem?
How to solve it?
Is it a DB2 Client bug?

Best Regards

Reply to this Message

juliane26 - 10 Jan 2006 18:11 GMT

This is -if you like to call it that way - an access bug, but actually
working as designed.
If you trace it, you will see that for some queries it actually
executes more than one database call.
so, if data changes between these calls, it will show it as #deleted.

At least that is what we found.

execute it as a native query and you should be fine.

Those patch settings usually helped, but I do not fully remember which
we did set, I think patch1=4 or 8 or so.

patch1=131072 and patch2=24 should be applied when still mapping to
char() in access (from what I can see)

Reply to this Message

peesz - 11 Jan 2006 16:18 GMT

> This is -if you like to call it that way - an access bug, but actually
> working as designed.

I know it's Access problem, but 7.2 Client works for me OK (map
TIMESTAMP as CHAR[26]).
I tried different configurations CLI parameters but id doesn't work..

Why they change in Client 8.2 logic for TIMESTAMP field?
Is there a way to change Client 8.2 to map TIMSTAMP as CHAR in MS Access?

Regards

Reply to this Message

peesz - 12 Jan 2006 10:17 GMT

I made some tests on Client 7.2 and 8.2.
The result is that Client 8.2 doesn't work switch Patch1=131072
(describe time stamps as a CHAR(26))

I think it's a ODBC Client 8.x bug!

Reply to this Message