The issue happens when using TPT 15.10 or 16.10 to load "formatted" files.
Couldn't understand what went wrong with TPT10508 error even after I cleaned up all files under $TWB_ROOT/checkpoint and $TWB_ROOT/logs directory. TPT jumped directly into "Application Phase", as if it tried to restart a job. But the job name is also appended with random number everytime.
Teradata Parallel Transporter Load Operator Version 16.10.00.01 $LOAD: private log specified: foo_test_load.log $FILE_READER: Instance 6 directing private log report to '_foo_test_filereader.log-6'. $FILE_READER: Instance 5 directing private log report to '_foo_test_filereader.log-5'. Teradata Parallel Transporter DataConnector Operator Version 16.10.00.01 $FILE_READER: Instance 4 directing private log report to '_foo_test_filereader.log-4'. $FILE_READER: Instance 1 directing private log report to '_foo_test_filereader.log-1'. $FILE_READER: Instance 8 directing private log report to '_foo_test_filereader.log-8'. $FILE_READER: Instance 3 directing private log report to '_foo_test_filereader.log-3'. $FILE_READER: Instance 2 directing private log report to '_foo_test_filereader.log-2'. $FILE_READER: Instance 7 directing private log report to '_foo_test_filereader.log-7'. $FILE_READER: DataConnector Producer operator Instances: 8 $FILE_READER: ECI operator ID: '$FILE_READER-15976' $LOAD: connecting sessions $FILE_READER: Operator instance 6 processing file '/mnt/n001/data/datacopy/foo_test/20171101/part-00008.10641401.teradata.gz'. $FILE_READER: Operator instance 1 processing file '/mnt/n001/data/datacopy/foo_test/20171101/part-00001.10642546.teradata.gz'. $FILE_READER: Operator instance 7 processing file '/mnt/n001/data/datacopy/foo_test/20171101/part-00003.10641460.teradata.gz'. $FILE_READER: Operator instance 8 processing file '/mnt/n001/data/datacopy/foo_test/20171101/part-00006.10642184.teradata.gz'. $FILE_READER: Operator instance 5 processing file '/mnt/n001/data/datacopy/foo_test/20171101/part-00009.10643137.teradata.gz'. $FILE_READER: Operator instance 2 processing file '/mnt/n001/data/datacopy/foo_test/20171101/part-00014.10641565.teradata.gz'. $FILE_READER: Operator instance 4 processing file '/mnt/n001/data/datacopy/foo_test/20171101/part-00015.10639367.teradata.gz'. $FILE_READER: Operator instance 3 processing file '/mnt/n001/data/datacopy/foo_test/20171101/part-00012.10638631.teradata.gz'. $LOAD: preparing target table $LOAD: entering Application Phase $LOAD: TPT10508: RDBMS error 3807: Object 'foo_test_LTT' does not exist. $LOAD: disconnecting sessions $FILE_READER: Total files processed: 0. $LOAD: Total processor time used = '0.173973 Second(s)' $LOAD: Start : Tue Nov 28 09:35:42 2017 $LOAD: End : Tue Nov 28 09:35:51 2017 Job step LOADING terminated (status 12) Job _foo_test-11280935.15777 terminated (status 12) Job start: Tue Nov 28 09:35:33 2017
The LOG table was actually not created during TPT, while ERROR and USER ERROR tables were created in the Teradata database.
I would need to see the script and the logs to get a better picture of what is going on.
BTW, we do not use $TWB_ROOT anymore. Haven't since 14.00 (or 14.10).
With 15.10.01 (and forwards) our installation and execution relies only on the PATH environment variables and our code will internally use relative paths from that location to get to the files and directories we need.
Even though you cleaned up the checkpoint files (no need to cleanup the logs just to start or resume a TPT job), you did not clean up the restart log table that resides on the Teradata Database.