Archives of the TeradataForum

Message Posted: Wed, 14 Dec 2005 @ 14:26:11 GMT

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

Jebaseelan:

I am not sure where your confusion comes from, but my guess is that you do not know the actual layout of your input file. Your self-defining INSERT tells Fastload the every single field in your record is the exact same data type and in the exact same location as it is in the table. From your error, this is not the case.

Fix your DEFINE to include the actual field data types and rewrite your INSERT with the :<field name> in the VALUES and it should work just fine. It appears, with a difference of 1911 bytes, as though your data coming in might be in CHAR but it is not CHAR in the table. It isn't magic. You have to tell Fastload the truth, the whole truth and nothing but the truth about the data coming to it in order for it to work.

Mostly you can only use the self-defining INSERT when you have used something like FastExport or BTEQ to unload a Teradata table.

Hope this gets you on the right path.

Michael Larkins
Certified Teradata Master
Certified Teradata SQL Instructor

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