Page 1 of 1

Warning messages when running job in DS 8.0.1

Posted: Thu May 14, 2009 10:55 am
by arul
Hi,
I am getting some warning messages while running jobs (DS 8.0.1). This job contains webservices (WISD input and out stages, ODBC connector stages). DB is DB2.

LKP1: IIS-CONN-ODBC-000007 Error branding the ODBC driver

LKP1: IIS-CONN-DAAPI-000067 Schema reconciliation detected a size mismatch for field FIELD1. When moving data from source field type STRING(min=0,max=256,charset=ISO_8859-1:1987) into target field type STRING(min=0,max=255,charset=ISO_8859-1:1987), truncation, loss of precision or data corruption can occur. Use STRING(min=0,max=256,charset=ISO_8859-1:1987) for target type

LKP2: Schema field FIELD_DATE in input data set 0 not present in design time information. Extended field properties for this field will not be available.

LKP1:IIS-CONN-DAAPI-000063 Unable to determine association between statement parameters and table columns. The connector will not be able to obtain external schema and only limited schema reconciliation will be performed

It looks like a connection warning, but I am unable to find the cause. Pls suggest some remedies.

Any additional information will be helpful as we are new to this environment.

Thanks,
Arul

Posted: Thu May 14, 2009 1:42 pm
by mekrreddy
This can be the issue with ODBC data type support. Not all data types of db2 are supported in ODBC, if you can change the ODBC to DB2 client you can avoid warnings.

thanks

Posted: Fri May 15, 2009 11:52 am
by arul
Thanks.. will try that
mekrreddy wrote:This can be the issue with ODBC data type support. Not all data types of db2 are supported in ODBC, if you can change the ODBC to DB2 client you can avoid warnings.

Posted: Sat May 16, 2009 10:30 am
by asorrell
You might want to report this issue to your local IBM service provider and get it researched. It looks like there may be an issue with an ODBC call not setting a string length correctly.

It looks like the string being received has a max length of 256, and the target it is being sent to has a max length of 255. This may be a bug and should be reported to your service provider.

As an alternative - if you are not using the 5.3 ODBC drivers, then you might want to upgrade and try them to see if the problem is resolved.