Archives of the TeradataForum

Message Posted: Tue, 29 Dec 2009 @ 09:13:43 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

I've read the whole thread, again, and noticed you had the same issue with random samples of 50 rows as well, so it would appear that the missing records are not consequence of some limits on the number of rows or file size.

Did you try to run similar reports on other tables? Is the issue specific to this particular table?

If it is a bug it is difficult to imagine it would be generic. BTEQ is one of the most used utilities, both in automated batches and interactive use.

It can export and import data so many QA tests would try to import the data and would notice missing columns or records quite easily. So, it is necessary to understand something about the scope of your issue. Try different tables. Try different data types. For example, numbers only. Try to run the reporton small set of data the quality of which causes no doubt.

The data in the table you are looking at might contain some formatting non-printable characters causing the problem. Entire table can get corrupted in some rare cases etc.

Last but not least, check the quality of the installation of your Teradata client. The simplest check to start with would be to ask a colleague of yours to run the same report from his/her client.

I am afraid without extra information of this kind it would be difficult to suggest anything. I had a quick look in the Archives of this Forum (they go back for almost ten years) but could not find anything similar. It looks like this is a new case.

It would be interesting if you could localize the case and then zoom in on the details.

Victor

	<Prev	Next>		<<First	<Prev	Next>	Last>>