![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am trying to log the row transform phase to a text file while running the copycolumn type for the phase. The problem is that if you set the row transform phase filter to copycolumn - I can't find a way to write out to the text file that they are there and what row they are working on. I have the transformation script for all the other phases writing to the same text file. But I can't set the row transform phase to use the transformation script if I set it to copycolumn. What is happening is that I have a progress database that I am trying to move to my Sql Server 2000 database. This will be done every night. The problem is that we have about 13 files that get errors from the Merant ODBC driver that says that some of the rows have a value exceeding its max length or precision. These fields are all x(1000). The program using the database doesn't seem to have a problem, so I assume there is a problem with the ODBC driver. It makes no sense about the error as I am reading the data not writing the data - so what has the length got to do with anything. I am trying to figure out which rows have these problems and by tracing each phase, I hope to figure out what the problem is. Thanks, Tom. |
#3
| |||
| |||
|
|
Does sound like a Driver problem. What happens if you set your fetch size to 1 and your insert size to 1. You then set your errors up high. By comparing then the rows you have in SQL Server with the rows in the Progress DB you can see the ones that come across. also in 2000 there is the opportunity to log failed rows to a text file (last tab DataPump task.) Try doing the import using and into MS Access. Does that work? |
![]() |
| Thread Tools | |
| Display Modes | |
| |