Archives of the TeradataForum
Message Posted: Sat, 28 Feb 2004 @ 15:20:59 GMT
The MultiLoad worktables can become quite large. This is due to the way it sends and matches the data to each SQL statement on the AMPs and the information it needs to guarantee a successful restart if a failure occurs. The best practice is to put the worktables in a work-type database that is different from you target table. Otherwise, you need enough space in the database to contain both the actual data and the work data until the table is finished being loaded.
So, you have two choices:
1. get your database administrator to MODIFY your database and add more space so you can resubmit and finish your MLOAD job. This of course assumes that you have enough available disk space to do this operation.
2. Assuming that you are still in the acquisition phase, RELEASE the MLOAD lock on the target table, drop your restart log, worktable, and error tables. Change your MLOAD script to create the worktables and error tables in a work database and rerun it.
So, that you are not required to have several production databases with a lot of extra space, you would be well advised to use option number two in all future loads.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|