Show TOC

Log FilesLocate this document in the navigation structure

Use

The database system, database tools, and interfaces write information and error messages to log files.

Displaying Log Files

Most log files are text files that you can read using a text editor. Note that some files like the Database Messages file are written in a pseudo-XML format and thus are not easily readable in a text editor, and other files are in binary format. Use Database Studio, Database Manager CLI or CCMS to display these files.

More information:

Creating a Log File Archive for Support

See

Overview of Important Database Log Files

Table 1: Kernel Log Files

Name

File Name

Directory

File ID

Description

Database Messages

KnlMsg

Run directory of the database (see Run Directory).

KNLMSG

Current kernel log file of the database, containing all kernel messages (error messages, warnings, and information)

This file is written in a pseudo-XML format.

The first part of the file contains messages of the database start into the operational state ADMIN: information about the software version, important paths and the current values of the database parameters. These messages are not be overwritten until the next database start, when the old version of the kernel log file is copied to the Database Messages (Old) file.

The second part of the file contains the messages that the database writes during operation. These messages will be overwritten cyclically. If the database crashes, a stack back trace is written.

See also Special Database Parameters KernelMessageFileSize and KernelMessageHistoryCount

Database Errors

KnlMsgArchive

Run directory of the database

KNLMSGARC

Error messages and start messages of the kernel since installation

This file is written in a pseudo-XML format.

This file is not overwritten cyclically. If you are analyzing database problems and the Database Messages and Database Messages (Old) files do not contain the relevant information anymore, check the Database Errors file.

See also the special database parameter MaxKernelMessageArchiveSize

Database Messages (Old)

KnlMsg.Old

Run directory of the database

KNLMSGOLD

Last kernel log file (before the last restart)

This file is written in a pseudo-XML format.

Database Messages (Classic)

-

(generated from the KnlMsg file)

Run directory of the database

KNLDIAG

Classic form of the current database kernel log file

Database Dump

knldump

Run directory of the database

Depending on your system, this file may become very large. To change the location of the file, use the database parameter KernelDumpFileName, see Support Database Parameters.

KNLDUMP

In case of an emergency datatabase shutdown, the global memory of the database is dumped into this file (in binary format).

Note that on Unix, no dump file is written if the database crashes due to a Unix signal.

Runtime Environment Dump

rtedump

Run directory of the database

To change the location of the file, use the support database parameter RTEDumpFileName.

RTEDUMP

In case of an emergency database shutdown, this file contains the tasks that were active in the database at the time of the emergency shutdown.

Name

File Name

Directory

File ID

Content

Database Parameter History

<database_name>.pah

<data_path>\config

You can display the data path using the dbm_getpath DBM command:

dbmcli dbm_getpath DataPath

For more information, see Database Manager CLI, dbm_getpath.

DBMPAHI

History of the database parameter values

Database Trace (Raw/Binary)

knltrace

Run directory of the database (see Run Directory).

To change the name and location of this file, use the support database parameter KernelTraceFile, see Support Database Parameters.

KNLTRC

Messages of the database trace (binary format)

The system initializes this file every time the database is started.

Database Trace (Readable)

<database_name>.prt

Run directory of the database

KNLTRCPRT

Text version of the database trace (available after a database trace has been created)

Installation Log File

Depending on which program you have used to install, update or uninstall the software:

  • SDBSETUPMsg<timestamp>.log (installation using SDBSETUP)

  • SDBINSTMsg<timestamp>.log (installation using SDBINST)

  • SDBuninstMsg<timestamp>.log (deinstallation using sdbuninst)

  • SDBUPDMsg<timestamp>.log (update using SDBUPD)

<global_data>\wrk

You can display the global data path using the dbm_getpath DBM command:

dbmcli dbm_getpath GlobalDataPath

If the system cannot find <global_data>, the following directories are used:

  • Microsoft Windows: %TMP%

  • Unix/Linux: $TMP

-

Messages during installation, update or deinstallation of the software

Event Dispatcher Configuration

klndiag.evt

You can also configure another name using the EventFileName support database parameter.

Run directory of the database

KNLEVT

If the the EventFileSize support database parameter is > 0, the system logs events in this file.

This file is overwritten cyclically.

Table 2: Database Manager Log Files

Name

File Name

Directory

File ID

Content

Backup History

dbm.knl

Run directory of the database (see Run Directory).

BACKHIST

Backup history of the database: contains all backup and restore actions

If no backups have yet been executed or the backup history was interrupted, HISTLOST is displayed.

For information from third-party backup tools, see the respective documentation.

Backup Templates

