LT,WT,ET,UV tables

I think you are talking about work tables (WT),Error Tables(ET),UV tables- (another
error table that stores data with uniqueness violations) and Log
Table(LT).Multiload uses these tables for processing the load operation into target
table

A log table maintains record of all checkpoints related to the load job, it is
essential/madatory to specify a log table in mload job. This table will be useful
in case you have a job abort or restart due to any reason.

Error tables store information related to the errors.There are two error tables
used by Multiload ET nd UV

Multiload operates in 5 phase initial,DML,Aquisition,Application and cleanup. after

intial and DML phases,It first populates the work tables in aquisition phase.The
data from source files is first populated into WT in aquisition phase and later on
applied to target tables in application.

You should note here that if a multiload job is successful all the above tables
will be automatically deleted/dropped by multiload in the cleanup phase.a
successful multiload job implies alll source rows from the file are applied
successfully to target table without any problem.however, when there is an abort
condition or error condition multiload would return an informative error message to
user and it does not delete any of the et,uv,wt,lt. A user is also not supposed to
delete these tables when there is a abort or error condition in middle of multiload
job.once the error is resolved, the user should restart his aborted or paused job
to run till completion.

If Iam not mistaken , there have been some job aborts in your case which were not
resolved, which is why you still have UV,ET,LT and WT tables left in your
database.Probably you might have renamed all these tables and started your jobs
afresh without resuming the previous aborted jobs.refer to the manual and take
appropriate steps to resolve the issue with left over et/uv/lt/wt tables.

regarding somesh's comments, its really awful to see people commenting on each
other.This forum is intended for knowledge sharing irrespective of members
skillsets.it is all about how we can help each other in making ourselves better in
Teradata skills.Anyways,appreciate members efforts to raise their doubts.I requewst
moderators to take necessary action on such personal comments.also i suggest
members to provide genuine feedback rather than providing vague responses like
'refer this thread', 'i think you are right/wrong','maybe i think
so','right',worng' etc., just to become a supreme being or just to show off their
presence in the forums.