It looks like this case: https://developer.teradata.com/tools/articles/teradata-utility-error-handling/teradata-utility-error... Has your error tables same name?
Restart after client failure
A Fastload job can be restarted after a client process failure. In this case the error tables and target tables must be in the state they were in when the failure occurred, therefore, a restart script must not in-clude the actions to drop error tables, drop target table and create target table. The following is an example of the restart script.
LOGON test/testuser,test; SET RECORD FORMATTED; DEFINE FILE=C:\DataIntegration\Data\tran1.dat; SHOW; BEGIN LOADING TEST.TRAN ERRORFILES TEST.TRANFLERR1, TEST.TRANFLERR2 CHECKPOINT 50000 INDICATORS; INSERT TEST.TRAN.*; END LOADING; LOGOFF;