Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mdhingra01
Posting Yak Master
179 Posts |
 Posted - 2004-11-10 : 09:40:40
|
| I am running a dts package thta is taking data from a SQL SERVER table and loading it into a DB2 Table. The process craps out. The error is:Error Source: IBM OLE DB Provider for DB2 ServersError Description: The number of failing rows exceeds tje maximum specified. CLI0109E String data right truncation. SQLSTATE=22001Is there way to see the failing records. DOes SQL Server write these entries to a table or log file that can be viewed. If not, is there a way to set up a log file that will track the transactions that fail?Thanks |
|
|
AndyB13
Aged Yak Warrior
583 Posts |
Posted - 2004-11-10 : 10:58:38
|
| Check your field data lengths on the DB2 table that they are the same or at least greater than the SQL DBThis will throw the same error (different number - 22001 SQLSTATE = 8152 SQL Server Error)CREATE TABLE #MyTemp (myColumn varchar(5))INSERT #MyTemp (myColumn) --SUCCESSVALUES ('12345')INSERT #MyTemp (myColumn) --ERRORVALUES ('123456')DROP TABLE #MyTempAndy |
 |
|
|
mdhingra01
Posting Yak Master
179 Posts |
Posted - 2004-11-10 : 13:21:15
|
| Thanks Andy. Field widths are identical and data types are the same. I found some special characters that are causing it to fail. The data in the SQL table is coming from a data dump in EBCDIC, versus SQL server interpreting the data in ASCII. I think there is a lost in translation in the import of the raw data and when I try to export it back out to DB2, then it can't handle the special characters. I need to now find a easy way to locate and update all special characters in the data. Anyone know any ways??? |
|
|
|
|
|
|
Log file