I have also faced this.
At that point the txt file would not have the file structure in the expected format.
Depends on the delimiter. you would have to find that line and provably cleanse.
Alternately if you use a splitter tool and split file in some 10 parts, you will find it easy to narrow down to the problem area.
Hope this helps.
I ran into a similar issue. I found special escape characters in my file that was killing it. The good news is that you know exactly where it failed in the file. So look at lines 30645 and 30646 with a good text editor that can view escape characters (Notepad++ or SciTE), and see if there is anything odd.
thanks for the suggestions.
I had a peek in Excel at that row .
Indeed there is a cell with this text
F├£R FORSCHUNG "
If I understood your comments right, it is the " causing problems; the character ├ , looking pretty odd, should be digested by QV?
EDIT: setup delimiter n the script is actually
delimiter is '\t'
so why is the " causing troubles? Shouldn't it be seen as a normal character?
A point which is more important.
Don't you think this is a huge pitfall of QV? Now I could spot this error because the delimiter character was luckily placed at the beginning of the source.
How about it happens close to the end, when 90% of records are loaded?
I would never notice that and QV would not warn me.
I see this as a severe pitfall.
actually, this appears to be the end of my load script
FROM [D:\MyDocs\Erik.Furlanis\My Documents\reMIN MAX\Oracle Source\0*-2013 Order Data.txt] (txt, utf8, embedded labels, delimiter is '\t', msq);
So, if I understood you rightly, that should have avoided for QV to get into troubles with the ".
But it did not!