The database system, database tools and interfaces write information and error messages to log files.
Most log files are text files that you can read using a text editor. Exceptions are binary log files and log files that are only generated by the database system when requested by a user.
More information:
Database Studio, Displaying Configuration and Log Files
Database Manager CLI, file_getfirst
Name |
File Name |
Directory |
File ID |
Description |
---|---|---|---|---|
Database Messages |
KnlMsg |
Run directory of the database: <independent_data_path>\wrk\<database_name> More information: Glossary, Run Directory |
KNLMSG |
Detailed current kernel log file of the database Contains all kernel messages (error messages, warnings and information) More information: 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 |
Database Messages (Old) |
KnlMsg.Old |
Run directory of the database |
KNLMSGOLD |
Last kernel log file (before the last restart) |
Database Messages (Classic) |
- (generated from the KnlMsg file) |
Run directory of the database |
KNLDIAG |
Classic form of the current database kernel log file |
Name |
File Name |
Directory |
File ID |
Content |
---|---|---|---|---|
Database Parameter History |
<database_name>.pah |
<independent_data_path>\config |
DBMPAHI |
History of the database parameters |
Database Trace (Raw/Binary) |
knltrace |
Run directory of the database |
KNLTRC |
Binary log file of the database trace; can also contain information about the cause crashes. The database system initializes this file each time the database is started. |
Database Trace (Readable) |
<database_name>.prt |
Run directory of the database: <independent_data_path>\wrk\<database_name> |
KNLTRCPRT |
Text version of the database trace |
- |
MaxDBInstanceCreation_install-<date-ID>.log |
<independent_data_path>\wrk |
- |
Log of the software installation |
Database Events |
klndiag.evt You can also configure another name using the EventFileName support database parameter. |
Run directory of the database: <independent_data_path>\wrk\<database_name> |
KNLEVT |
The system logs events in this file when the EventFileSize support database parameter is > 0. This file is overwritten cyclically. More information: Support Database Parameters |
Name |
File Name |
Directory |
File ID |
Content |
---|---|---|---|---|
Backup History |
dbm.knl |
Run directory of the database |
BACKHIST |
Backup history Contains all backup and restore actions. If no backups have yet been executed or the backup history was interrupted, HISTLOST is displayed. For information about the log files of backup tools from other providers, see the respective documentation. |
Backup Media History |
dbm.mdf |
Run directory of the database |
BACKMDF |
History of the backup templates used for the backups |
Database Manager Log File |
dbm.prt |
Run directory of the database |
DBMPRT |
Log of the DBM Server Contains all administration commands sent to the DBM Server |
Global Database Manager Log File |
dbmsrv_<database_computer>.prt |
<independent_data_path>\wrk |
DBMSRV |
Independent log of the DBM Server |
Installation Log File |
dbm.ins |
Run directory of the database |
INSTPRT |
Log of loading and updating the system tables |
- |
dbahist.prt |
<independent_data_path>\wrk\<database_name>\dbahist |
DBAHIST |
For SAP systems only Log of database administration activities |
- |
dbm.ebf |
Run directory of the database: <independent_data_path>\wrk\<database_name> |
BACKEBF |
Only for third-party backup tools 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 |
BACKEBP |
Only for third-party backup Log file of the last backup |
Name |
File Name |
Directory |
File ID |
Content |
---|---|---|---|---|
X Server Messages |
xserver_<computer_name>.prt |
<independent_data_path>\wrk |
XSRVPROT |
Log of the SAP MaxDB X Server (database communication server) |
X Server Messages (Old) |
xserver_<computer_name>.old |
<independent_data_path>\wrk |
XSRVPROTOLD |
Last log of the SAP MaxDB X Server |
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. |
dbstudio.log.bak |
<user_home>\sdb\DatabaseStudio\.metadata\.plugins\com.sap.sdb.tools.core |
Previous Database Studio log file |
File Name |
Directory |
Content |
---|---|---|
DBAN.prt |
<independent_data_path>\wrk\analyzer |
Database Analyzer log files |
DBAN.inf |
<independent_data_path>\wrk\analyzer |
Database Analyzer status |
DBAN.err |
<independent_data_path>\wrk\analyzer |
Database Analyzer errors |
Further Database Analyzer Log Files |
- |
- |
File Name |
Directory |
File ID |
Content |
---|---|---|---|
loader.log |
<loader_appplication_data>\log |
- |
Loader log file |
loader.log |
<independent_data_path>\wrk |
LOADER |
Loader server log file |
loader_<timestamp>.log |
<loader_user_data>\packages |
- |
Log file of Loader in transport mode |
transport.log |
<loader_application_data>\packages |
- |
Transformation history |
More information: Loader, |
File Name |
File ID |
Content |
Directory |
---|---|---|---|
lcinit.his |
LCINITHIS |
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. |
Run directory of the database: <independent_data_path>\wrk\<database_name> |
lcinit.log |
LCINIT |
Information for starting, stopping and initializing SAP liveCache with the CCMS function of the SAP system |
Run directory of the database |
Glossary, Directory