SAP DB has different classes of log files. The table below shows which log files are generated by the database instance. The files are stored in the run directory and its subdirectories.
File name |
Log class |
File Content |
knldiag |
protocol |
Current kernel log; this log is created when the database instance is started with the size specified in the special database parameter KERNELDIAGSIZE. Messages about starts in the operational state
ADMIN are not overwritten cyclically. |
knldiag.old |
protocol |
Last kernel log. Each time the database instance is started, the file knldiag is renamed to knldiag.old. |
knldiag.err |
protocol |
Kernel error messages This file is not overwritten. New error messages are added to the end of the file. |
knldiag.evt |
protocol |
Log of database events |
knltrace |
dump |
Log file of the database trace This file can also contain information about the causes of crashes. This file is initialized each time the database instance is started. |
<database_name>.prt |
protocol |
Test version of database trace |
knldump |
dump |
Backup of the main memory information after a database crash |
rtedump |
dump |
Memory dump from runtime environment of database instance |
<database_name>.pah |
protocol |
History of database parameters |
The following log files also exist:
dbm.* |
|
loader.prt |
|
xserver.prt |
X-Server log file |
SAPDB<profile>_install- |
Log of the Standard Installation or the Update of the database software |
These files belong to the liveCache database instance type (only in SAP systems):
lcinit.log |
Start or initialization of liveCache with CCMS functions from the SAP system |
lcinit.his |
History of all liveCache actions |
lc<token> |
Log of liveCache activities |