The utility manager produces log records associated with
a number of DB2® utilities, including
the load utility.
The following log records mark the beginning or end of a specific
activity during a load operation:
- Setup phase
- Load Start. This log record signifies the beginning of a load
operation's setup phase.
- Commit log record. This log record signifies the successful completion
of the setup phase.
- Abort log record. This log record signifies the failure of the
setup phase. (Alternately, in a single partition database, if the
Load setup phase fails prior to physically modifying the table, it
will generate a Local Pending commit log record).
- Load phase
- Load Start. This log record signifies the beginning of a load
operation's load phase.
- Local Pending commit log record. This log record signifies the
successful completion of the load phase.
- Abort log record. This log record signifies the failure of the
load phase.
- Delete phase
- Load Delete Start. This log record is associated with the beginning
of the delete phase in a load operation. The delete phase is started
only if there are duplicate primary key values. During the delete
phase, each delete operation on a table record, or an index key, is
logged.
- Load Delete End. This log record is associated with the end of
the delete phase in a load operation. This delete phase is repeated
during the rollforward recovery of a successful load operation.
The following list outlines the log records that the load utility
creates depending on the size of the input data:
- Two log records are created for every table space extent allocated
or deleted by the utility in a DMS table space.
- One log record is created for every chunk of identity values consumed.
- Log records are created for every data row or index key deleted
during the delete phase of a load operation.
- Log records are created that maintain the integrity of the index
tree when performing a load operation with the ALLOW READ
ACCESS and INDEXING MODE INCREMENTAL options
specified. The number of records logged is considerably less than
a fully logged insertion into the index.