BackupTemplates.xml

Run directory of the database

DBMMDF

Information and history of backup templates of the database

Database Manager Log File

dbm.prt

Run directory of the database

DBMPRT

Log file of the DBM server of the current installation, containing all administration commands sent to the DBM server

Examples: information about adding data and log volumes or database parameter changes

Global Database Manager Log File

dbmsrv_<database_computer>.prt

<data_path>\wrk

You can display the data path using the dbm_getpath DBM command:

dbmcli dbm_getpath DataPath

For more information, see Database Manager CLI, dbm_getpath.

DBMSRV

General log file for all DBM servers that are located on the database computer

Database Manager History Log File

dbmcfg.his

Run directory of the database

INSTANCECFGHISTORY

Changes on Database Manager configuration file for the database dbm.cfg (performed by Database Manager automatically) are written to log file dbmcfg.his.

Installation Log File

dbm.ins

Run directory of the database

INSTPRT

Information on loading the system tables for the database

DBA Action Log

dbahist.prt

<run_directory>\dbahist

DBAHIST

Database administration actions, see DBA History

External Backup History

dbm.ebf

Run directory of the database

BACKEBF

Only for third-party backup tools

Backup history of the database, 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.

External Backup Log

dbm.ebp

Run directory of the database

BACKEBP

Only for third-party backup tools

Information about backups of the database that are created using third-party backup tools. This file is overwritten when a new request is sent to a third-party backup tool.

Table 3: SAP MaxDB X Server Log Files

Name

File Name

Directory

File ID

Content

Global Listener Messages

sdbgloballistener_<computer_name>.prt

<data_path>\wrk

You can display the data path using the dbm_getpath DBM command:

dbmcli dbm_getpath DataPath

For more information, see Database Manager CLI, dbm_getpath.

GLOBALLSTN#.prt

Note that you need to enter the file ID exactly as shown above, including the hash mark ( #).

Log file of the global listener

Contains error messages concerning the remote communication (for example in case of network problems)

The first part of the file contains information about the operating system settings and the user environment in which the global listener was started.

For more information, see Global Listener and X Servers.

Global Listener Messages (Old)

sdbgloballistener_<computer_name>.prt.old

<data_path>\wrk

GLOBALLSTNOLD#.prt.old

Note that you need to enter the file ID exactly as shown above, including the hash mark ( #).

Last log file of the SAP MaxDB global listener

X Server Messages

xserver_<computer_name>_<port>.prt

<data_path>\wrk

XSRVPRT

Log file of the installation-specific X server of the installation you are currently working with

Contains error messages concerning the remote communication (for example in case of network problems)

The first part of the file contains information about the operating system settings and the user environment in which the X server was started.

X Server Messages (Old)

xserver_<computer_name>_<port>.prt.old

<data_path>\wrk

XSRVPRTOLD

Last log file of the installation-specific X server of the installation you are currently working with

NI Server Messages

niserver_<computer_name>_<port>.trace

<data_path>\wrk

-

Log file of the NI server (which is used for connections via SAProuter) of the installation you are currently working with

Table 4: Database Studio Log Files

File Name

Directory

Content

dbstudio.log

<user_home>\sdb\DatabaseStudio\.metadata\.plugins\com.sap.sdb.tools.core

Database Studio log file

The system overwrites this log file each time Database Studio is started and saves the old log file as dbstudio.log.bak.

For information on how to configure logging for Database Studio, see Database Studio Preferences: Logging.

dbstudio.log.bak

<user_home>\sdb\DatabaseStudio\.metadata\.plugins\com.sap.sdb.tools.core

Previous Database Studio log file

Table 5: Database Analyzer Log Files

File Name

Directory

Content

DBAN.prt

<run_directory>\analyzer\<date>

For more information, see Run Directory.

Database Analyzer log files

DBAN.inf

<run_directory>\analyzer

Database Analyzer status

DBAN.err

<run_directory>\analyzer

Database Analyzer errors

Further Database Analyzer Log Files

-

-

Table 6: Loader Log Files

File Name

Directory

File ID

Content

loader.log/loader_<timestamp>.log

<loader_user_data>\log

-

Loader log file

Table 7: SAP liveCache-Specific Log Files

File Name

File ID

Directory

Content

lcinit.his

LCINITHIS

Run directory of the database (see Run Directory).

History of all start, stop, and initialization actions of SAP liveCache. The system appends the information in the lcinit.log log file to this log file.

lcinit.log

LCINIT

Run directory of the database

Information on starting, stopping and initializing SAP liveCache with the CCMS function of the SAP system