In computing, a logfile is a file that records either events that occur in an operating system or other

software runs, or messages between different users of a communication software. [citation needed] Logging is
the act of keeping a log. In the simplest case, messages are written to a single logfile.

Monitoring and Displaying Log Files

Concept
Log and trace file contain information about the system execution.
Logs are mainly used by administrators to monitor the system operation and to perform error
analysis. Logs are typically written to categories.
Traces are usually used by developers or support specialists to record and analyze the occurrence
of certain events in programs during runtime. Traces are typically written to locations.

Who uses logs and traces?

Logging Administrators and wide customers are interested in log files to view messages specific
to distinguish problem areas. Therefore, logs are always switched on and get written automatically.
They have predefined granularity (severity) that can be modified during runtime.
Tracing Support engineers and developers use the trace files facility to check an abnormal
condition in the control flow. Therefore, tracing is not normally turned on. Traces can be switched on
if a problem has occurred and a detailed analysis of a distinct part of a program is necessary.

The System Log

The SAP System logs all system errors, warnings, user locks due to failed logon attempts from known
users, and process messages in the system log. There are to two different types of logs created by the
system log:
Local Logs
Central Logs
Use transaction SM21 to access the system log output screen. With this transaction, you can read any
of the messages that are contained in the system logs. You can modify the view to meet your needs.

Local Logs
Each SAP System application server has a local log that receives all the messages output by this server.
The system log records these messages in a circular file on the server. When this log file reaches the
maximum permissible length, the system log overwrites it, starting over from the beginning. (The
location of the local log is specified in the rslg/local/file profile parameter.)

Central Logs
We recommend that you also maintain a central log file on a selected application server. Each
individual application server then sends its local log messages to this server. The server that you
designate to maintain the central log collects the messages from the other application servers and
writes these messages to the central log.

The central log consists of two files: the active file and the old file. (The location of the active file is
specified in therslg/central/fileprofile parameter; the location of the old file is specified in
therslg/central/old_file.)
The active file contains the current log. When it reaches the maximum size, the system performs a "log
file switch". It deletes the old log file, makes the previously active file the old file, and creates a new
active file. The switch occurs when the size of the active log file is half the value as specified in
therslg/max_diskspace/central parameter. (Note: the SAP System does not support the saving of old
system log files. If you want to save old logs, then you must archive them yourself.)
If you use Windows NT or AS/400, then note the following:
- Central logging is not available on the Windows NT and AS/400 platforms.
- Per default, the profile parameter rslg/collect_daemon/host should be set correctly. However, if you
receive warnings, then make sure that this parameter is set to NONE.
- For these platforms, you can use the All remote syslogs function from transaction SM21 to read the
data of all the instances in your SAP System. In the alert monitor, if you receive an alert, you can use
the Remote syslogfunction to analyze the affected instance.

Log Files
Use
The database system, database tools and interfaces write information and error messages in log files.
Most log files are text files that you can read with a text editor.
Exceptions:
Binary log files
Log files that are only generated by the database system when requested by a user
To display the contents of such log files, use the Database Manager database tool, or the CCMS in SAP
systems. You need the file ID of the log file.
Note that file IDs are case-sensitive.
See
Database Manager GUI,
Reading Log Files
Database Manager CLI,
file_getfirst
Database Administration in CCMS: MaxDB,
Logs and
Messages
Database Administration in CCMS: SAP liveCache Technology,
Logs and
Kernel Logs

Messages

File
Name

Directory

File ID

Description

knldiag

Run directory of the database instance:

<independent_data_path>\wrk\<database_name>
(seeGlossary, Run Directory)

KNLDIAG

Current kernel log of the

database instance
Contains all kernel messages
(error messages, warnings and
information)
See also the special database
parameterKNLDIAGSIZE

knlmsg

Run directory of the database instance

KNLMSG

Detailed current kernel log of

the database instance
Contains all kernel messages

(error messages, warnings and

information)
You can use the Database
Manager to display more
information about the
messages.
Pseudo XML file
knldiag.e Run directory of the database instance
rr

KNLDIAGERR Error messages and start

messages of the kernel since
installation

knldiag.o Run directory of the database instance

ld

KNLDIAGOLD Last kernel log (before the last

restart)

General Log Files

File Name

Directory

File ID

Contents

<database_name>.pah

<independent_data_path>\config

DBMPAHI

History of the database

parameters

<database_name>.prt

Run directory of the database instance:

KNLTRCPRT Text version of the
<independent_data_path>\wrk\<databas
database trace
e_name>

knldump

Run directory of the database instance

KNLDUMP

Memory dump after a

database crash

knlmini.dmp

