So your suggestion worked great. Streaming out into multiple files works awesome.
Now the next challenge is exporting multiple tables in parallel using separate scripts. Running into issues with that.
Let's say I have table1 and table2, and export_Table1 and export_Table2 scripts.
I kick off export_Table1, and in a separate session i kick off export_Table2 script. The second script outputs
Found CheckPoint file: /opt/teradata/client/16.00/tbuild/checkpoint/ec2-userLVCP
This is a restart job; it restarts at step export_to_file.
and attempts to export table2. Is there a way around this behavior? I can obviously run these on separate EC2 instances, or have multiple installations of Teradata client on the same machine, but is there a way to indicate that this is NOT a restart of another export?
Are you providing a unique job name to each job?
Use the -j command line option.
Otherwise all jobs will try to use your logon id and your jobs might step on each other.