Log File (SAP Library

Log File

Definition

One important log function of the Loader is to create and manage a log file. Runtime behavior during export or import (that is, the execution of the commands) is in each case logged into the log file loader_<timestamp>.log or loader.log.

Use

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

● Transport mode: Runtime behavior during export or import (that is, the execution of the commands) is logged into the log file loader_<timestamp>.log. The time stamp enables you to see when the package was executed. The time stamp of the first log file is identical with the name of the package package_timestamp (default is the time stamp as name). If the package is used for further transformations, log files are created whose time stamps reflect the beginning of this transformation, and which are therefore no longer identical with the name of the package.

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

Storage of the Log Files

Operating Mode

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>

Example for EXPORT directory:

C:\transport\sdb\loader\packages\export\GENUA\DEMODB\20060330101010

Command file mode and session mode

Server profile: <independent_data_path>\wrk

Client profile: <loader_application_data>\log

Example for client profile:

C:\Documents and Settings\anna\My Documents\sdb\loader\log

Structure

In the log file you will find all Loader commands required for establishing a connection and executing the desired 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, and so on.
// 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.

Integration

The log file is structured in such a way 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 execution time, the number of objects for which actions were carried out and any errors which occurred. However, the log file does not detail which individual actions were required to execute the command. If you would like to have this detailed information, you can used the syntax element package_spec to log activities in more detail.

See also:

Additional Log Functions (package_spec)

REMARK Command

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

<remark_command> ::= REMARK "<literal>"

literal: comment

See the SQL Reference Manual, Structure link Literal (literal)