Archives of the TeradataForum

Message Posted: Sun, 03 Feb 2008 @ 09:28:55 GMT

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

I've never seen this error before, but I thought the fourth possibility provided by the Messages manual was interesting:

This error occurs when an internal consistency check fails. The possible inconsistency are:

1) Session status not in order

2) MLoad phase status not in order

3) MLoad state status not in order

4) _Target table is in MLoad state but WorkTable is missing_

That scenario happens all the time at our site - people dropping work tables but not the log table and trying to restart after an error. Maybe the error tables must exist for this error to be thrown?

I'm with Victor - RELEASE MLOAD using BTEQ; drop the log, error, and work tables; run your script again.

- Chris

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