Object documentationLoader Log File Locate this document in the navigation structure


An important log function in Loader is to create and manage log files. The runtime behavior during export or import (execution of Loader commands) is always written to log file loader_<timestamp>.log or loader.log.


When you start Loader, the log file is created or updated.

  • Transport mode: Runtime behavior during export or import (execution of commands) is written to log file loader_<timestamp>.log. The time stamp shows when the package was executed. The time stamp of the first log file is identical to the name of the package package_timestamp (default of package name is the time stamp). If the package is used for further transformations, log files are created whose time stamps reflect the beginning of this transformation. This is no longer identical to the name of the package.

  • Command file mode and session mode: Runtime behavior within a single Loader session is written to log file loader.log, which is continuously updated. If another Loader session is opened at the same time, log file loader_<timestamp>.log is created and updated for this Loader session. The time stamp indicates when the additional Loader session was opened.

Storage of the Loader Log File

Operating Mode

Default Loader Log File Directory

Transport Mode

EXPORT directory: <loader_user_data>\packages\export\<database_computer>\<database_name>\<package_timestamp>

IMPORT directory: <loader_user_data>\packages\import\<database_computer>\<database_name>\<package_timestamp>

Session/Command File Mode


You can change the default for the log file directory of the current Loader session using the SET LOGFILEPATH command.

Example Example

Starting Loader in session mode


Information about the default Loader log file directory (Microsoft Windows)

Loader protocol: 'C:\Users\D019124\Documents\sdb\loader\log\loader.log'

End of the example.


In the log file you find all Loader commands required to open a session and to execute the required transformation (export, import or transport). All comments start on a new line with // * or // <letter>.

Special Comment Lines

// M

Line with messages; these are informative system messages, such as the number of lines inserted and rejected, last completed transaction.

// E

Line with error messages; this is used to introduce the two lines with the table and position values as well as the error number or error text for rejected lines.

// R

Line with REMARK comment; these are comments that the user specified using the REMARK command.


The log file is structured so that parts of it can be easily used to create a command file. In the log file, every command is saved together with information about the execution time, the number of objects for which actions were carried out, and any errors that occurred. However, the log file does not detail which individual actions were required to execute the command. If you would like this information, you can use the Loader syntax element package_spec to log activities in more detail (Additional Log Functions (package_spec)).

REMARK Command

You can use this Loader command to write comments in the log file.

Syntax Syntax

  1. <remark_command> ::=
      REMARK "<literal>"
End of the code.