We must remove the error tables before we re-run the same load job or it will terminate in an error condition.
Use RELEASE MLOAD tablename; statement if MLOAD doesn’t successfully completed and there is no desire to restart the MLOAD. This will return the target table to general availability. Error tables should be dropped manually, as RELASE MLOAD will not drop them automatically.
•TPUMP uses row hash locks thus allowing concurrent updates on the same table
•FastExport is used to export data from Teradata to the Host.
ERRORLEVEL (3807) SEVERITY 8;
Continuous updates results in more accurate, timely data. Tpump uses row hash locks than table level locks. This allows you to run queries while Tpump is running.
• End phase
For smaller table deletes, simple DELETE command is enough. Multiload delete is useful when the delete has to be performed on a large table in teradata.
Adding to the above, if from n"start record" and for n "stop record" are not mentioned, mload considers records from start till the end of the file
This restart logic is the reason that Fastload will not load duplicate rows into a MULTISET table. It assumes they are duplicates because of this logic. Fastload support Multiset table but does not support the duplicate rows. Multiset tables are tables that allow duplicate rows. When Fastload finds the duplicate rows it discards it. Fast Load can load data into multiset table but will not load the duplicate rows