FASTLOAD Command 

Syntax

<fastload_statement> ::=
FASTLOAD [
<usage_spec>] TABLE <table_spec> <load_column_spec_mlt> <infile_spec>

FASTLOAD with 100 % USAGE
TABLE customer
  cno 1
  surname 2
  zip 3
  place 4
INFILE 'customer.data'

Use

You use this command for loading data to load external data into the tables of a database instance.

FASTLOAD command files are processed while the database is running.

 

When data is loaded with FASTLOAD, it is entered directly in the pages on the database instance. This command loads data more quickly than the DATALOAD command. However, because it does not write any log entries, you must back up the new data after you have loaded it. You can back up either the relevant pages (incremental data backup) or the entire data volume. The table is write-protected until you have backed up the new data. See: Database Manager GUI: SAP DB 7.3, section Data Backup

Prerequisites

Process Flow

When a FASTLOAD command is started, the target table of the load operation in the database instance is locked so other users cannot write to it. The target table can still be read, however.

Unrestricted reading and writing is possible in all other tables.

Once a FASTLOAD command has been processed, other write operations triggered with FASTLOAD from the same user can be performed on this table. Once the load operation with FASTLOAD has been completed, all users only have read access for the table.

A backup of the database instance must be created before it is released again for write operations from other users.

Result

The data in the source table has been loaded to the target table.

The REPM Server uses an implicit COMMIT to complete the data load successfully.

Errors

If a FASTLOAD load operation is aborted, all of the lines transferred during the operation are deleted. Data that existed in the table before the FASTLOAD load operation was started remains unchanged.

If you cancel the load operation because the Replication Manager refused to transfer certain lines, you can check the log file of the Replication Manager to find the data record that caused the operation to fail.