FastLoad Errors-rdbms Error 2634

Let's take a look at the following statement: BEGIN LOADING STU_FL
Errorfiles error_1, error_2; If the error_1 or error_2 table already exists at this time, the error will be as follows:

 
0008 BEGIN LOADING stu_fl
     ERRORFILES error_1, error_2;

**** 07:41:08 Number of FastLoad sessions requested = 4
**** 07:41:08 Number of FastLoad sessions connected = 2
**** 07:41:08 FDL4808 LOGON successful
**** 07:41:08 RDBMS error 2634: Existing ERROR table(s) or Incorrect use of stu_fl in  Fast Load operation.
**** 07:41:08 Delete the Error Tables or fix the BEGIN LOADING statement

Check out the manual, error code 2634 related information is as follows:

2634 Existing ERROR table (s) or incorrect use of%tvmid in Fast Load operation.Explanation:This error occurs if the Table/errortable (s) specified either;(a) existed before the start of the Fast Load, or(b) did not indicate the it is involved in this specificFast Load.Notes: This error means either, the user has referenced Existing tables for the errorfiles in a Fast LoadThat's not restarting, or that incorrect tabl Es were referenced in a restart of a Fast Load.Remedy:If This is a restart of a previous Fast Load,Delete the referenced error files. If This is a restart, correct the " Begin Loading Statement So" the error files are those specified for the orig Inal Fast Load. We can clearly see that the reason for this error is that we are in a fastload that is not restarting, errorfiles refers to a table that already exists.

Workaround:

Add the following statement before the FastLoad begins to delete the table specified by Errorfiles: drop table error_1; /* error table, internal to fast load utility needed to be defined */drop table error_2; /* error table, internal to fast load utility needed to be defined */

Summary:

BEGIN LOADING STU_FL

Errorfiles error_1, error_2; 1. In a fastload that is not restarting, if the Errorfiles specified table already exists, it will report 2634 of the error; 2. If the process of fastload is not wrong, error_1, error_2 is not automatically generated; 3. We can select * from error_1; view related error messages;