At each check point there will be an entry made in SYSADMIN.FASTLOG table.In your case the fast load will resume loading from the first row following the last successful check point(50,000) i.e. 50,001.This is during data aquisition phase.If it is interrupted in the application phase just resubmit the fast load script with only BEGIN and END loading statements.
You can also perform a manual restart using RECORD command say (RECORD 60,001) assuming the last check point as 60,000 from SYSADMIN.FASTLOG table.This will skip first 60,000 records and start from 60,001.
The DBS will always eliminate the duplicate rows from SET and MULTISET tables for FastLoad jobs. In other words, on a FastLoad job, you can send duplicate rows to the Teradata database, but the database will discard them.
The Teradata database will not discard duplicate rows being sent from MultiLoad jobs when MultiLoad is loading a MULTISET table.
These are DBS rules, not client utility rules.
FastLoad will not load duplicate data in both SET and Multi-Set Table is perfectly understandable..
But what would happen if the Target Table is a NOPI table?
does the rule is still applicable?
if so how is it implemented?
FastLoad can load duplicate rows into NoPI tables.
Normally, the DBS throws away duplicates during the sort (in the Application Phase).
NoPI tables are always MULTISET tables, but since there is no sort on NoPI tables, duplicate rows are not discarded by the DBS.
While loading a empty table using Fload, in Acquisition Phase (Phase 1) getting database full error, later i added some more space to the database. Now what can be done complete the load process? whether resubmitting the script is enough or something has to be specified in Begin Loading command?
It is correct, resubmit the job is just enough. Make sure that the Error tables and the target tables are untouched (i.e. no drop Error Tables, or recreate the taget table).