The following table describes the things to consider when using the END LOADING command.
|End Loading Phase||The END LOADING command begins the end loading phase of a Teradata FastLoad job. During this phase, all rows are distributed on the AMPs and stored in the final Teradata FastLoad table.
When the end loading phase completes, the database removes the access locks that were placed on the three tables specified in the BEGIN LOADING command so users with the proper privileges can access them using Teradata SQL statements.
|Entering Teradata SQL Statements||Many of the Teradata SQL statements from Teradata FastLoad cannot be entered because the utility supports only a subset of the Teradata SQL language. So, when END LOADING has completed and access to data stored in the Teradata FastLoad table or the error tables is required, it cannot be done from Teradata FastLoad. You must use BTEQ or a similar application program must be used to query these tables.|
|Error Tables||Teradata FastLoad automatically drops error tables that contain no rows when END LOADING finishes executing.|
|Internal Checkpointing||The database uses internal checkpointing while processing an END LOADING command. Therefore, a job can be interrupted during the end loading phase without disturbing processing status. When the job is restarted, the database resumes processing from where it left off.|