Data Services with MySql Odbc on linux - weird results

dataservices job design
1

We are in the process of migrating from DI 11.7 to Data Services XI (3.2).
DS is running on 64bit redhat linux server. We have job that retrieves data from MySql source and inserts into oracle table ( template table ). The source has 500 rows. DI extracts 500 rows, but while inserting into Oracle table, it is nulling out 1 column in particular after inserting 250 records. We have ran this job 50+ times, always the same result. 1 column gets nulled out, even though the corresponding row has valid values in the source system.

we have installed the recomended 64bit mysql odbc driver ( ver: 3.51.22 ) but of no use.

Appreciate any and all help

Thanks.

bidi_user (BOB member since 2007-09-06)

2

can you check the value of following parameters in $LINK_DIR/bin/odbc.ini

Under MySQL ODBC DSN section

ODBC64SqlHandleSize=
ODBC64SqlLenSize=

manoj_d (BOB member since 2009-01-02)

3

Both are set as below:

ODBC64SqlHandleSize=64
ODBC64SqlLenSize=64

bidi_user (BOB member since 2007-09-06)

4

is the datatype of the column same in Database and Table Schema after importing to DataStore ?

manoj_d (BOB member since 2009-01-02)

5

Data Type is the same : Varchar

Mysql datatype is varchar(96)
oracle datatype is varchar2(100)

bidi_user (BOB member since 2007-09-06)

6

When i login into mysql database using mysql command line client and describe the table, it shows the column data type as VARCHAR(32) but in Data Services it displays as VARCHAR(96)

bidi_user (BOB member since 2007-09-06)

7

Hi all,

Only to register and help other people:

I had the same problem.

I saw the odbc.ini file and these lines were commented:

OdbcConformanceLevel = 3.0

ODBC64SqlHandleSize = 64

ODBC64SqlLenSize = 32

I removed the ‘#’ characteres and the problem was solved.

Regards,
Vinícius F.

ViniciusFossaluza :brazil: (BOB member since 2009-09-02)

8

same problem here running windows, with DS tripling up column widths.

had a ticket open on it, but sap couldnt reproduce it. :frowning:

jlynn73 :us: (BOB member since 2009-10-27)

9

My guess would be this is codepage related. Codepage of the database, codepage of the datastore? Would compare that with what support is using as settings.

Werner Daehn :de: (BOB member since 2004-12-17)

10

Anyone get an answer to this? (widths are tripled, in mysql) I am experiencing the same issue with DI 12.2 against MySQL 5.

dnewton :us: (BOB member since 2004-01-30)

11

what is the OS, is it 64-bit or 32-bit ?
what is the MySQL driver version ?

is the following parameter set in $LINK_DIR/odbc.ini file and to what value ?

ODBC64SqlHandleSize =
ODBC64SqlLenSize =

what is the version of UnixODBC ?

manoj_d (BOB member since 2009-01-02)

12

This is 32-bit DI running on 64-bit Windows 2008.

MyODBC windows odbc driver is version 5.1.

Where would that ODBC.INI file be on a Windows machine?

thanks much…

dnewton :us: (BOB member since 2004-01-30)

13

you don’t need ODBC.ini in windows, I think problem could be with the Driver version that you are using, check the PAR document, I think you will have to use MySQL 3.05

manoj_d (BOB member since 2009-01-02)