Run directory of the database instance

Only for Microsoft

Windows
Memory dump after
database kernel crash
(for postmortem
debugging)
See the support
database
parameter MINI_DUMP

knltrace

Run directory of the database instance

KNLTRC

Binary log file of the

database trace; can also
contain information
about the cause of the
crash.
The database system
initializes this file each
time the database
instance is started.

MaxDBInstanceCreation_in <independent_data_path>\wrk
stall-<date-ID>.log

Log of the software

installation
See Installation
Manual,

rtedump

Run directory of the database instance

RTEDUMP

Logging

Latest values of the

runtime environment of
the database instance

liveCache-Specific Log Files

File
File ID Contents
Name

Directory

lcinit.his LCINITHIS History of all start, stop and

Run directory of the database instance:

lcinit.lo
g

LCINIT

initialization actions in the liveCache.

Information from the log lcinit.log is
attached to this history.

<independent_data_path>\wrk\<database_nam
e>

Information for starting, stopping and

initializing the SAP liveCache with the
CCMS function of the SAP system

Run directory of the database instance

Database Manager Log Files

File Name

Directory

File ID

Contents

dbahist.prt

<independent_data_path>\wrk\<database_n DBAHIST
ame>\dbahist

For SAP
systems only
Log of the
database
administratio
n activities

dbm.ebf

Run directory of the database instance:

BACKEBF
<independent_data_path>\wrk\<database_n
ame>

Only for
backup tools
from other
providers
Backup
history,
includes
backup IDs,
external
backup IDs
and error
messages
If a backup
tool
successfully
executed a
backup but
could not
determine
the backup
ID, it enters
the backup
as failed in
the backup
history.

dbm.ebp

Run directory of the database instance

BACKEBP

Only for
backup tools
from other
providers
The log of the
last backup

dbm.ins

Run directory of the database instance

INSTPRT

Log of
loading/updat
ing the
system tables

dbm.knl

Run directory of the database instance

BACKHIST

Backup
history
Contains all

backups and
restore
actions. If no
backups have
yet been
executed or
the backup
history was
interrupted,
HITSLOST is
displayed.
For
information
about the log
files of
backup tools
from other
providers,
see the
respective
documentatio
n.
dbm.mdf

Run directory of the database instance

BACKMDF

History of the
backup
templates
used for the
backups

dbm.prt

Run directory of the database instance

DBMPRT

Log of the
DBM Server
Contains all
administratio
n commands
sent to the
DBM Server

dbm.utl

Run directory of the database instance

UTLPRT

Contains
administratio
n commands
sent from the
DBM Server
to the
database
kernel

dbmsrv_<database_comput <independent_data_path>\wrk
er>

DBMSRV

Instance
independent
log of the
DBM Server

dbmsrv_<database_comput <independent_data_path>\wrk
er>.dmp

DBMSRVMINIDUM
P

Memory
dump saved
by the DBM
server in case
of a crash
Contains
stack and

memory
segments
Can be used
for postmortem
debugging

Loader Log Files

File Name

Directory

File ID

loader.log

<loader_appplication_data>\log

loader.log

<independent_data_path>\wrk

Contents
Log of the Loader

LOADER

Loader server log

loader_<timestamp>.lo <loader_user_data>\packages
g

Log of the Loader in transport mode

transport.log

Transformation history

<loader_application_data>\package
s

See also:
Loader,
Log File,
Transformation History
X Server Log Files

File Name

Directory

File ID

Contents

xserver_<computer_name>.prt <independent_data_path>\wrk XSRVPROT

Log of the X Server

xserver_<computer_name>.old <independent_data_path>\wrk XSRVPROTOLD

Last log of the X Server

Database Analyzer Log Files

File Name

Directory

DBAN.prt

<independent_data_path>\wrk\anal ANALYZER#\DBAN.prt
yzer

Logs of the Database

Analyzer

DBAN.inf

<independent_data_path>\wrk\anal ANALYZER#\DBAN.inf
yzer

Status of the Database

Analyzer

DBAN.err

<independent_data_path>\wrk\anal ANALYZER#\DBAN.err
yzer

Errors of the Database

Analyzer

Other
files

File ID

Contents

ANALYZER#\<date>

log

Event Dispatcher Log Files

File
Name

Directory

File ID

dbmevtdisp Run directory of the database instance:

.prt
<independent_data_path>\wrk\<database_name>

Contents

EVTDISPPR Log of the Event

T
Dispatcher

Synchronization Manager Log Files

File Name

Directory

File ID Contents

Your choice
Defined in the file MSGSERVER.XML

Your choice
Defined in the file MSGSERVER.XML

Log of the message

server