Recently we created a new cognos 10.2.1 BI test environment. In production we run cognos BI 10.1.1. We use Data Manager 10.1 in production and installed 10.2.1 in the test environment. We use MS SQL 2008 R2 for our DW. We are extracting data from a DB2 ERP System. We moved over a copy of our prod sql db to the test environment. When we run a refresh for one of the tables we get
"DM-DBM-0400 UDA driver reported the following on connection SOURCE:
UDA-SQL-0144 An arithmetic exception was detected.
[IBM][iSeries Access ODBC Driver]Column 2: CWBNL0107 - Converted 12 bytes, 3 errors found beginning at offset 6
[IBM][iSeries Access ODBC Driver]Error in assignment."
Attached is the complete log. The only difference between the two environments is the version of Data Manager. They are both pointing to the same source DB2 ERP System. I don't get this message in the production environment when I refresh the same table. Other tables refresh without any issue in the test environment. Has anyone else ever experienced this behavior? Thank you in advance for any insight!
Quote from: gatorfe on 16 Dec 2014 03:39:18 PM
Recently we created a new cognos 10.2.1 BI test environment. In production we run cognos BI 10.1.1. We use Data Manager 10.1 in production and installed 10.2.1 in the test environment. We use MS SQL 2008 R2 for our DW. We are extracting data from a DB2 ERP System. We moved over a copy of our prod sql db to the test environment. When we run a refresh for one of the tables we get
"DM-DBM-0400 UDA driver reported the following on connection SOURCE:
UDA-SQL-0144 An arithmetic exception was detected.
[IBM][iSeries Access ODBC Driver]Column 2: CWBNL0107 - Converted 12 bytes, 3 errors found beginning at offset 6
[IBM][iSeries Access ODBC Driver]Error in assignment."
Attached is the complete log. The only difference between the two environments is the version of Data Manager. They are both pointing to the same source DB2 ERP System. I don't get this message in the production environment when I refresh the same table. Other tables refresh without any issue in the test environment. Has anyone else ever experienced this behavior? Thank you in advance for any insight!
Hi,
I'm pretty confident this has nothing to do with Data Manager or Data Manager versions. Looks like you're using ODBC to connect to DB2? My gut feel here is that the ODBC config is different on your test environment vs production. I suspect the ODBC config on Prod has been configured to permit unsupported characters without throwing an error, but this has not been done on your test server?
Does this technote help?
http://www-01.ibm.com/support/docview.wss?uid=swg21341271
Cheers!
MF.
Thank you for the article. All settings are the same in the odbc connections between test and prod servers. That includes the Allow unsupported characters.
We did not check both odbc.exe on the server. The one user syswo64 did not have the setting checked. thank you for your help!